Is org.graylog2:graylog2-server 6.3 vulnerable?

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

No known advisories in the last release

org.graylog2:graylog2-server 6.3.15, the last 6.3 release, has no known advisories. 3 advisories affect earlier 6.3.x releases, so update to 6.3.15.

Update within 6.3:mvn versions:use-dep-version -Dincludes=org.graylog2:graylog2-server -DdepVersion=6.3.15 -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

Fixed within 6.3.x, affecting earlier releases

  • MediumCVE-2026-69190GHSA-m9c2-85gv-8xr522 Sept 2026

    Graylog: Manager-to-Owner privilege escalation on saved searches and dashboards

    Affected
    >=6.3.0 <6.3.14 · >=7.0.0 <7.0.9 · >=7.1.0 <7.1.4
    Fixed in
    6.3.14, 7.0.9, 7.1.4
  • 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

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

Affected: 6.3.0 to 6.3.13. 6.3.14 and later are not affected. Latest org.graylog2:graylog2-server: 7.2.2.

VersionKnown advisories
org.graylog2:graylog2-server 6.3.15None
org.graylog2:graylog2-server 6.3.14None
org.graylog2:graylog2-server 6.3.13CVE-2026-69190
org.graylog2:graylog2-server 6.3.12CVE-2026-69190
org.graylog2:graylog2-server 6.3.11CVE-2026-69190, CVE-2026-55867, CVE-2026-55841
org.graylog2:graylog2-server 6.3.10CVE-2026-69190, CVE-2026-55867, CVE-2026-55841
org.graylog2:graylog2-server 6.3.9CVE-2026-69190, CVE-2026-55867, CVE-2026-55841
org.graylog2:graylog2-server 6.3.8CVE-2026-69190, CVE-2026-55867, CVE-2026-55841
org.graylog2:graylog2-server 6.3.7CVE-2026-69190, CVE-2026-55867, CVE-2026-55841
org.graylog2:graylog2-server 6.3.5CVE-2026-69190, CVE-2026-55867, CVE-2026-55841
org.graylog2:graylog2-server 6.3.4CVE-2026-69190, CVE-2026-55867, CVE-2026-55841
org.graylog2:graylog2-server 6.3.3CVE-2026-69190, CVE-2026-55867, CVE-2026-55841
org.graylog2:graylog2-server 6.3.2CVE-2026-69190, CVE-2026-55867, CVE-2026-55841
org.graylog2:graylog2-server 6.3.1CVE-2026-69190, CVE-2026-55867, CVE-2026-55841
org.graylog2:graylog2-server 6.3.0CVE-2026-69190, CVE-2026-55867, CVE-2026-55841

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

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.