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

CVE-2025-53106 · Severity: medium · CVSS 4 · Published 2025-06-30

Graylog vulnerable to privilege escalation through API tokens

Technologies: org.graylog2:graylog2-server (Maven). Vendors: Maven.

Quick answers

Is CVE-2025-53106 exploited in the wild?
No. Junglewise Threat Intelligence has no report of CVE-2025-53106 being exploited in the wild.
How severe is CVE-2025-53106?
Medium severity, with a CVSS score of 4, published 30 June 2025.
Which products and versions are affected?
org.graylog2:graylog2-server (Maven) ECOSYSTEM:introduced=6.2.0,fixed=6.2.4.
Is there a fix for CVE-2025-53106?
Yes. org.graylog2:graylog2-server (Maven): upgrade to 6.2.4 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
Am I affected by CVE-2025-53106?
Check whether you run org.graylog2:graylog2-server (Maven) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

  • org.graylog2:graylog2-server (Maven): upgrade to 6.2.4 or later
    # set org.graylog2:graylog2-server to 6.2.4 in your pom.xml or build.gradle

Affected products

  • org.graylog2:graylog2-server (Maven) ECOSYSTEM:introduced=6.2.0,fixed=6.2.4

Identifiers

  • CVE-2025-53106
  • GHSA-3m86-c9x3-vwm9

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.