Is org.graylog2:graylog2-server 7.0 vulnerable?
Maven · 17 releases from 7.0.0 to 7.0.16 · latest org.graylog2:graylog2-server is 7.2.2 · checked 18 Nov 2026
No known advisories in the last release
org.graylog2:graylog2-server 7.0.16, the last 7.0 release, has no known advisories. 3 advisories affect earlier 7.0.x releases, so update to 7.0.16.
mvn versions:use-dep-version -Dincludes=org.graylog2:graylog2-server -DdepVersion=7.0.16 -DforceVersion=trueIs your project on an affected org.graylog2:graylog2-server?
Look after several Java apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie
Fixed within 7.0.x, affecting earlier releases
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
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
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 7.0.x release
Affected: 7.0.0 to 7.0.8. 7.0.9 and later are not affected. Latest org.graylog2:graylog2-server: 7.2.2.
| Version | Known advisories |
|---|---|
| org.graylog2:graylog2-server 7.0.16 | None |
| org.graylog2:graylog2-server 7.0.15 | None |
| org.graylog2:graylog2-server 7.0.14 | None |
| org.graylog2:graylog2-server 7.0.13 | None |
| org.graylog2:graylog2-server 7.0.12 | None |
| org.graylog2:graylog2-server 7.0.11 | None |
| org.graylog2:graylog2-server 7.0.10 | None |
| org.graylog2:graylog2-server 7.0.9 | None |
| org.graylog2:graylog2-server 7.0.8 | CVE-2026-69190 |
| org.graylog2:graylog2-server 7.0.7 | CVE-2026-69190 |
| org.graylog2:graylog2-server 7.0.6 | CVE-2026-69190, CVE-2026-55867, CVE-2026-55841 |
| org.graylog2:graylog2-server 7.0.5 | CVE-2026-69190, CVE-2026-55867, CVE-2026-55841 |
| org.graylog2:graylog2-server 7.0.4 | CVE-2026-69190, CVE-2026-55867, CVE-2026-55841 |
| org.graylog2:graylog2-server 7.0.3 | CVE-2026-69190, CVE-2026-55867, CVE-2026-55841 |
| org.graylog2:graylog2-server 7.0.2 | CVE-2026-69190, CVE-2026-55867, CVE-2026-55841 |
| org.graylog2:graylog2-server 7.0.1 | CVE-2026-69190, CVE-2026-55867, CVE-2026-55841 |
| org.graylog2:graylog2-server 7.0.0 | CVE-2026-69190, CVE-2026-55867, CVE-2026-55841 |
Which of your client projects are still on org.graylog2:graylog2-server 7.0?
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
- org.graylog2:graylog2-server 7.2
- org.graylog2:graylog2-server 7.1
- org.graylog2:graylog2-server 6.3
- org.graylog2:graylog2-server 6.2
- org.graylog2:graylog2-server 6.1
- org.graylog2:graylog2-server 6.0
- org.graylog2:graylog2-server 5.2
- org.graylog2:graylog2-server 5.1
- org.graylog2:graylog2-server 5.0
- All org.graylog2:graylog2-server advisories
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.