Live Exposure Defense: From CVE to Confirmed Exposure in 12 Hours – See more

Back
New CVE Detected

CVE-2026-47890 – SSE Stream Corruption / CRLF Injection – Spring Framework 6.2.0–6.2.19 and 7.0.0–7.

Be the first to know when new zero-days emerge:

Subscribe to Email Alerts
Subscribe to RSS Feed

Summary

CVE-2026-47890 is a CRLF injection vulnerability (CWE-93) affecting Spring Framework’s handling of Server-Sent Events (SSE) when rendering view fragments in Spring MVC and Spring WebFlux applications. It allows an attacker who controls data streamed to other users to corrupt the SSE stream, potentially injecting content that affects other clients’ sessions. The issue is tracked as critical severity.

Technical details

  • Root cause: improper neutralization of carriage-return/line-feed sequences when Spring MVC/WebFlux serializes view fragments into an SSE data stream.
  • Trigger conditions: the application must use Spring MVC or WebFlux, stream view fragments to clients over SSE, and an attacker must control data that gets streamed to other users of the application.
  • Attack vector: network, no authentication or user interaction required to exploit once the above conditions are met.
  • Impact: corruption of the SSE data stream delivered to other users, which — depending on frontend logic — can corrupt client-side state or present attacker-controlled/malicious content to victims.

Affected software

  • Spring Framework 7.0.0 through 7.0.8
  • Spring Framework 6.2.0 through 6.2.19

Severity

CVSS v3.1 Base Score: 9.8 (Critical)
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Mitigation and recommended actions

  • Immediate: upgrade to Spring Framework 7.0.9 (open source fix). Organizations on Enterprise Support can obtain fixes in 7.0.8.1 or 6.2.20.
  • If patching isn’t immediately possible: avoid streaming untrusted/attacker-influenced data as SSE view fragments to other users, or disable SSE view-fragment rendering until upgraded, as Spring has not published additional workarounds.

How IONIX identifies potentially affected assets

IONIX matches the following signals against data already collected when it crawled the asset; identifying the technology sends no request beyond that crawl.

  • Raw HTTP response body: Caused by: org.springframework.data., at: org.springframework.data., org.springframework.data.mapping.MappingException, org.springframework.data.repository.RepositoryCreationException, /WEB-INF/lib/spring-data-commons-<version>.jar, spring-data-commons-<version>.jar, /META-INF/MANIFEST.MF referencing spring-data-commons

References

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

  • Mapping of all Assets with this Technology
  • Identification of potentially exposed assets to this CVE
  • Confirmation of verified exploitable assets
Get Exposure Report

How IONIX’s External Exposure Management Platform Detects and Validates
Zero-Days to Shrink MTTR

1

Map your entire attack surface (continously)

IONIX uses multi-factor discovery methods, including DNS analysis, certificate mapping, metadata inspection, and more, to automatically map every internet-facing asset across your environment. This includes cloud instances, third-party platforms, shadow IT, and even forgotten infrastructure that traditional tools miss.

2

Monitor for new CVEs

Dozens of threat intel feeds using agentic technology are continuously analyzed to detect the appearance of proof-of-concept code, exploit kits, and indicators of active targeting. IONIX goes further by applying AI to proactively evaluate whether emerging vulnerabilities are likely to be exploited, even before PoCs go public.

3

Identify Potential External Exposures

Not all CVEs matter. IONIX filters vulnerabilities by asking attacker-centric questions: Can it be reached from the internet? Does it require authentication? Is it being exploited in the wild? This dramatically reduces noise and focuses teams on threats that can actually be weaponized.

4

Create Safe, Scalable Exploit Validations

IONIX transforms real-world PoCs into safe, non-intrusive test payloads that can be run in production environments without disruption. These simulations are precisely targeted to the systems that are vulnerable, ensuring rapid validation without unnecessary load.

5

Execute Exploit Validations

By combining context about software stack, versioning, exposure status, and reachability, IONIX ensures that only the right payloads are executed against the right assets, maximizing efficiency and minimizing risk.

6

Drive Fast and Actionable Remediation

Results are routed through integrations with ticketing, SOAR, and SIEM tools. Issues are written in plain language, bundled into remediation clusters, and prioritized based on asset criticality, exploitability, and blast radius. This shortens mean time to remediation (MTTR) and empowers teams to act with confidence.

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

  • Mapping of all Assets with this Technology
  • Identification of potentially exposed assets to this CVE
  • Confirmation of verified exploitable assets
Get Exposure Report
Close

Subscribe to Threat Center RSS

Copy/paste the link below into your preferred RSS reader or follow these instructions to subscribe to Slack alerts.

Open RSS feedSlack setup instructions

Close

Get Real-Time CVE Alerts to Your Email

Be the first to know when new zero-days emerge