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".
                
            Metrics
Affected Vendors & Products
References
        History
                    Thu, 30 Oct 2025 16:00:00 +0000
| 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
         
  | 
Wed, 02 Jul 2025 21:15:00 +0000
| Type | Values Removed | Values Added | 
|---|---|---|
| Metrics | 
        
        ssvc
         
  | 
Wed, 02 Jul 2025 13:45:00 +0000
| 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
         
  | 
Status: PUBLISHED
Assigner: GitHub_M
Published: 2025-07-02T13:28:08.825Z
Updated: 2025-07-02T20:22:11.030Z
Reserved: 2025-06-25T13:41:23.086Z
Link: CVE-2025-53106
Updated: 2025-07-02T20:22:07.572Z
Status : Analyzed
Published: 2025-07-02T14:15:26.273
Modified: 2025-10-30T15:45:51.620
Link: CVE-2025-53106
No data.
ReportizFlow