Is org.graylog2:graylog2-server 6.2 vulnerable?

Maven · 15 releases from 6.2.0 to 6.2.14 · latest org.graylog2:graylog2-server is 7.2.2 · checked 18 Nov 2026

Yes: 2 known advisories

Yes. org.graylog2:graylog2-server 6.2.14, the last 6.2 release, is affected by 2 known security advisories (1 high, 1 medium), including CVE-2026-55841, CVE-2026-55867. 1 more affects earlier 6.2.x releases. Upgrade to 6.3.12 or later to fix all of them.

Upgrade with:mvn versions:use-dep-version -Dincludes=org.graylog2:graylog2-server -DdepVersion=6.3.12 -DforceVersion=true

Is your project on an affected org.graylog2:graylog2-server?

Private repo? Upload its lockfile instead, or connect GitHub to check every repo.

Look after several Java apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie

Advisories affecting org.graylog2:graylog2-server 6.2.14

  • MediumCVE-2026-55867GHSA-j769-9gv9-65gr28 Aug 2026

    Graylog token revocation endpoint allows authenticated users to delete other users’ access tokens

    Affected
    >=6.2.0 <6.3.12 · >=7.0.0 <7.0.7 · >=7.1.0 <7.1.2
    Fixed in
    6.3.12, 7.0.7, 7.1.2
  • HighCVE-2026-55841GHSA-gqr6-r77p-c2pj28 Aug 2026

    Fortigate syslog message parser can be exploited to modify or delete fields from the original message

    Affected
    <6.3.12 · >=7.0.0 <7.0.7 · >=7.1.0 <7.1.2
    Fixed in
    6.3.12, 7.0.7, 7.1.2

Fixed within 6.2.x, affecting earlier releases

  • HighCVE-2025-53106GHSA-3m86-c9x3-vwm930 Jun 2025

    Graylog vulnerable to privilege escalation through API tokens

    Affected
    >=6.2.0 <6.2.4 · >=6.3.0-alpha.1 <6.3.0-rc.2
    Fixed in
    6.2.4, 6.3.0-rc.2

Every org.graylog2:graylog2-server 6.2.x release

Affected: 6.2.0 to 6.2.14. Latest org.graylog2:graylog2-server: 7.2.2.

VersionKnown advisories
org.graylog2:graylog2-server 6.2.14CVE-2026-55867, CVE-2026-55841
org.graylog2:graylog2-server 6.2.13CVE-2026-55867, CVE-2026-55841
org.graylog2:graylog2-server 6.2.12CVE-2026-55867, CVE-2026-55841
org.graylog2:graylog2-server 6.2.11CVE-2026-55867, CVE-2026-55841
org.graylog2:graylog2-server 6.2.10CVE-2026-55867, CVE-2026-55841
org.graylog2:graylog2-server 6.2.9CVE-2026-55867, CVE-2026-55841
org.graylog2:graylog2-server 6.2.8CVE-2026-55867, CVE-2026-55841
org.graylog2:graylog2-server 6.2.7CVE-2026-55867, CVE-2026-55841
org.graylog2:graylog2-server 6.2.6CVE-2026-55867, CVE-2026-55841
org.graylog2:graylog2-server 6.2.5CVE-2026-55867, CVE-2026-55841
org.graylog2:graylog2-server 6.2.4CVE-2026-55867, CVE-2026-55841
org.graylog2:graylog2-server 6.2.3CVE-2026-55867, CVE-2026-55841, CVE-2025-53106
org.graylog2:graylog2-server 6.2.2CVE-2026-55867, CVE-2026-55841, CVE-2025-53106
org.graylog2:graylog2-server 6.2.1CVE-2026-55867, CVE-2026-55841, CVE-2025-53106
org.graylog2:graylog2-server 6.2.0CVE-2026-55867, CVE-2026-55841, CVE-2025-53106

Which of your client projects are still on org.graylog2:graylog2-server 6.2?

NPMscan reads the lockfiles in every GitHub repo you pick, finds the exact org.graylog2:graylog2-server version each one installs, and checks it against these advisories. Each finding comes with the command that fixes it.

Other org.graylog2:graylog2-server versions

Advisory data from OSV.dev (opens OSV.dev in a new tab), which includes the GitHub Advisory Database. Release list from the Maven registry. Refreshed daily.