cve.bz

CVE-2026-41695 broadcom spring data commons: Uncontrolled Resource Consumption

7.5 highEPSS 0.4%Fix available

High (7.5) in broadcom spring data commons. EPSS 0.4% estimated probability of exploitation activity in the next 30 days. Fixed in org.springframework.data:spring-data-commons 3.5.12, 4.0.6.

On this page
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.

Severity

CVSS 3.1

7.5 high
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
EPSS
0.4% (unchanged from 0.4% a week ago; 0.5% 30 days ago) estimated probability of exploitation activity in the next 30 days; 31st percentile. Scored 2026-11-22. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: yes · Technical impact: partial, assessed 2026-06-10. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-400 Uncontrolled Resource Consumption
Published
Modified
NVD analysis
Analyzed
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2026-41695 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-41695?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-41695?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-41695 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
Spring Data Commonsfrom 4.0.0 before 4.0.5.1
Spring Data Commonsfrom 3.5.0 before 3.5.11.1
Spring Data Commonsfrom 3.4.0 before 3.4.15

Packages (OSV)

AdvisoryEcosystemPackageAffectedFixed in
GHSA-88fw-v6x4-3f58Mavenorg.springframework.data:spring-data-commons>=4.0.0 <4.0.64.0.6
GHSA-88fw-v6x4-3f58Mavenorg.springframework.data:spring-data-commons>=3.5.0 <3.5.123.5.12
GHSA-88fw-v6x4-3f58Mavenorg.springframework.data:spring-data-commons>=3.4.0 <=3.4.13no fix published

Red Hat

Red Hat rates this Important.

Red Hat's statement

A flaw was found in Spring Data Commons. Crafted property path strings can trigger excessive processing, leading to denial of service. Red Hat products that bundle spring-data-commons and expose Spring Data query resolution to untrusted input are affected. In Red Hat Dev Spaces, the vulnerable code path is reachable only through admin-authenticated endpoints, limiting practical exploitability.

Red Hat's mitigation

Mitigation for this issue is either not available or the currently available options do not meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base or stability.

ProductPackageStateAdvisory
Red Hat OpenShift Dev Spaces 3.30devspaces/openvsx-rhel9:1787759145Fixed 2026-09-01RHSA-2026:62260
Red Hat OpenShift Dev Spaces 3.30devspaces/pluginregistry-rhel9:1787759723Fixed 2026-09-01RHSA-2026:62260
Red Hat Data Grid 8spring-data-commonsNot affected
Red Hat Fuse 7spring-data-commonsWill not fix
Red Hat JBoss Enterprise Application Platform Expansion Packspring-data-commonsNot affected

Contains Red Hat Security Data © Red Hat, Inc., licensed under CC BY 4.0. Source: https://access.redhat.com/security/data. Modified: reformatted. Red Hat's page for CVE-2026-41695.

Attack patterns (CAPEC)

  • CAPEC-147 XML Ping of the Death Likelihood: Low · Severity: Medium
  • CAPEC-227 Sustained Client Engagement
  • CAPEC-492 Regular Expression Exponential Blowup

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

References

Check your stackJSON