CVE-2026-41841 is an information disclosure vulnerability in Spring Framework static-resource resolution for Spring MVC and Spring WebFlux. It affects applications with multiple resource handlers that use different resource locations, where at least one handler serves authentication-protected resources and the handlers share a resource cache. If a publicly accessible resource is resolved and cached first, a requester may subsequently obtain a protected resource having the same name through the cached resolution result. Affected versions are 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; unsupported versions are also affected.
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.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
No public exploits tracked yet. Mallory keeps watching.
No public exploit code observed for this vulnerability.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
8 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
Unknown.
An information disclosure vulnerability in shared resource caching logic that may expose cached static assets to unauthorized users.
An information disclosure vulnerability in Spring Framework affecting Spring MVC and Spring WebFlux static resource resolution when multiple resource handlers with different locations share a cache, potentially allowing access to protected resources.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.