{"answers":{"affected":"2 open source packages ship an affected version, including sse-channel.","exploited":"There is no known exploitation of CVE-2026-44217 in the wild and no public exploit code.","fix":"Upgrade sse-channel to 4.0.1 or later.","what":"CVE-2026-44217 is a medium-severity vulnerability in rexxars sse-channel, published on 12 May 2026. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-44217 and fix it if it is affected.\n\nWhat it is: CVE-2026-44217 is a medium-severity vulnerability in rexxars sse-channel, published on 12 May 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-44217 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- sse-channel (npm): affected all versions; fixed in 4.0.1\n- sse-channel (npm): affected all versions; fixed in 4.0.1\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-44217/ (Markdown: https://insights.sbomify.com/CVE-2026-44217/index.md)","id":"CVE-2026-44217","markdown":"https://insights.sbomify.com/CVE-2026-44217/index.md","name":"CVE-2026-44217","record":{"aliases":["GHSA-84hm-wfh8-c5pg"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["data_modify"],"network_reachable":"yes","non_default_config":false,"product_category":"Node.js SSE library","requires_auth":"none","summary":"Attackers can inject arbitrary messages into Server-Sent Events streams by exploiting unsanitized event fields in the sse-channel library.","user_interaction":"not_required","vuln_class":"other"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":6.6,"severity":"medium","source":"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","version":"4.0"},"cwes":[{"id":"CWE-93","name":"Improper Neutralization of CRLF Sequences"}],"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.","ecosystems":["npm"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"sse-channel: SSE Injection via unsanitized event fields","id":"CVE-2026-44217","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"npm","product":null,"products":[],"type":"other","year":"2026"},"n_packages":2,"n_references":2,"next":{"headline":"ciguard: Container image runs as root (no USER directive)","id":"CVE-2026-44218"},"packages":[{"ecosystem":"npm","fixed":["4.0.1"],"introduced":["0"],"last_affected":[],"package":"sse-channel","purl":null,"source":"GHSA-84hm-wfh8-c5pg"},{"ecosystem":"npm","fixed":["4.0.1"],"introduced":["0"],"last_affected":[],"package":"sse-channel","purl":"pkg:npm/sse-channel","source":"GHSA-84hm-wfh8-c5pg"}],"prev":{"headline":"Wasmtime: Panic when allocating a table exceeding the size of the host's address space","id":"CVE-2026-44216"},"products":["sse-channel"],"published":"2026-05-12","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"yes","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-05-14","vendors":["rexxars"]},"summary":"Attackers can inject arbitrary messages into Server-Sent Events streams by exploiting unsanitized event fields in the sse-channel library.","url":"https://insights.sbomify.com/CVE-2026-44217/"}