Skip to content

Spring MVC and WebFlux has Server Sent Event stream corruption

Low severity GitHub Reviewed Published Mar 20, 2026 to the GitHub Advisory Database • Updated Mar 20, 2026

Package

maven org.springframework:spring-webflux (Maven)

Affected versions

>= 7.0.0-M1, < 7.0.6
>= 6.2.0, < 6.2.17
>= 6.0.0, <= 6.1.21
>= 5.3.0, <= 5.3.39

Patched versions

7.0.6
6.2.17
maven org.springframework:spring-webmvc (Maven)
>= 7.0.0-M1, < 7.0.6
>= 6.2.0, < 6.2.17
>= 6.0.0, <= 6.1.21
>= 5.3.0, <= 5.3.39
7.0.6
6.2.17

Description

Spring MVC and WebFlux applications are vulnerable to stream corruption when using Server-Sent Events (SSE). This issue affects Spring Foundation: from 7.0.0 through 7.0.5, from 6.2.0 through 6.2.16, from 6.1.0 through 6.1.25, from 5.3.0 through 5.3.46.

References

Published by the National Vulnerability Database Mar 20, 2026
Published to the GitHub Advisory Database Mar 20, 2026
Reviewed Mar 20, 2026
Last updated Mar 20, 2026

Severity

Low

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

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

CVSS v3 base metrics

Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.
CVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:U/C:N/I:L/A:N

EPSS score

Exploit Prediction Scoring System (EPSS)

This score estimates the probability of this vulnerability being exploited within the next 30 days. Data provided by FIRST.
(26th percentile)

Weaknesses

Improper Locking

The product does not properly acquire or release a lock on a resource, leading to unexpected resource state changes and behaviors. Learn more on MITRE.

CVE ID

CVE-2026-22735

GHSA ID

GHSA-6hcq-hmm3-jj3c

Source code

Loading Checking history
See something to contribute? Suggest improvements for this vulnerability.