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

Information Disclosure via Static Resource Cache in Spring MVC and WebFlux

IdentifiersCVE-2026-41841CWE-200

CVE-2026-41841 is an information disclosure vulnerability in Spring Framework affecting Spring MVC and Spring WebFlux applications during static resource resolution. The issue arises when an application defines multiple resource handlers with different resource locations, at least one of those handlers protects resources with authentication, and the handlers share a cache. Under those conditions, if a publicly accessible resource is resolved first and cached, an attacker may subsequently obtain a protected resource with the same name from the shared cache. 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 may also be 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 unauthorized access to protected static resources that should require authentication. The impact is confidentiality loss only: an unauthenticated remote attacker may retrieve cached assets from protected resource locations when a same-named public resource was previously resolved and stored in the shared cache. The referenced CVSS v3.1 vector indicates high confidentiality impact with no integrity or availability impact.

Mitigation

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

According to the provided Spring advisory context, no additional mitigation steps are necessary beyond upgrading to a fixed version. If immediate patching is not possible, reducing or eliminating shared caching across differently protected static resource handlers may reduce exposure, but this was not stated by the vendor as an official mitigation.

Remediation

Patch, then assume compromise.

Upgrade Spring Framework to a fixed release appropriate for the deployed branch. Reported fixed versions are 7.0.8 for 7.0.x OSS users, 6.2.19 for 6.2.x OSS users, 7.0.7.1 for 7.0.x commercial users, 6.2.18.1 for 6.2.x commercial users, 6.1.28 for 6.1.x commercial users, and 5.3.49 for 5.3.x commercial users. Unsupported versions should be migrated 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 Frameworkapplication

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.