Skip to content

GHSA-vqgp-pf68-6947 CVE-2026-41847

Spring Framework Security Filter Bypass in WebFlux Kotlin Router DSL

Medium Maven
Severity
4.8 / 10
Medium · CVSS 3.1
Exploit chance (EPSS)
0.17%
Chance of exploitation in the next 30 days. Higher than 5.86% of scored vulnerabilities.
Known exploited
No
Not in CISA's catalog
Weakness
CWE-284 Improper Access Control
Fix
None yet
No fixed version published

Description

Spring WebFlux applications may be vulnerable to a security bypass when using the Kotlin Router DSL.

Affected versions: Spring Framework 5.3.0 through 5.3.48.

Affected versions

Maven

PackageVulnerableFixed in
org.springframework:spring-webflux
<= 5.3.39
No fix yet

How to fix

No fixed version has been published yet. Until one is, remove or replace the package, or turn off or isolate the affected feature. This page updates when a fix ships.

Severity breakdown

CVSS 3.1 4.8

CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:N

Attack vector
Network
Attack complexity
High
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
Low
Availability
None

Weakness

CWE-284: Improper Access Control

The product does not restrict or incorrectly restricts access to a resource from an unauthorized actor.

How to prevent it
  • Architecture and Design, Operation: Very carefully manage the setting, management, and handling of privileges. Explicitly manage trust zones in the software.
  • Architecture and Design: Compartmentalize the system to have "safe" areas where trust boundaries can be unambiguously drawn. Do not allow sensitive data to go outside of the trust boundary and always be careful when interfacing with a compartment outside of the safe area. Ensure that appropriate compartmentalization is built into the system design, and the compartmentalization allows for and reinforces privilege separation functionality. Architects and designers should rely on the principle of least privilege to decide the appropriate time to use privileges and the time to drop privileges.

References

Timeline

  1. Published
  2. Last updated by the source
  3. Latest EPSS score
AdvisorySeverityWhy it's related
GHSA-36p3-wjmg-h94x
Remote Code Execution in Spring Framework
Critical Known exploited Also affects org.springframework:spring-webflux
GHSA-9qf2-26p9-2q2q
Spring Framework Header Predicate Bypass in WebFlux Functional Endpoints
Critical Also affects org.springframework:spring-webflux
GHSA-j9f9-w8pj-32f8
Spring Framework Server Sent Event stream corruption while rendering fragments
Critical Also affects org.springframework:spring-webflux
GHSA-cjpg-rgq5-fr37
Spring Framework Multipart Request Smuggling in Spring MVC and WebFlux
Medium Also affects org.springframework:spring-webflux
GHSA-h3qp-gqrc-q736
Spring Framework Open Redirect in Spring MVC and WebFlux
Medium Also affects org.springframework:spring-webflux
GHSA-72pg-x5f8-j25j
Spring Framework Path Traversal via Versioned Static Resources in Spring MVC and WebFlux
Medium Also affects org.springframework:spring-webflux
GHSA-x23c-287f-qqv5
Spring Framework Denial of Service via Versioned Resources in Spring MVC and WebFlux
High Also affects org.springframework:spring-webflux
GHSA-mq64-j8f9-9gcj
Spring Framework Information Disclosure via Static Resource Cache in Spring MVC and WebFlux
Medium Also affects org.springframework:spring-webflux
Is this in your code?

MergeHarbor checks every repository's dependencies against this database, ranks what matters by exploitability and reachability, routes it to the owning team and opens the fix pull request.

Check your repos with MergeHarbor