Graylog 6.3.0 Alpha 2
Approved changes feed: RSS · Atom
cpe:2.3:a:graylog:graylog:6.3.0:alpha2:*:*:*:*:*:*
part: a version: 6.3.0 update: alpha2
| Vendor | Graylog (a3d1ffbe-f335-5bd2-b539-69be69a93655) |
|---|---|
| Product | Graylog (732b9fd8-0305-50e3-b071-3b47c3f2aaaf) |
| Edition | * |
| Language | * |
| Software edition | * |
| Target software | * |
| Target hardware | * |
| Other | * |
| Notes | Imported from NVD CPE 2.0 feed |
PURL mappings
| PURL | Source | Last updated |
|---|---|---|
pkg:github/graylog2/graylog2-server |
purl2cpe | 2026-06-01 10:11:01.885809 |
Vulnerability references
| Identifier | cpeApplicability | Submitted | db.gcve.eu details | Rationale |
|---|---|---|---|---|
CVE:CVE-2025-53106 |
vulnerable | 2026-06-08 07:31:13.963711 |
Graylog vulnerable to privilege escalation through API tokens
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".
Published: 2025-07-02T13:28:08.825Z
Updated: 2025-07-02T20:22:11.030Z |
Imported from gcve-enriched-dumps CVE data |
Contribute
You can submit an edit proposal for this CPE entry or suggest a related product/vendor addition using the action button above.