Skip to main content
Mallory
High

Denial of Service via Versioned Static Resource Resolution in Spring MVC and WebFlux

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

CVE-2026-41842 is a denial-of-service vulnerability in Spring Framework affecting Spring MVC and Spring WebFlux applications during static resource resolution. According to the provided content, the issue is triggered when applications serve static resources from the file system and have versioned resource support enabled. Under those conditions, an attacker can send malicious requests that are slow to resolve, causing HTTP/server connections to remain occupied for extended periods while the framework processes versioned web asset lookups. The vulnerability affects Spring Framework 7.0.0 through 7.0.7, 6.2.0 through 6.2.18, 6.1.0 through 6.1.27, and 5.3.0 through 5.3.48, with unsupported versions also reported as 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 can exhaust available request-handling capacity by tying up server or HTTP connections, resulting in application-level denial of service. The provided content indicates this can lead to full platform unavailability for affected Spring MVC or WebFlux applications. The referenced CVSS v3.1 vector in the content is AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H, indicating a remotely exploitable high-availability impact without requiring authentication or user interaction.

Mitigation

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

The provided content states that no further mitigation steps are necessary beyond upgrading. Where immediate patching is not possible, the information currently available does not provide an official vendor mitigation or workaround.

Remediation

Patch, then assume compromise.

Upgrade Spring Framework to a fixed release appropriate for the deployed branch. Based on the provided content, fixes are available in Spring Framework 7.0.8 for OSS users (or 7.0.7.1 commercial), 6.2.19 for OSS users (or 6.2.18.1 commercial), 6.1.28 through a commercial release, and 5.3.49 through a commercial release. Unsupported versions are also affected and should be migrated to a supported fixed version.
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.

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 activity4

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