{"answers":{"affected":"4 open source packages ship an affected version, including h3. It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-33128 exists.","fix":"Upgrade h3 to a fixed version for your release line: 1.15.6 or 2.0.1-rc.15.","what":"CVE-2026-33128 is a high-severity vulnerability in h3js h3, published on 20 Mar 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-33128 and fix it if it is affected.\n\nWhat it is: CVE-2026-33128 is a high-severity vulnerability in h3js h3, published on 20 Mar 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-33128 exists.\n\nAffected packages and fixed versions:\n- h3 (npm): affected all versions; fixed in 1.15.6\n- h3 (npm): affected all versions; fixed in 1.15.6\n- h3 (npm): affected from 2.0.0; fixed in 2.0.1-rc.15\n- h3 (npm): affected from 2.0.0; fixed in 2.0.1-rc.15\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-33128/ (Markdown: https://insights.sbomify.com/CVE-2026-33128/index.md)","id":"CVE-2026-33128","markdown":"https://insights.sbomify.com/CVE-2026-33128/index.md","name":"CVE-2026-33128","record":{"aliases":["GHSA-22cc-p3c6-wpvm"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["data_modify","other"],"network_reachable":"yes","non_default_config":false,"product_category":"H3 HTTP framework","requires_auth":"none","summary":"Attackers can inject arbitrary Server-Sent Events into client streams via unsanitized newlines in H3 framework event fields.","user_interaction":"not_required","vuln_class":"other"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"h3","vendor":"h3"}],"cvss":{"score":7.5,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:L/I:H/A:N","version":"3.1"},"cwes":[{"id":"CWE-93","name":"Improper Neutralization of CRLF Sequences"}],"description":"H3 is a minimal H(TTP) framework. In versions prior to 1.15.6 and between 2.0.0 through 2.0.1-rc.14, createEventStream is vulnerable to Server-Sent Events (SSE) injection due to missing newline sanitization in formatEventStreamMessage() and formatEventStreamComment(). An attacker who controls any part of an SSE message field (id, event, data, or comment) can inject arbitrary SSE events to connected clients. This issue is fixed in versions 1.15.6 and 2.0.1-rc.15.","ecosystems":["npm"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":true,"headline":"h3 has a Server-Sent Events Injection via Unsanitized Newlines in Event Stream Fields","id":"CVE-2026-33128","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"npm","product":null,"products":[],"type":"other","year":"2026"},"n_packages":4,"n_references":3,"next":{"headline":"h3 has an observable timing discrepancy in basic auth utils","id":"CVE-2026-33129"},"packages":[{"ecosystem":"npm","fixed":["1.15.6"],"introduced":["0"],"last_affected":[],"package":"h3","purl":null,"source":"GHSA-22cc-p3c6-wpvm"},{"ecosystem":"npm","fixed":["1.15.6"],"introduced":["0"],"last_affected":[],"package":"h3","purl":"pkg:npm/h3","source":"GHSA-22cc-p3c6-wpvm"},{"ecosystem":"npm","fixed":["2.0.1-rc.15"],"introduced":["2.0.0"],"last_affected":[],"package":"h3","purl":null,"source":"GHSA-22cc-p3c6-wpvm"},{"ecosystem":"npm","fixed":["2.0.1-rc.15"],"introduced":["2.0.0"],"last_affected":[],"package":"h3","purl":"pkg:npm/h3","source":"GHSA-22cc-p3c6-wpvm"}],"prev":{"headline":"Frigate has SSRF vulnerability in /ffprobe endpoint","id":"CVE-2026-33126"},"products":["h3"],"published":"2026-03-20","related":[{"cvss_score":8.9,"headline":"h3 v1 has Request Smuggling (TE.TE) issue","id":"CVE-2026-23527","kev_date_added":null,"published":"2026-01-15"},{"cvss_score":7.4,"headline":"h3 has a middleware bypass with one gadget","id":"CVE-2026-33131","kev_date_added":null,"published":"2026-03-20"},{"cvss_score":5.9,"headline":"h3 has an observable timing discrepancy in basic auth utils","id":"CVE-2026-33129","kev_date_added":null,"published":"2026-03-20"},{"cvss_score":3.7,"headline":"h3: Missing Path Segment Boundary Check in `mount()` Causes Middleware Execution on Unrelated Prefix-Matching Routes","id":"CVE-2026-33490","kev_date_added":null,"published":"2026-03-26"}],"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":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-03-20","vendors":["h3js"]},"summary":"Attackers can inject arbitrary Server-Sent Events into client streams via unsanitized newlines in H3 framework event fields.","url":"https://insights.sbomify.com/CVE-2026-33128/"}