CVE-2026-41695
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 · uneditedSpring Data Commons applications may be vulnerable to denial of service through resource exhaustion when attacker-controlled property path strings are passed to MappingContext property path resolution. 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.
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 confidenceSpring Data Commons contains a denial of service vulnerability in MappingContext property path resolution. When attacker-controlled property path strings are passed to the property path resolution mechanism, it can lead to resource exhaustion, potentially causing the application to become unresponsive or crash.
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>= 3.4.0, < 3.4.15>= 3.5.0, < 3.5.11.1>= 4.0.0, < 4.0.5.1CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Identify Spring Data Commons versionInspect your project's dependency manifest: for Maven check pom.xml for 'spring-data-commons' dependency, for Gradle check build.gradle. Alternatively, list the spring-data-commons jar in your application's classpath and check the MANIFEST.MF file for the Implementation-Version attribute.Affected if The version falls within 3.4.0-3.4.14, 3.5.0-3.5.11, or 4.0.0-4.0.5.
-
Confirm MappingContext is in useSearch your codebase for imports and usage of org.springframework.data.mapping.context.MappingContext, or classes that extend or use it such as PersistentEntity or PersistentProperty implementations.Affected if MappingContext is loaded and initialized in the application runtime.
-
Identify property path input entry pointsSearch source code for endpoints, methods, or parameters that accept property path strings. Look for usage of PropertyPath, PathAccessor, or similar APIs from org.springframework.data.util package that process dynamic property paths.Affected if User-controlled or external input can reach property path resolution logic without validation.
-
Check for property path resolution in repositoriesInspect Spring Data repository implementations, particularly those using SpEL expressions in @Query annotations or custom query methods that accept dynamic property references. Review any code using SpelExpression or similar expression parsers with external input.Affected if Repository methods accept property path strings from request parameters or external sources.
The environment is affected if Spring Data Commons version is 3.4.0-3.4.14, 3.5.0-3.5.11, or 4.0.0-4.0.5 AND the application exposes endpoints or APIs that pass unsanitized property path strings to Spring Data's mapping resolution logic.
Generated from the published advisory. Verify against your own configuration.
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 · scoped3.4.153.5.11.14.0.5.1
Upgrade Spring Data Commons to version 4.0.6+, 3.5.12+, or 3.4.15+ to receive the patch. If immediate patching is not possible, implement input validation to restrict property path strings to expected patterns and limit their complexity before passing them to MappingContext.
Spring Data Commons 3.4.15, 3.5.11.1, or 4.0.5.1 (depending on your major version branch)
- Identify the current Spring Data Commons version in your project's dependency management (pom.xml, build.gradle, or similar)
- Update the Spring Data Commons version to the appropriate fixed release based on your current branch: 3.4.15+ for 3.4.x, 3.5.11.1+ for 3.5.x, or 4.0.5.1+ for 4.0.x
- Run mvn dependency:tree or gradle dependencies to verify the new version is resolved
- Rebuild the application and run full test suite to verify functionality
- If using Spring Boot, ensure the Spring Boot version manages Spring Data Commons to a compatible fixed version
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.0 h
- Testing8.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,288.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-41695 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-41695 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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