VYPR
Medium severity4.8NVD Advisory· Published Jun 9, 2026

CVE-2026-41847

CVE-2026-41847

Description

Spring Framework 5.3.x applications using WebFlux Kotlin Router DSL can bypass security filters when ServerRequest is modified.

AI Insight

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

Spring Framework 5.3.x applications using WebFlux Kotlin Router DSL can bypass security filters when ServerRequest is modified.

Vulnerability

Spring Framework applications using WebFlux and the Kotlin Router DSL are vulnerable to a security bypass if they employ a filter that modifies or replaces the ServerRequest (e.g., using ServerRequestWrapper) before passing it to the next handler function. This issue affects Spring Framework versions 5.3.0 through 5.3.48 [1].

Exploitation

An attacker can exploit this vulnerability if the affected application meets all the conditions: uses Spring WebFlux, uses the Kotlin Router DSL, and uses a filter that modifies ServerRequest. The attacker does not need specific privileges or user interaction, as the security bypass occurs when the modified ServerRequest is silently discarded by the downstream handler, which receives the original, unmodified request instead [1].

Impact

When exploited, this vulnerability causes security-related modifications applied to the ServerRequest by a filter to have no effect. The downstream handler receives the original request, effectively bypassing intended security controls. This could lead to unauthorized access or actions that the security filter was designed to prevent [1].

Mitigation

Users of affected versions should upgrade to Spring Framework version 5.3.49, which addresses this vulnerability. This fix was made available commercially on June 8, 2026. 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

2

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