dbcve.org
Spring Data CommonsFramework / library · Broadcom

CVE-2026-41721

MEDIUM · 5.9 CVSS v3.1 Published 2026-06-10
Fix available
A fix is available. Upgrade to 2.7.20 / 3.3.17 or later.
See remediation →
68/100
Remediation priority · Elevated
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Spring Data Commons contains a vulnerability that can lead to a Denial of Service (DoS) condition if Spring Data Web Support is enabled in conjunction with a Controller method using @ProjectedPayload, when an attacker sends a specially crafted HTTP request that causes the application to allocate lots of memory. Affected versions: Spring Data Commons 4.0.0 through 4.0.5; 3.5.0 through 3.5.11; 3.4.0 through 3.4.14; 3.3.0 through 3.3.16; 3.2.0 through 3.2.15; 3.1.0 through 3.1.14; 3.0.0 through 3.0.15; 2.7.0 through 2.7.19.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

Spring Data Commons contains a DoS vulnerability where a specially crafted HTTP request targeting a Controller method annotated with @ProjectedPayload (with Spring Data Web Support enabled) causes excessive memory allocation, potentially leading to service unavailability.

MitigationUpgrade Spring Data Commons to a patched version, or disable Spring Data Web Support if @ProjectedPayload functionality is not required.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Spring Data CommonsFramework / library
Affected:>= 2.7.0, < 2.7.20>= 3.0.0, <= 3.0.15>= 3.1.0, <= 3.1.14>= 3.2.0, <= 3.2.15>= 3.3.0, < 3.3.17>= 3.4.0, < 3.4.15>= 3.5.0, < 3.5.11.1>= 4.0.0, < 4.0.5.1

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
High
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify Spring Data Commons version
    Inspect your project's dependency management file (Maven pom.xml, Gradle build.gradle, or a dependency report). Look for the spring-data-commons artifact and note its version number.
    Affected if The installed version falls within any of these ranges: >= 2.7.0 and < 2.7.20; >= 3.0.0 and <= 3.0.15; >= 3.1.0 and <= 3.1.14; >= 3.2.0 and <= 3.2.15; >= 3.3.0 and < 3.3.17; >= 3.4.0 and < 3.4.15; >= 3.5.0 and < 3.5.11.1; >= 4.0.0 and < 4.0.5.1
  2. Confirm Spring Data Web Support is enabled
    Check your project dependencies for spring-data-web, spring-boot-starter-data-web, or any dependency that pulls in Spring Data Web support modules. Also inspect your application's configuration files for any explicit enablement of Spring Data Web features.
    Affected if Spring Data Web Support is present on the classpath or explicitly enabled in configuration, and the Spring Data Commons version is vulnerable as identified in the previous step.
  3. Locate @ProjectedPayload usage
    Search your codebase for any classes, interfaces, or methods annotated with @ProjectedPayload, particularly those used in controller method parameters or request handling components.
    Affected if @ProjectedPayload is used on any controller methods or endpoints, combined with the vulnerable Spring Data Commons version and Spring Data Web Support being enabled.

You are affected if your environment uses a vulnerable Spring Data Commons version AND has Spring Data Web Support enabled AND exposes endpoints using @ProjectedPayload to untrusted HTTP requests.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 2.7.20 / 3.3.17 / 3.4.15 or later
Fixed in 2.7.203.3.173.4.15
Interim mitigation

Upgrade Spring Data Commons to a patched version, or disable Spring Data Web Support if @ProjectedPayload functionality is not required.

Recommended fix High confidence

Upgrade to Spring Data Commons 2.7.20, 3.0.16, 3.1.15, or 3.2.16 (or later) depending on your current branch

  1. 1. Identify the current version of Spring Data Commons in your project by checking your Maven pom.xml or Gradle build.gradle file.
  2. 2. Determine which version branch your current installation belongs to (2.7.x, 3.0.x, 3.1.x, or 3.2.x).
  3. 3. For Spring Data Commons 2.7.x: Upgrade to version 2.7.20 or later.
  4. 4. For Spring Data Commons 3.0.x: Upgrade to version 3.0.16 or later.
  5. 5. For Spring Data Commons 3.1.x: Upgrade to version 3.1.15 or later.
  6. 6. For Spring Data Commons 3.2.x: Upgrade to version 3.2.16 or later.
  7. 7. If using Spring Boot, update the Spring Data Commons version via the spring-boot-dependencies BOM or by explicitly setting the version in your build configuration.
  8. 8. Rebuild and test your application to ensure the upgrade does not introduce regressions.
Caveat Minor; patch releases typically contain only bug and security fixes with no breaking API changes

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Spring Data Commons Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing6.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,380
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,808.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-41721 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-41721 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data