EUVD-2026-67856
GHSA-q79r-r9xg-r863
Severity by source
AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:N/A:N
Network API requires low-privilege auth (PR:L); S:C reflects admin-role callers accessing password hashes of other users beyond their own scope.
Primary rating from Vendor (https://github.com/Graylog2/graylog2-server).
CVSS VectorVendor: https://github.com/Graylog2/graylog2-server
Lifecycle Timeline
2DescriptionCVE.org
Impact
A vulnerability was found in Graylog's API endpoint for retrieving system catalog entity titles. Authenticated users could retrieve database fields of supported entities by sending a custom API request. These fields can include e.g. the password hash of a user (but not the password itself), which should not be returned through the API, regardless of the endpoint. Permission checks do still apply, so users can retrieve their own password hash, but not those of other users. The admin user (or any user with an admin role) can retrieve password hashes of all users.
Patches
This issue has been patched in Graylog 7.1.4. In this version, an allow list will be used to check if protected fields are being accessed, refusing those requests. Affected users should upgrade to 7.1.4 or above to remediate the vulnerability.
Workarounds
There is no known workaround. Upgrading to a patched version is recommended.
Credits
Thanks to Evelynkaz for reporting.
AnalysisAI
Graylog Server's system catalog entity titles API endpoint leaks protected database fields - including user password hashes - to authenticated requesters who craft custom field-selection parameters. PR:L authentication is required, and permission checks are partially enforced: regular users are limited to their own password hash, but any user holding an admin role can extract password hashes for every account in the system. …
Unlock full vulnerability intelligence
- Risk assessment & exploitation conditions
- Attack chain visualization
- Remediation with exact patch versions
- Threat intelligence from 22 sources
- Personal watchlist & email alerts
Free forever · No credit card required
Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata
Vulnerability AssessmentAI
| Exploitation | Authentication is required - the CVSS PR:L metric confirms a valid low-privilege Graylog account is the minimum prerequisite; unauthenticated access is not possible. … Additional conditions and limiting factors are described in the full assessment. |
| Risk Assessment | The provided CVSS 3.1 vector (AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:N/A:N, score 5.0) is consistent with the description: network-reachable, low complexity, requires only a valid Graylog account, and the scope change (S:C) reflects that an admin-role holder can reach password hashes belonging to all other users - data outside the requesting account's own scope. … Full risk analysis with EPSS, KEV, and SSVC signal comparison available after sign-in. |
| Exploit Scenario | Full exploit scenario with step-by-step reproduction available after sign-in. |
| Remediation | Upgrade Graylog Server to version 7.1.4 or later; this is the vendor-confirmed fix (https://github.com/Graylog2/graylog2-server/releases/tag/7.1.4). … Detailed patch versions, workarounds, and compensating controls in full report. |
Threat intelligence, references, and detailed analysis are available after sign-in.
Same technique Information Disclosure
View allShare
External POC / Exploit Code
Leaving vuln.today