Event spoofing via unsanitized SSE delimiters
Published Apr 7, 2026 · Updated Apr 7, 2026
Server-Sent Events injection in Nest before 11.1.18 allows attackers to spoof events and corrupt reconnection state via crafted message fields. SseStream._transform() writes message.type and message.id into SSE output without removing carriage returns or line feeds, which become protocol fields and event boundaries. Exploitation requires developer code to map attacker-controlled data into type or id; direct HTTP input does not reach those fields by default.
Summary
What happened
Server-Sent Events injection in Nest before 11.1.18 allows attackers to spoof events and corrupt reconnection state via crafted message fields. SseStream._transform() writes message.type and message.id into SSE output without removing carriage returns or line feeds, which become protocol fields and event boundaries. Exploitation requires developer code to map attacker-controlled data into type or id; direct HTTP input does not reach those fields by default.
The record
- CVE
- CVE-2026-35515
- Published
- Apr 7, 2026
- Updated
- Apr 7, 2026
- Vendor
- NestJS
- Product
- Nest
- Classifications
- CWE-74, T1565.002
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Apr 7, 2026CVE publishedPublication date reported by the CVE source.
- Apr 7, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=< 11.1.18
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo