https://cve.radiocsirt.org Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Wed, 07 Oct 2026 02:00:09 +0000 https://cve.radiocsirt.org/vuln/euvd-2026-318648 EUVD-2026-318648 https://cve.radiocsirt.org/vuln/euvd-2026-318648 https://cve.radiocsirt.org/vuln/fkie_cve-2026-44217 <p>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.</p> <p>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.</p> https://cve.radiocsirt.org/vuln/fkie_cve-2026-44217 https://cve.radiocsirt.org/vuln/ghsa-84hm-wfh8-c5pg <p><strong>Affected:</strong> npm: sse-channel</p> <p>### Impact</p> <p>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.</p> <p>- **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</p> <p>### Patches Patch available in v4.0.1.</p> <p>### 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.</p> <p>### Resources</p> <p>https://github.com/rexxars/sse-channel/issues/42</p> <p><strong>Affected:</strong> npm: sse-channel</p> <p>### Impact</p> <p>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.</p> <p>- **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</p> <p>### Patches Patch available in v4.0.1.</p> <p>### 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.</p> <p>### Resources</p> <p>https://github.com/rexxars/sse-channel/issues/42</p> https://cve.radiocsirt.org/vuln/ghsa-84hm-wfh8-c5pg