Vulnerability Database · Maven · Package report

org.graylog2:graylog2-server: vulnerability history, versions and safety

org.graylog2:graylog2-server is a package in the Maven ecosystem. Vulert records 16 vulnerabilities for it across 92 releases, from May 2022 to Sep 2026. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
16 vulnerabilities recorded H5 M8 L3
i
0 with no fix published

Every vulnerability has a patched version to move to.

i
4 in the last 12 months

Most recent disclosure 22 Sep 2026.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

Vulert verdict on org.graylog2:graylog2-server 7.2.1 i

Updated on 23 Oct 2026

Good news: 7.2.1, the version you would install today, has no known vulnerabilities. Older releases do — the table below lists all 16.

Package health score 71/100
  • Security Some issues to review
  • Maintenance Sustainable
  • Popularity Niche
  • Community Moderate

What to do: Stay on 7.2.1 or newer. This can change: a vulnerability disclosed tomorrow can affect 7.2.1 too — Vulert watches the package and alerts you if that happens. Monitor it with Vulert →

  • Current release 7.2.1 — unaffected i
  • Vulnerabilities on record 16 over 4 years · 4 in the last year i
  • Latest disclosure 22 Sep 2026 i
  • Highest CVSS 8.8 i
  • With no published fix 0 i
  • Depended on by 4 packages i
  • Stars 8,160 i
  • OpenSSF scorecard 5/10 i
  • Last release this month i
  • Licence SSPL-1.0 i

Version list, release dates, licence and dependants published by Maven Central, refreshed 23 Oct 2026. Licence information is not legal advice.

Concerned about your application's security?

Vulert continues monitoring your dependencies and alerts you when new vulnerabilities are disclosed. No installation and no source-code access required.

01 Versions

Which versions are affected

Every version Vulert tracks for org.graylog2:graylog2-server, newest first, with the vulnerabilities recorded against each one. A version showing none has no vulnerability in the Vulert database — open it for the full picture on that release.

