VulnerabilityPublished 19 Mar 2026

CVE-2026-22735: Spring Foundation · CWE-667

Affects Spring FoundationSource CVE Database V5

Compare

Not known to be exploited · CVSS 2.6 Low.

Data as of 31 Oct 2026, 08:20 UTC

CVSS 3.1 base score

2.6Low

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.1% chance of exploitation in 30 days – higher than 1% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

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

Attack Vector: Network
Attack Complexity: High
Privileges Required: Low
User Interaction: Required
Scope: Unchanged
Confidentiality: None
Integrity: Low
Availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: High: A successful attack depends on conditions beyond the attacker's control. That is, a successful attack cannot be accomplished at will, but requires the attacker to invest in some measurable amount of effort in preparation or execution against the vulnerable component before a successful attack can be expected. For example, a successful attack may require an attacker to: gather knowledge about the environment in which the vulnerable target/component exists; prepare the target environment to improve exploit reliability; or inject themselves into the logical network path between the target and the resource requested by the victim in order to read and/or modify network communications (e.g., a man in the middle attack).
Privileges Required: Low: The attacker is authorized with (i.e., requires) privileges that provide basic user capabilities that could normally affect only settings and files owned by a user. Alternatively, an attacker with Low privileges may have the ability to cause an impact only to non-sensitive resources.
User Interaction: Required: Successful exploitation of this vulnerability requires a user to take some action before the vulnerability can be exploited.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: None: There is no loss of confidentiality within the impacted component.
Integrity: Low: Modification of data is possible, but the attacker does not have control over the consequence of a modification, or the amount of modification is limited. The data modification does not have a direct, serious impact on the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 19 Mar 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 30 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponized: A Metasploit exploit module or Exploit-DB entry exists (Metasploit scanner modules do not count), or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Affected software

Product	Affected	Fixed in
SpringSpring Foundation	Affected >=7.0.0 <=7.0.5 >=6.2.0 <=6.2.16 >=6.1.0 <=6.1.25 >=5.3.0 <=5.3.46	Fixed in–

AI-suggested

Organizations should proactively monitor for updates from the Spring Foundation project and apply patches promptly once they become available for the affected versions. Until patches are released, developers should review their use of Server-Sent Events in Spring MVC and WebFlux applications to identify potential misuse or improper stream handling that could lead to corruption. Implementing additional validation and error handling on both server and client sides can help detect and mitigate corrupted event streams. Limiting exposure of SSE endpoints through network segmentation, access controls, and authentication can reduce the attack surface. Additionally, educating developers on secure SSE implementation best practices and conducting thorough testing of SSE functionality under various conditions can prevent exploitation. Monitoring application logs for anomalies in SSE traffic may also provide early detection of attempted exploitation.

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.

Impact

The primary impact of CVE-2026-22735 is on the integrity of data streams in applications using Spring MVC or WebFlux with SSE. Corrupted event streams could lead to incorrect or incomplete data being processed by clients, potentially causing application logic errors, inconsistent user experiences, or downstream processing faults. While the vulnerability does not affect confidentiality or availability, integrity issues in real-time event streams could disrupt critical business processes relying on accurate event delivery, such as financial transactions, monitoring dashboards, or notification systems. The requirement for user interaction and low privileges reduces the likelihood of widespread exploitation, and the high attack complexity further limits the risk. However, organizations with high-dependency on SSE for real-time data delivery should consider the risk carefully, especially in environments where data integrity is paramount.

CWE-667Improper Locking (opens in a new tab)
Class weakness
The product does not properly acquire or release a lock on a resource, leading to unexpected resource state changes and behaviors.
Implementation · Libraries or Frameworks
Use industry standard APIs to implement locking mechanism.
Attack patterns
Leveraging Race Conditions via Symbolic Links (opens in a new tab)
Forced Deadlock (opens in a new tab)
Leveraging Race Conditions (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

spring.io/security/cve-2026-22735 (opens in a new tab)

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 20 Mar 2026, 00:08 UTC

WeaknessesCWE-667

Technical details

References

Community reviews

Related threats