CVE-2026-41721
Last modified
CVE-2026-41721 is a medium-severity vulnerability rated 5.9/10 on the CVSS scale. 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.. EPSS estimates a 0.33% chance of exploitation in the next 30 days.
Description
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.
Metrics
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H
Weakness Enumeration
Affected Software
| Vendor | Product | Versions |
|---|---|---|
| Broadcom | Spring Data Commons | >= 2.7.0, < 2.7.20 |
| Broadcom | Spring Data Commons | >= 3.0.0, <= 3.0.15 |
| Broadcom | Spring Data Commons | >= 3.1.0, <= 3.1.14 |
| Broadcom | Spring Data Commons | >= 3.2.0, <= 3.2.15 |
| Broadcom | Spring Data Commons | >= 3.3.0, < 3.3.17 |
| Broadcom | Spring Data Commons | >= 3.4.0, < 3.4.15 |
| Broadcom | Spring Data Commons | >= 3.5.0, < 3.5.11.1 |
| Broadcom | Spring Data Commons | >= 4.0.0, < 4.0.5.1 |
References
- https://spring.io/security/cve-2026-41721Vendor Advisory
Timeline
- Published
- Last Modified
- Status
- Analyzed
Frequently Asked Questions
What is CVE-2026-41721?
How severe is CVE-2026-41721?
How do I fix CVE-2026-41721?
How Strix Helps
- How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2026
- CVE-2026-41715In specific scenarios involving HTTP redirects from a secure…6.1
- CVE-2026-41716Spring Data's internal property-lookup cache accepts and per…7.5
- CVE-2026-41717Spring Data MongoDB contains a SpEL (Spring Expression Langu…8.1
- CVE-2026-41719A SpEL Injection vulnerability exists in the Spring Data Key…6.4
- CVE-2026-4172A vulnerability was detected in TRENDnet TEW-632BRP 1.010B32…7.3
- CVE-2026-41720Spring LDAP's DirContextAuthenticationStrategy implementatio…7.4
- CVE-2026-41722VMware Cloud Foundation Operations contains multiple stored …5.4
- CVE-2026-41723VMware Cloud Foundation Operations contains multiple stored …8
- CVE-2026-41724VMware Cloud Foundation Operations contains multiple stored …5.4
- CVE-2026-41726When an application opts into DelegatingDeserializer, a prod…6.5
- CVE-2026-41727Spring Kafka's retry topic infrastructure did not sufficient…6.5
- CVE-2026-41728Spring Data REST's JSON Patch (application/json-patch+json) …7.5
Are you affected by CVE-2026-41721?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST