https://cve.radiocsirt.org/rss/recent/all/10 Most recent entries from all 2026-10-07T07:35:57.594937+00:00 Vulnerability-Lookup csirt@opendfir.org python-feedgen Contains only the most 10 recent entries. https://cve.radiocsirt.org/vuln/euvd-2026-318648 EUVD-2026-318648 2026-10-07T07:35:57.661647+00:00 EUVD-2026-318648 https://cve.radiocsirt.org/vuln/fkie_cve-2026-44217 fkie_cve-2026-44217 2026-10-07T07:35:57.661687+00:00

sse-channel is an SSE-implementation which can be used to any node.js http request/response stream. Prior to 4.0.1, implementations that allow user-provided values to be passed to event, retry or id fields are susceptible to event spoofing, where an attacker could inject arbitrary messages into the stream. This vulnerability is fixed in 4.0.1.

 https://cve.radiocsirt.org/vuln/ghsa-84hm-wfh8-c5pg GHSA-84hm-wfh8-c5pg — sse-channel: SSE Injection via unsanitized event fields 2026-10-07T07:35:57.661720+00:00

Affected: npm: sse-channel

### 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