Graylog vulnerable to privilege escalation through API tokens
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | |||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Graylog2 | graylog2-server | affected |
|
Configuration 1 [-]
|
No data.
No data available yet.
| Source | ID | Title |
|---|---|---|
EUVD |
EUVD-2025-19760 | Graylog vulnerable to privilege escalation through API tokens |
Github GHSA |
GHSA-3m86-c9x3-vwm9 | Graylog vulnerable to privilege escalation through API tokens |
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
Exploit prediction score: < 1% (0.608% probability within 30 days)
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Graylog
Graylog graylog |
|
| CPEs | cpe:2.3:a:graylog:graylog:*:*:*:*:*:*:*:* cpe:2.3:a:graylog:graylog:6.3.0:-:*:*:*:*:*:* cpe:2.3:a:graylog:graylog:6.3.0:alpha1:*:*:*:*:*:* cpe:2.3:a:graylog:graylog:6.3.0:alpha2:*:*:*:*:*:* cpe:2.3:a:graylog:graylog:6.3.0:alpha3:*:*:*:*:*:* cpe:2.3:a:graylog:graylog:6.3.0:alpha4:*:*:*:*:*:* cpe:2.3:a:graylog:graylog:6.3.0:beta1:*:*:*:*:*:* cpe:2.3:a:graylog:graylog:6.3.0:beta2:*:*:*:*:*:* cpe:2.3:a:graylog:graylog:6.3.0:beta3:*:*:*:*:*:* cpe:2.3:a:graylog:graylog:6.3.0:beta4:*:*:*:*:*:* cpe:2.3:a:graylog:graylog:6.3.0:beta5:*:*:*:*:*:* cpe:2.3:a:graylog:graylog:6.3.0:rc1:*:*:*:*:*:* |
|
| Vendors & Products |
Graylog
Graylog graylog |
|
| Metrics |
cvssV3_1
|
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
| Type | Values Removed | Values Added |
|---|---|---|
| Description | Graylog is a free and open log management platform. In versions 6.2.0 to before 6.2.4 and 6.3.0-alpha.1 to before 6.3.0-rc.2, Graylog users can gain elevated privileges by creating and using API tokens for the local Administrator or any other user for whom the malicious user knows the ID. For the attack to succeed, the attacker needs a user account in Graylog. They can then proceed to issue hand-crafted requests to the Graylog REST API and exploit a weak permission check for token creation. This issue has been patched in versions 6.2.4 and 6.3.0-rc.2. A workaround involves disabling the respective configuration found in System > Configuration > Users > "Allow users to create personal access tokens". | |
| Title | Graylog vulnerable to privilege escalation through API tokens | |
| Weaknesses | CWE-285 | |
| References |
| |
| Metrics |
cvssV4_0
|