Advisory Database
  • Advisories
  • Dependency Scanning
  1. maven
  2. ›
  3. org.graylog2/graylog2-server
  4. ›
  5. CVE-2025-53106

CVE-2025-53106: Graylog vulnerable to privilege escalation through API tokens

June 30, 2025 (updated July 2, 2025)

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.

References

  • github.com/Graylog2/graylog2-server
  • github.com/Graylog2/graylog2-server/commit/6936bd16a783c2944a3d2f1e83902062520f90e3
  • github.com/Graylog2/graylog2-server/commit/9215b8f1fd32566c31e6f7447ed864df3590c157
  • github.com/Graylog2/graylog2-server/security/advisories/GHSA-3m86-c9x3-vwm9
  • github.com/advisories/GHSA-3m86-c9x3-vwm9
  • nvd.nist.gov/vuln/detail/CVE-2025-53106

Code Behaviors & Features

Detect and mitigate CVE-2025-53106 with GitLab Dependency Scanning

Secure your software supply chain by verifying that all open source dependencies used in your projects contain no disclosed vulnerabilities. Learn more about Dependency Scanning →

Affected versions

All versions starting from 6.2.0 before 6.2.4, all versions starting from 6.3.0-alpha.1 before 6.3.0-rc.2

Fixed versions

  • 6.2.4
  • 6.3.0-rc.2

Solution

Upgrade to versions 6.2.4, 6.3.0-rc.2 or above.

Weakness

  • CWE-285: Improper Authorization

Source file

maven/org.graylog2/graylog2-server/CVE-2025-53106.yml

Spotted a mistake? Edit the file on GitLab.

  • Site Repo
  • About GitLab
  • Terms
  • Privacy Statement
  • Contact

Page generated Tue, 19 Aug 2025 12:18:59 +0000.