i
Version Released Vulert vulnerabilities Licence Fix published Details
7.2.1 19 Oct 2026 none SSPL-1.0 — Details →
7.0.15 19 Oct 2026 none SSPL-1.0 — Details →
7.1.11 19 Oct 2026 none SSPL-1.0 — Details →
7.2.0 12 Oct 2026 none SSPL-1.0 — Details →
7.0.14 07 Oct 2026 none SSPL-1.0 — Details →
7.1.10 07 Oct 2026 none SSPL-1.0 — Details →
7.1.9 02 Sep 2026 none SSPL-1.0 — Details →
7.0.13 02 Sep 2026 none SSPL-1.0 — Details →
7.1.8 18 Aug 2026 none SSPL-1.0 — Details →
7.1.7 05 Aug 2026 none SSPL-1.0 — Details →
7.0.12 05 Aug 2026 none SSPL-1.0 — Details →
6.3.15 05 Aug 2026 none SSPL-1.0 — Details →
7.1.6 23 Jul 2026 none SSPL-1.0 — Details →
7.0.11 23 Jul 2026 none SSPL-1.0 — Details →
7.0.10 08 Jul 2026 none SSPL-1.0 — Details →
7.1.5 08 Jul 2026 none SSPL-1.0 — Details →
7.0.9 01 Jul 2026 none SSPL-1.0 — Details →
7.1.4 01 Jul 2026 none SSPL-1.0 — Details →
6.3.14 01 Jul 2026 none SSPL-1.0 — Details →
7.0.8 05 Jun 2026 none SSPL-1.0 — Details →
7.1.3 05 Jun 2026 M1 SSPL-1.0 Yes Details →
6.3.13 05 Jun 2026 M1 SSPL-1.0 Yes Details →
7.0.7 20 May 2026 none SSPL-1.0 — Details →
7.1.2 20 May 2026 M1 SSPL-1.0 Yes Details →
6.3.12 20 May 2026 M1 SSPL-1.0 Yes Details →
7.1.1 08 May 2026 M1 SSPL-1.0 Yes Details →
6.3.11 01 Apr 2026 H1 M2 SSPL-1.0 Yes Details →
6.2.14 01 Apr 2026 H1 M1 SSPL-1.0 Yes Details →
7.0.6 01 Apr 2026 none SSPL-1.0 — Details →
7.0.5 04 Mar 2026 none SSPL-1.0 — Details →
6.3.10 04 Mar 2026 H1 M2 SSPL-1.0 Yes Details →
6.2.13 04 Mar 2026 H1 M1 SSPL-1.0 Yes Details →
6.2.12 05 Feb 2026 H1 M1 SSPL-1.0 Yes Details →
6.3.9 05 Feb 2026 H1 M2 SSPL-1.0 Yes Details →
7.0.4 05 Feb 2026 none SSPL-1.0 — Details →
6.2.11 08 Jan 2026 H1 M1 SSPL-1.0 Yes Details →
6.3.8 08 Jan 2026 H1 M2 SSPL-1.0 Yes Details →
7.0.3 08 Jan 2026 none SSPL-1.0 — Details →
6.2.10 03 Dec 2025 H1 M1 SSPL-1.0 Yes Details →
6.3.7 03 Dec 2025 H1 M2 SSPL-1.0 Yes Details →
7.0.2 03 Dec 2025 none SSPL-1.0 — Details →
7.0.1 24 Nov 2025 none SSPL-1.0 — Details →
6.2.9 05 Nov 2025 H1 M1 SSPL-1.0 Yes Details →
7.0.0 03 Nov 2025 none SSPL-1.0 — Details →
6.3.5 15 Oct 2025 H1 M2 SSPL-1.0 Yes Details →
6.1.16 01 Oct 2025 H1 SSPL-1.0 Yes Details →
6.2.8 01 Oct 2025 H1 M1 SSPL-1.0 Yes Details →
6.3.4 01 Oct 2025 H1 M2 SSPL-1.0 Yes Details →
6.1.15 03 Sep 2025 H1 SSPL-1.0 Yes Details →
6.2.7 03 Sep 2025 H1 M1 SSPL-1.0 Yes Details →
6.3.3 03 Sep 2025 H1 M2 SSPL-1.0 Yes Details →
6.1.14 06 Aug 2025 H1 SSPL-1.0 Yes Details →
6.2.6 06 Aug 2025 H1 M1 SSPL-1.0 Yes Details →
6.3.2 06 Aug 2025 H1 M2 SSPL-1.0 Yes Details →
6.3.1 04 Jul 2025 H1 M2 SSPL-1.0 Yes Details →
6.2.5 02 Jul 2025 H1 M1 SSPL-1.0 Yes Details →
6.1.13 02 Jul 2025 H1 SSPL-1.0 Yes Details →
6.3.0 30 Jun 2025 H1 M2 SSPL-1.0 Yes Details →
6.2.4 23 Jun 2025 H1 M1 SSPL-1.0 Yes Details →
6.1.12 04 Jun 2025 H1 SSPL-1.0 Yes Details →
6.2.3 04 Jun 2025 H2 M1 SSPL-1.0 Yes Details →
6.1.11 07 May 2025 H1 SSPL-1.0 Yes Details →
6.2.2 07 May 2025 H2 M1 SSPL-1.0 Yes Details →
6.2.1 30 Apr 2025 H2 M1 SSPL-1.0 Yes Details →
6.2.0 28 Apr 2025 H2 M1 SSPL-1.0 Yes Details →
6.0.14 03 Apr 2025 H2 SSPL-1.0 Yes Details →
6.1.10 03 Apr 2025 H2 SSPL-1.0 Yes Details →
6.0.13 05 Mar 2025 H3 SSPL-1.0 Yes Details →
6.1.8 05 Mar 2025 H2 M1 SSPL-1.0 Yes Details →
6.0.12 17 Feb 2025 H3 SSPL-1.0 Yes Details →
6.1.7 17 Feb 2025 H2 M1 SSPL-1.0 Yes Details →
6.0.11 05 Feb 2025 H3 SSPL-1.0 Yes Details →
6.1.6 05 Feb 2025 H2 M1 SSPL-1.0 Yes Details →
6.0.10 08 Jan 2025 H3 SSPL-1.0 Yes Details →
6.1.5 08 Jan 2025 H2 M1 SSPL-1.0 Yes Details →
6.0.9 04 Dec 2024 H3 SSPL-1.0 Yes Details →
6.1.4 04 Dec 2024 H2 M1 SSPL-1.0 Yes Details →
6.0.8 06 Nov 2024 H3 SSPL-1.0 Yes Details →
6.1.2 06 Nov 2024 H2 M1 SSPL-1.0 Yes Details →
6.1.1 23 Oct 2024 H2 M1 SSPL-1.0 Yes Details →
6.1.0 18 Oct 2024 H2 M1 SSPL-1.0 Yes Details →
5.2.12 02 Oct 2024 H3 SSPL-1.0 Yes Details →
6.0.7 02 Oct 2024 H3 SSPL-1.0 Yes Details →
6.0.6 04 Sep 2024 H3 SSPL-1.0 Yes Details →
5.2.11 04 Sep 2024 H3 SSPL-1.0 Yes Details →
5.2.10 07 Aug 2024 H3 SSPL-1.0 Yes Details →
6.0.5 07 Aug 2024 H3 SSPL-1.0 Yes Details →
5.2.9 03 Jul 2024 H3 SSPL-1.0 Yes Details →
6.0.4 03 Jul 2024 H3 SSPL-1.0 Yes Details →
5.2.8 05 Jun 2024 H3 SSPL-1.0 Yes Details →
6.0.3 05 Jun 2024 H3 SSPL-1.0 Yes Details →
6.0.2 22 May 2024 H3 SSPL-1.0 Yes Details →
6.0.1 13 May 2024 H3 SSPL-1.0 Yes Details →
6.0.0 06 May 2024 H3 SSPL-1.0 Yes Details →
5.2.7 30 Apr 2024 H3 SSPL-1.0 Yes Details →
5.1.13 03 Apr 2024 H3 SSPL-1.0 Yes Details →
5.2.6 03 Apr 2024 H3 SSPL-1.0 Yes Details →
5.1.12 06 Mar 2024 H3 SSPL-1.0 Yes Details →
5.2.5 06 Mar 2024 H3 SSPL-1.0 Yes Details →
5.2.4 07 Feb 2024 H3 SSPL-1.0 Yes Details →
5.1.11 07 Feb 2024 H3 — Yes Details →
5.2.3 03 Jan 2024 H3 — Yes Details →
5.1.10 03 Jan 2024 H4 M1 — Yes Details →
5.2.2 06 Dec 2023 H3 — Yes Details →
5.1.9 06 Dec 2023 H4 M1 — Yes Details →
5.2.1 15 Nov 2023 H3 — Yes Details →
5.1.8 01 Nov 2023 H4 M1 — Yes Details →
5.2.0 30 Oct 2023 H3 — Yes Details →
5.2.0-rc.2 26 Oct 2023 H3 — Yes Details →
5.2.0-rc.1 23 Oct 2023 H3 — Yes Details →
5.2.0-beta.3 17 Oct 2023 H3 — Yes Details →
5.2.0-beta.2 12 Oct 2023 H3 — Yes Details →
5.0.13 12 Oct 2023 H4 M1 — Yes Details →
5.1.7 12 Oct 2023 H4 M1 — Yes Details →
5.0.12 04 Oct 2023 H4 M1 — Yes Details →
5.1.6 04 Oct 2023 H4 M1 — Yes Details →
5.2.0-beta.1 02 Oct 2023 H3 — Yes Details →
5.2.0-alpha.1 27 Sep 2023 H3 — Yes Details →
5.0.11 06 Sep 2023 H4 M1 — Yes Details →
5.1.5 06 Sep 2023 H4 M1 — Yes Details →

