dbcve.org
Spring Data CommonsFramework / library · Broadcom

CVE-2026-41716

HIGH · 7.5 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 →
84/100
Remediation priority · High
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's internal property-lookup cache accepts and permanently retains attacker-supplied strings as cache keys, allowing heap exhaustion through repeated requests. Affected versions: Spring Data Commons 2.7.0 through 2.7.19; 3.3.0 through 3.3.16; 3.4.0 through 3.4.14; 3.5.0 through 3.5.11; 4.0.0 through 4.0.5.

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 an internal property-lookup cache that improperly accepts attacker-controlled strings as cache keys and retains them indefinitely, enabling an attacker to repeatedly send unique strings to exhaust heap memory and cause a denial of service.

MitigationUpgrade Spring Data Commons to version 2.7.20, 3.3.17, 3.4.15, 3.5.12, or 4.0.6 or later, which implement bounds on the cache or sanitize input.

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.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
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

CVSS:3.1/AV:N/AC:L/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 dependency
    Search your project build files (pom.xml, build.gradle) or the application's classpath for the spring-data-commons JAR. List all JAR files containing 'spring-data-commons' in the lib or lib directory.
    Affected if The spring-data-commons library is present in your application runtime
  2. Determine installed version
    Extract the version from the JAR file name (spring-data-commons-X.X.X.jar) or check the MANIFEST.MF file inside the JAR. If using Maven/Gradle, run 'mvn dependency:list' or 'gradle dependencies' and filter for spring-data-commons.
    Affected if The version falls within any of these ranges: 2.7.0 to 2.7.19, 3.3.0 to 3.3.16, 3.4.0 to 3.4.14, 3.5.0 to 3.5.11, or 4.0.0 to 4.0.5
  3. Check for Spring Data repository usage
    Review your codebase for interfaces extending Repository, CrudRepository, PagingAndSortingRepository, or JpaRepository from org.springframework.data.repository. Also search for usages of PropertyPath or related property lookup APIs.
    Affected if Your application uses Spring Data repository interfaces or property path resolution that triggers the vulnerable cache
  4. Identify exposed endpoints accepting string input
    Review controller or service code for endpoints that accept arbitrary string parameters (path variables, query parameters, request body fields) which could be passed to repository queries or property lookups. Focus on endpoints that directly use input in findBy, getBy, or property access patterns.
    Affected if The application has REST endpoints or APIs that accept user-supplied strings and pass them to Spring Data query methods or property resolution

You are affected if your application uses a vulnerable version of Spring Data Commons AND exposes endpoints that accept attacker-controlled strings which get processed by Spring Data repositories or property lookup APIs.

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 version 2.7.20, 3.3.17, 3.4.15, 3.5.12, or 4.0.6 or later, which implement bounds on the cache or sanitize input.

Recommended fix High confidence

Spring Data Commons 2.7.20, 3.3.17, 3.4.15, or 3.5.11.1 (depending on your current major.minor line)

  1. Identify the current Spring Data Commons version in your project's dependency management (pom.xml, build.gradle, or Maven/Gradle wrapper)
  2. Upgrade Spring Data Commons to the appropriate fixed version based on your current major.minor line: for 2.7.x upgrade to 2.7.20, for 3.3.x upgrade to 3.3.17, for 3.4.x upgrade to 3.4.15, for 3.5.x upgrade to 3.5.11.1
  3. If using Spring Boot, ensure you upgrade to a compatible Spring Boot version that bundles the fixed Spring Data Commons release
  4. Rebuild and test the application to verify the upgrade does not introduce regressions
  5. Deploy the updated application
Caveat Minor version upgrades within the same major.minor line typically have minimal breaking changes; however, review the Spring Data release notes for any deprecation notices or behavioral changes between your current version and the target fixed version

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
  • Implementation2.0 h
  • Testing4.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,720
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-41716 — 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-41716 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