Skip to content

GHSA-j9f9-w8pj-32f8 CVE-2026-47890

Spring Framework Server Sent Event stream corruption while rendering fragments

Critical Maven
Severity
9.8 / 10
Critical · CVSS 3.1
Exploit chance (EPSS)
0.56%
Chance of exploitation in the next 30 days. Higher than 46.89% of scored vulnerabilities.
Known exploited
No
Not in CISA's catalog
Weakness
CWE-93 Improper Neutralization of CRLF Sequences ('CRLF Injection')
Fix
Available
2 packages have a fixed version

Description

Spring MVC and WebFlux applications are vulnerable to stream corruption when using Server-Sent Events (SSE) with view fragments. Spring Framework 7.0.0 - 7.0.8 Spring Framework 6.2.0 - 6.2.19

Affected versions

Maven

PackageVulnerableFixed in
org.springframework:spring-webflux
>= 6.2.0, <= 6.2.19
No fix yet
org.springframework:spring-webflux
>= 7.0.0, < 7.0.9
7.0.9
org.springframework:spring-webmvc
>= 6.2.0, <= 6.2.19
No fix yet
org.springframework:spring-webmvc
>= 7.0.0, < 7.0.9
7.0.9

How to fix

Move to the fixed version or later with your package manager, update the lockfile, and run your tests. If the package only arrives through another dependency, upgrade that dependency first. If none of its releases pulls a fixed version yet, force the version with your package manager's override.

org.springframework:spring-webflux Maven → 7.0.9

maven
<dependency><groupId>org.springframework</groupId><artifactId>spring-webflux</artifactId><version>7.0.9</version></dependency>
gradle
implementation("org.springframework:spring-webflux:7.0.9")

org.springframework:spring-webmvc Maven → 7.0.9

maven
<dependency><groupId>org.springframework</groupId><artifactId>spring-webmvc</artifactId><version>7.0.9</version></dependency>
gradle
implementation("org.springframework:spring-webmvc:7.0.9")

Severity breakdown

CVSS 3.1 9.8

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

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

Weakness

CWE-93: Improper Neutralization of CRLF Sequences ('CRLF Injection')

The product uses CRLF (carriage return line feeds) as a special element, e.g. to separate lines or records, but it does not neutralize or incorrectly neutralizes CRLF sequences from inputs.

How to prevent it
  • Implementation: Avoid using CRLF as a special sequence.
  • Implementation: Appropriately filter or quote CRLF sequences in user-controlled input.

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-pc63-qcmh-9cmg
Spring Framework Improper Path Limitation in XsltView
Critical Also affects org.springframework:spring-webmvc
GHSA-cjpg-rgq5-fr37
Spring Framework Multipart Request Smuggling in Spring MVC and WebFlux
Medium Also affects org.springframework:spring-webflux
GHSA-vqgp-pf68-6947
Spring Framework Security Filter Bypass in WebFlux Kotlin Router DSL
Medium Also affects org.springframework:spring-webflux
GHSA-957g-f97v-vppc
Spring Framework Cross-site Scripting via JSP Form Tags
Medium Also affects org.springframework:spring-webmvc
GHSA-3chg-m5w7-qfv5
Spring Framework Cross-site Scripting via JavaScriptUtils
Medium Also affects org.springframework:spring-webmvc
GHSA-h3qp-gqrc-q736
Spring Framework Open Redirect 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