The newest 120 of 378 versions Vulert tracks. Severity counts are the vulnerabilities recorded against that exact release.

02 Disclosure history

How often vulnerabilities are recorded

  • 2022 3
  • 2023 3
  • 2024 2
  • 2025 4
  • 2026 4

Counted by the year Vulert recorded each vulnerability — the same date the table below shows as disclosed. 4 of the 16 were recorded in the last 12 months.

Vulnerability wrong, a fix missing, or a package we should cover? Report it and we will fix the record. Report Vulnerability Provide Feedback

Updated: 23/Oct/2026 · Vulnerabilities in our DB: 524315

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →

Questions

About org.graylog2:graylog2-server

Is org.graylog2:graylog2-server safe to use?

Vulert records 16 vulnerabilities for org.graylog2:graylog2-server in Maven: 0 critical, 5 high, 8 medium and 3 low. Every one of them has a published fix, so the practical answer is to run a supported release and keep it patched.

What is org.graylog2:graylog2-server's Vulert package health score?

Vulert scores org.graylog2:graylog2-server 71/100, which reads as in good shape. The score weighs the vulnerability record (40), maintenance and release cadence (25), adoption from dependents and stars (20) and community signals such as the OpenSSF scorecard and forks (15).

Is the latest version of org.graylog2:graylog2-server affected?

No. 7.2.1, the version you would install today, has no vulnerabilities on record against it. Earlier releases do — the version table above lists each release with what affects it.

How many vulnerabilities does org.graylog2:graylog2-server have?

16 vulnerabilities are recorded for org.graylog2:graylog2-server in the Maven ecosystem: 0 critical, 5 high, 8 medium and 3 low. The ledger on this page lists the same counts next to the date of the most recent disclosure.

How often are new org.graylog2:graylog2-server vulnerabilities disclosed?

4 vulnerabilities were recorded for org.graylog2:graylog2-server in the last 12 months, and the oldest entry in this database dates to 14 May 2022. Recency matters more than a lifetime total: it shows how actively new issues are being disclosed for the package you are considering.

Which versions of org.graylog2:graylog2-server are affected?

Each vulnerability on this page lists the affected version range and the fixed version to move to. Open the vulnerability for the version you actually run — fixes are specific to a release line, not to the package as a whole.

How do I monitor org.graylog2:graylog2-server for upcoming vulnerabilities?

Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the org.graylog2:graylog2-server version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.