VulertSecurity VulertSecurity

Vulnerability Database · Maven · Package report

org.springframework.graphql:spring-graphql: vulnerability history, versions and safety

org.springframework.graphql:spring-graphql is a package in the Maven ecosystem. Vulert records 4 vulnerabilities for it across 10 releases, from Sep 2023 to Jun 2026. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
4 vulnerabilities recorded H3 L1
i
0 with no fix published

Every vulnerability has a patched version to move to.

i
3 in the last 12 months

Most recent disclosure 11 Jun 2026.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all org.springframework.graphql:spring-graphql vulnerabilities

Vulert verdict on org.springframework.graphql:spring-graphql 2.1.0-RC1 i

Updated on 23 Oct 2026

Good news: 2.1.0-RC1, the version you would install today, has no known vulnerabilities. Older releases do — the table below lists all 4.

Package health score 80/100
  • Security Minor issues
  • Maintenance Sustainable
  • Popularity Widely used
  • Community Moderate

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

  • Current release 2.1.0-RC1 — unaffected i
  • Vulnerabilities on record 4 over 2 years · 3 in the last year i
  • Latest disclosure 11 Jun 2026 i
  • Highest CVSS 8.1 i
  • With no published fix 0 i
  • Stars 1,597 i
  • Last release this month i
  • Licence Apache-2.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.springframework.graphql:spring-graphql, 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
2.0.6 22 Oct 2026 none Apache-2.0 — Details →
2.1.0-RC1 22 Oct 2026 none Apache-2.0 — Details →
2.1.0-M1 24 Sep 2026 none Apache-2.0 — Details →
2.0.5 20 Aug 2026 none Apache-2.0 — Details →
2.0.4 10 Jun 2026 none Apache-2.0 — Details →
1.4.6 10 Jun 2026 none Apache-2.0 — Details →
2.0.3 21 Apr 2026 H3 Apache-2.0 Yes Details →
1.4.5 15 Feb 2026 none Apache-2.0 — Details →
2.0.2 21 Jan 2026 H3 Apache-2.0 Yes Details →
1.3.7 16 Dec 2025 none Apache-2.0 — Details →
1.4.4 16 Dec 2025 none Apache-2.0 — Details →
2.0.1 16 Dec 2025 H3 Apache-2.0 Yes Details →
2.0.0 18 Nov 2025 H3 Apache-2.0 Yes Details →
2.0.0-RC2 04 Nov 2025 none Apache-2.0 — Details →
2.0.0-RC1 21 Oct 2025 none Apache-2.0 — Details →
1.4.3 21 Oct 2025 none Apache-2.0 — Details →
2.0.0-M3 16 Sep 2025 none Apache-2.0 — Details →
1.4.2 16 Sep 2025 none Apache-2.0 — Details →
2.0.0-M2 19 Aug 2025 none Apache-2.0 — Details →
2.0.0-M1 22 Jul 2025 none Apache-2.0 — Details →
1.4.1 26 Jun 2025 none Apache-2.0 — Details →
1.3.6 26 Jun 2025 none Apache-2.0 — Details →
1.4.0 20 May 2025 none Apache-2.0 — Details →
1.3.5 17 Apr 2025 none Apache-2.0 — Details →
1.3.4 18 Feb 2025 none Apache-2.0 — Details →
1.3.3 23 Oct 2024 none Apache-2.0 — Details →
1.2.9 22 Oct 2024 none Apache-2.0 — Details →
1.3.2 16 Jul 2024 none Apache-2.0 — Details →
1.2.8 16 Jul 2024 none Apache-2.0 — Details →
1.3.1 18 Jun 2024 none Apache-2.0 — Details →
1.2.7 18 Jun 2024 none Apache-2.0 — Details →
1.3.0 21 May 2024 none Apache-2.0 — Details →
1.2.6 28 Mar 2024 none Apache-2.0 — Details →
1.2.5 21 Feb 2024 none Apache-2.0 — Details →
1.2.4 21 Nov 2023 none Apache-2.0 — Details →
1.1.7 19 Sep 2023 none Apache-2.0 — Details →
1.0.6 19 Sep 2023 none Apache-2.0 — Details →
1.0.5 19 Sep 2023 none Apache-2.0 — Details →
1.1.6 19 Sep 2023 none Apache-2.0 — Details →
1.2.3 19 Sep 2023 none Apache-2.0 — Details →
1.2.2 18 Jul 2023 none Apache-2.0 — Details →
1.2.1 20 Jun 2023 none Apache-2.0 — Details →
1.1.5 20 Jun 2023 L1 Apache-2.0 Yes Details →
1.2.0 16 May 2023 none Apache-2.0 — Details →
1.1.4 16 May 2023 L1 Apache-2.0 Yes Details →
1.0.4 21 Mar 2023 none Apache-2.0 — Details →
1.1.3 21 Mar 2023 L1 Apache-2.0 Yes Details →
1.1.2 21 Feb 2023 L1 Apache-2.0 Yes Details →
1.1.1 20 Dec 2022 L1 Apache-2.0 Yes Details →
1.1.0 22 Nov 2022 L1 Apache-2.0 Yes Details →
1.0.3 22 Nov 2022 none Apache-2.0 — Details →
1.0.2 20 Sep 2022 none Apache-2.0 — Details →
1.0.1 20 Jul 2022 none Apache-2.0 — Details →
1.0.0 18 May 2022 none Apache-2.0 — Details →

All 54 versions Vulert tracks for this package. Severity counts are the vulnerabilities recorded against that exact release.

02 Disclosure history

How often vulnerabilities are recorded

  • 2023 1
  • 2026 3

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

03 Vulnerabilities

Recorded vulnerabilities for org.springframework.graphql:spring-graphql

The 4 most severe of 4 vulnerabilities recorded for this package

Search all 4 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2026-41700: Spring for GraphQL Cross-Site WebSocket Hijacking Vulnerability 8.1 high 2.0.4 11 Jun 2026
CVE-2026-41699: Spring for GraphQL Unsafe Deserialization Vulnerability 8.1 high 2.0.4 11 Jun 2026
CVE-2026-41856: Spring for GraphQL Annotation Detection Vulnerability 7.5 high 2.0.4 11 Jun 2026
CVE-2023-34047: Spring for GraphQL Exposed to GraphQL Context with Values from Different Session 3.1 low 1.1.6 20 Sep 2023

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.springframework.graphql:spring-graphql

Is org.springframework.graphql:spring-graphql safe to use?

Vulert records 4 vulnerabilities for org.springframework.graphql:spring-graphql in Maven: 0 critical, 3 high, 0 medium and 1 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.springframework.graphql:spring-graphql's Vulert package health score?

Vulert scores org.springframework.graphql:spring-graphql 80/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.springframework.graphql:spring-graphql affected?

No. 2.1.0-RC1, 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.springframework.graphql:spring-graphql have?

4 vulnerabilities are recorded for org.springframework.graphql:spring-graphql in the Maven ecosystem: 0 critical, 3 high, 0 medium and 1 low. The ledger on this page lists the same counts next to the date of the most recent disclosure.

How often are new org.springframework.graphql:spring-graphql vulnerabilities disclosed?

3 vulnerabilities were recorded for org.springframework.graphql:spring-graphql in the last 12 months, and the oldest entry in this database dates to 20 Sep 2023. 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.springframework.graphql:spring-graphql 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.springframework.graphql:spring-graphql for upcoming vulnerabilities?

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