NewApp Monitoring is liveSign up free
AgentbeamBeta
Open-source package vulnerability · npm

CVE-2026-44217: sse-channel: SSE Injection via unsanitized event fields

mediumCVSS 4.0 6.6GHSA-84hm-wfh8-c5pg

Impact Implementations that allows user-provided values to be passed to event, retry or id fields would be susceptible to event spoofing, where an attacker could inject arbitrary messages into the stream. - Event Spoofing: Attacker can inject arbitrary SSE events into the stream - Client-side Manipulation: Injected events can trigger unintended behavior in frontend JavaScript EventSource listeners - Data Integrity:…

Published May 5, 2026 · Updated May 13, 2026

Affected packages

sse-channel

Ecosystem
npm
Affected
<= 4.0.0
Fixed in
4.0.1
Check
npm ls sse-channel

Advisory details

From the GitHub Advisory Database (CC BY 4.0).

Impact

Implementations that allows user-provided values to be passed to event, retry or id fields would be susceptible to event spoofing, where an attacker could inject arbitrary messages into the stream.

  • Event Spoofing: Attacker can inject arbitrary SSE events into the stream
  • Client-side Manipulation: Injected events can trigger unintended behavior in frontend JavaScript EventSource listeners
  • Data Integrity: Consumers of the SSE stream cannot distinguish injected events from legitimate ones

Patches

Patch available in v4.0.1.

Workarounds

Do not allow user data to control event, retry or id fields, and if you must - sanitize the input before passing it to sse-channel, stripping any newlines.

Resources

https://github.com/rexxars/sse-channel/issues/42

Credited to SnailSploit.

References

How this page is made: the data panel comes from the GitHub Advisory Database, CISA’s KEV catalog, the NVD and FIRST EPSS, and updates twice a day. No analysis has been written for this entry yet. Methodology