Evidence used
- No CISA KEV confirmation is currently recorded.
- The selected CVSS metric records a network-reachable, unauthenticated path with no user interaction.
- EPSS is 0.46% for the current model date.
BlackTreeCVE IntelligenceFull vulnerability report · 2026
CVE-2026-41695High confidence
Denial of Service in Spring Data Commons Property Path Resolution
Spring · Spring Data Commons
7.5HighCVSS 3.1
Within 7 days
Patch availableHigh technical severity; prioritise exposed affected systems while verifying vendor guidance.
R
Open reassessment dashboard →Operational reassessment
Published severity in operational context
Published severityHigh→Operational priority:High, unchanged from published severity.unchanged
Compensating controls
- Validate the affected product branch and deploy the verified fixed release.
- Restrict the affected network interface to trusted sources where business-safe.
- Monitor vendor guidance and exploitation sources for a material change.
Verification
- Confirm that the asset runs Spring Spring Data Commons and falls inside the recorded affected range.
- Verify the installed build against the product-specific fixed version after deployment.
- Validate exposure, authentication requirements and compensating controls in the actual environment.
- Reopen this reassessment when CVSS, KEV, EPSS, exploit evidence or remediation changes.
Open-source package ranges6 source-attributed ranges
These OSV and GitHub advisory ranges apply only to the named package and ecosystem. A listed fixed version is not a universal product patch or proof that an update is installed.
| Ecosystem and package | Affected range | First fixed version | Evidence |
|---|---|---|---|
| Mavenorg.springframework.data:spring-data-commons | ECOSYSTEM: introduced 4.0.0; fixed 4.0.6 | 4.0.6 | OSV record ↗aggregator derived · 10 Sep 2026 |
| Mavenorg.springframework.data:spring-data-commons | ECOSYSTEM: introduced 3.5.0; fixed 3.5.12 | 3.5.12 | OSV record ↗aggregator derived · 10 Sep 2026 |
| Mavenorg.springframework.data:spring-data-commons | ECOSYSTEM: introduced 3.4.0; last affected 3.4.13 | Not stated | OSV record ↗aggregator derived · 10 Sep 2026 |
| mavenorg.springframework.data:spring-data-commons | >= 4.0.0, <= 4.0.5 | 4.0.6 | GitHub advisory ↗upstream repository advisory · 31 Jul 2026 |
| mavenorg.springframework.data:spring-data-commons | >= 3.5.0, <= 3.5.11 | 3.5.12 | GitHub advisory ↗upstream repository advisory · 31 Jul 2026 |
| mavenorg.springframework.data:spring-data-commons | >= 3.4.0, <= 3.4.13 | Not stated | GitHub advisory ↗upstream repository advisory · 31 Jul 2026 |
Direct vendor intelligence
1 currentAuthoritative vendor CSAF and VEX advisories
Structured product status and remediation from the issuing vendor. Product-state explanations are always visible; large lists can be searched or downloaded.
CVE-2026-41695 · CSAF 2.0 · revision 3 · finalRed Hat Product SecuritySpring Data Commons: Spring Data Commons: Denial of Service via crafted property path strings
The vendor explicitly identifies these products as affected by this CVE.
- spring-data-commons as a component of Red Hat Fuse 7
- Summary
- A flaw was found in Spring Data Commons. A remote attacker can exploit this vulnerability by providing specially crafted property path strings to the MappingContext property path resolution. This can lead to resource exhaustion, resulting in a denial of service (DoS) for affected applications.
- Remediation
- Before applying this update, make sure all previously released errata relevant to your system have been applied. For details on how to apply this update, refer to: https://access.redhat.com/articles/11258
High technical severity; prioritise exposed affected systems while verifying vendor guidance.
Patch available01
What, why and how
Spring 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.
What
Spring 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.
Why
The product does not properly control the allocation and maintenance of a limited resource.
How
An attacker operating through a network path may attempt exploitation without authentication or user interaction. If successful, the issue may disrupt the affected service.
What
Spring 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.
Why
The product does not properly control the allocation and maintenance of a limited resource.
How
An attacker operating through a network path may attempt exploitation without authentication or user interaction. If successful, the issue may disrupt the affected service.
02
Exploit reality and attack path
CVSS severity, EPSS forecast probability, public exploit material and CISA-confirmed exploitation are separate signals.
Observed exploitation No confirmed evidence
?
Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.No CISA KEV match was present at the last successful refresh. This means no confirmation from that source, not proof of no exploitation.
Public PoC / exploit material None recorded
?
Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.No exploit-tagged reference or CISA SSVC proof-of-concept state is currently recorded. Research may still exist outside the structured feeds.
- Likely attack path
- a network path → Uncontrolled Resource Consumption → disrupt the affected service
- Attack surface
- Network
- Privileges required
- None: unauthenticated exploitation is possible
- User interaction
- None
- Attack complexity
- Low: no specialised conditions are recorded
- Security boundary
- Unchanged: impact remains within the vulnerable component's security authority
- Weakness
?
CWE means Common Weakness Enumeration: a standard category for the underlying weakness. - CWE-400 ↗
CWE-400: Uncontrolled Resource Consumption. The product does not properly control the allocation and maintenance of a limited resource.
- CVSS vector
?
CVSS means Common Vulnerability Scoring System. The vector records the metric values used to calculate technical severity. CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:HCommon Vulnerability Scoring System 3.1: the compact vector below is decoded into plain language.
AVNetworkAttack vector: The vulnerable component can be reached over a network.ACLowAttack complexity: No specialised conditions are required beyond attacker-controlled input.PRNonePrivileges required: The attacker does not need an account or existing privileges.UINoneUser interaction: No action by another user is required.SUnchangedScope: The security impact remains within the vulnerable component's authority.CNoneConfidentiality impact: No direct loss is represented by this metric.INoneIntegrity impact: No direct loss is represented by this metric.AHighAvailability impact: A successful attack can cause a major loss.- Post-exploitation / living off the land
- No specific living-off-the-land technique is confirmed in the structured sources. Monitor normal administration tools for activity inconsistent with the affected service's baseline.
03
Patch and workaround
Operational remediation based on structured source evidence.
- Status
?
Patch availability is based on structured fixed-version fields and authoritative update references. If no fix is verified, check the vendor advisory before making a change. - Patch available
- Fixed
- registry.redhat.io/devspaces/openvsx-rhel9@sha256:560dd6062c5240e73ec60ecc13d402009b01e81ed452b6314c3817a2d116d575_amd64 as a component of Red Hat OpenShift Dev Spaces 3.30
- registry.redhat.io/devspaces/openvsx-rhel9@sha256:61a523a9663ff94b984f06fb72a570a18faf326b5efe6ef7d3ba55f96d4e422f_ppc64le as a component of Red Hat OpenShift Dev Spaces 3.30
- registry.redhat.io/devspaces/openvsx-rhel9@sha256:a4f8b673fd049befb193ee8f93ac8167b784cfe35b5de3584b19a95c726d9cff_s390x as a component of Red Hat OpenShift Dev Spaces 3.30
- registry.redhat.io/devspaces/openvsx-rhel9@sha256:b73b5fef7a238e3a16a0b724a8022588a4f69195743bf489f2bb01e4d3a59113_arm64 as a component of Red Hat OpenShift Dev Spaces 3.30
- registry.redhat.io/devspaces/pluginregistry-rhel9@sha256:121aee11bc25d5e983808691d3b82905048b5a67ffb01f61c86815867e4e8d08_amd64 as a component of Red Hat OpenShift Dev Spaces 3.30
- registry.redhat.io/devspaces/pluginregistry-rhel9@sha256:7ba97ebd86b3442cd95ffa2605b7890e2f85731ae84ee696d18bae0633439afe_s390x as a component of Red Hat OpenShift Dev Spaces 3.30
- registry.redhat.io/devspaces/pluginregistry-rhel9@sha256:9eccdaac68f3ce6a42a435ceb511483d0f233fb21b3dee8343b8d70cbd67f2ac_arm64 as a component of Red Hat OpenShift Dev Spaces 3.30
- registry.redhat.io/devspaces/pluginregistry-rhel9@sha256:f74ce43b7d8ade25e5b0f78a41f87db5c6005a85f48cde956b9a87a5892c3a87_ppc64le as a component of Red Hat OpenShift Dev Spaces 3.30
- Action
- Before applying this update, make sure all previously released errata relevant to your system have been applied. For details on how to apply this update, refer to: https://access.redhat.com/articles/11258
- Workaround
- No verified workaround is recorded. If business-safe, reduce exposure to the affected interface and allow only trusted sources until authoritative guidance is available.
04
Evidence and provenance
Published 9 Jun 2026 · Last source change 27 Jun 2026, 21:31 UTC · CWE-400 · Uncontrolled Resource Consumption
CVE recordCVE.org · 5.2
CVSS sourceCNA
EPSS source FIRST · tracked since 2026-08-14
?
The date BlackTree first stored a score for this CVE from the daily FIRST EPSS feed.European sourceENISA EUVD · EUVD-2026-35891
Product sourceVendor CSAF · Red Hat Product Security
Remediation sourceVendor CSAF · Red Hat Product Security
CWE sourceCNA
NVD statusNVD enriched
Core structured fields are present and their contributing authorities are shown above.
Material change intelligence
View recent updates ↗What changed after publication
- Affected versionsThe structured affected or fixed version information changed.Red Hat Product Security ↗
- Before
- 4.0.0 < 4.0.5.1; 3.5.0 < 3.5.11.1; 3.4.0 < 3.4.15 · Fixed: No fixed version is explicitly recorded in the structured CVE data.
- After
- 4.0.0 < 4.0.5.1; 3.5.0 < 3.5.11.1; 3.4.0 < 3.4.15 · Fixed: Before applying this update, make sure all previously released errata relevant to your system have been applied. For details on how to apply this update, refer to: https://access.redhat.com/articles/11258
- Remediation statusRemediation status changed from Awaiting fix to Patch available.Red Hat Product Security ↗
- Before
- Awaiting fix
- After
- Patch available
CVE published
Fixed release recorded from official guidance
Technical terms and abbreviations used in this report
- CVE
- Common Vulnerabilities and Exposures: the public identifier for one disclosed vulnerability.
- CVSS
- Common Vulnerability Scoring System: a technical severity framework; it is not patching priority by itself.
- EPSS
- Exploit Prediction Scoring System: FIRST's estimate of the probability that exploitation activity will be observed in the next 30 days; it is a forecast, not confirmation.
- CWE
- Common Weakness Enumeration: the standard category describing the underlying software or hardware weakness.
- CNA
- CVE Numbering Authority: an organisation authorised to assign and publish CVE records.
- CISA ADP
- Cybersecurity and Infrastructure Security Agency Authorized Data Publisher: structured enrichment added to a CVE record.
- NVD
- National Vulnerability Database: NIST's enrichment service for CVE records.
- CERT / CSIRT
- A computer security incident response team that publishes warnings or coordinates incident response.
- PoC
- Proof of concept: public material that demonstrates or helps reproduce exploitation.
- CSAF
- Common Security Advisory Framework: a machine-readable format for security advisories.
- LoTL
- Living off the land: abuse of legitimate tools or system functions during an attack.