Skip to main content
Live Webinar with SANS (June 25)— Agentic CTI Automation for Fun & ProfitRegister Free
Mallory
Medium

Spring Data Commons DoS via @ProjectedPayload memory allocation

IdentifiersCVE-2026-41721CWE-400· Uncontrolled Resource Consumption

CVE-2026-41721 is a denial-of-service vulnerability in Spring Data Commons. The issue is exposed when Spring Data Web Support is enabled and an application has a controller method using @ProjectedPayload. In that configuration, a specially crafted HTTP request can trigger excessive memory allocation during request handling/data binding, causing the application to consume large amounts of memory. Affected versions are 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, and 2.7.0 through 2.7.19; older unsupported versions are also affected.

Share:
For your environment

Are you exposed to this one?

Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.

ANALYST BRIEF

Impact, mitigation & remediation

What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

Successful exploitation allows a remote, unauthenticated attacker to force the application to allocate excessive memory, potentially exhausting heap resources and degrading or terminating service availability. Based on the provided CVSS vector, the impact is limited to availability; no confidentiality or integrity impact is indicated.

Mitigation

If you can’t patch tonight, do this now.

If immediate patching is not possible, reduce exposure by disabling Spring Data Web Support where feasible or removing/avoiding controller methods that use @ProjectedPayload in exposed paths. Restrict unauthenticated access to affected endpoints and apply request-size/rate controls or upstream resource-limiting defenses to reduce the likelihood of memory-exhaustion attacks until patched.

Remediation

Patch, then assume compromise.

Upgrade Spring Data Commons to a fixed version for the relevant release line. The provided content identifies fixes in 4.0.6 and 3.5.12. For older supported branches, fixes are available via Enterprise Support in 3.4.15, 3.3.17, and 2.7.20. Older unsupported versions should be upgraded to a supported fixed release.
PUBLIC EXPLOITS

Exploits

No public exploits tracked yet. Mallory keeps watching.

VALID 0 / 0 TOTALView more in app

No public exploit code observed for this vulnerability.

EXPOSURE SURFACE

Affected products & vendors

Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.

VendorProductType
BroadcomSpring-Data-Commonsapplication

Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.

What this page doesn’t show

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, which detections to deploy, and what to do tonight.
Exposure mapping

Query your assets running an affected version, and investigate the blast radius.

Threat actor evidence

Every observed campaign linking this CVE to a named adversary.

Associated malware

Malware families riding this exploit, with evidence and IOCs.

Detection signatures

YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.

Vendor-by-vendor mapping

Cross-references every affected SKU, including bundled OEM variants.

Social activity

Community discussion across Reddit, Mastodon, and other social sources.