VYPR
Medium severity5.9NVD Advisory· Published Jun 9, 2026

CVE-2026-41841

CVE-2026-41841

Description

Spring Framework versions 7.0.x, 6.2.x, 6.1.x, and 5.3.x are vulnerable to information disclosure when resolving static resources.

AI Insight

LLM-synthesized narrative grounded in this CVE's description and references.

Spring Framework versions 7.0.x, 6.2.x, 6.1.x, and 5.3.x are vulnerable to information disclosure when resolving static resources.

Vulnerability

Spring MVC and WebFlux applications are vulnerable to information disclosure when resolving static resources. This occurs when an application uses Spring MVC or WebFlux, has multiple resource handlers with different locations, at least one handler requires authentication, and a shared cache is configured for these handlers. Affected versions include 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 [1].

Exploitation

An attacker can exploit this vulnerability by first triggering the resolution of a publicly available resource with a specific name. If this resource is cached, and then a protected resource with the same name is resolved, the attacker can gain access to the protected resource. This attack does not require authentication or specific network positioning, but relies on the specific configuration of resource handlers and caching [1].

Impact

Successful exploitation of this vulnerability allows an attacker to disclose sensitive information by gaining unauthorized access to protected resources that should otherwise require authentication. The scope of the compromise is limited to the resources accessible through the misconfigured static resource handling [1].

Mitigation

Users of affected Spring Framework versions should upgrade to the following fixed versions: 7.0.8, 6.2.19, 6.1.28, or 5.3.49, depending on the specific branch. No further mitigation steps are necessary beyond upgrading [1].

AI Insight generated on Jun 9, 2026. Synthesized from this CVE's description and the cited reference URLs; citations are validated against the source bundle.

Affected products

3

Patches

0

No patches discovered yet.

Vulnerability mechanics

No source-code context for this CVE — mechanics is only generated when we can read the actual fix diff. Without that, the four sections (root cause, attack vector, affected code, fix) would be speculation rather than analysis.

References

1

News mentions

1