{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-123863 in the wild and no public exploit code.","exposure":"An affected version is exposed as installed. No special setting or call is needed.","fix":"Upgrade to a fixed version.","what":"CVE-2026-123863 is a high-severity denial of service vulnerability in nodejs node, published on 11 Nov 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-123863 and fix it if it is affected.\n\nWhat it is: CVE-2026-123863 is a high-severity denial of service vulnerability in nodejs node, published on 11 Nov 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-123863 in the wild and no public exploit code.\nExposure: An affected version is exposed as installed. No special setting or call is needed.\n\nAffected product: nodejs node. No package-level version data is available, so check the vendor advisory linked from the reference page.\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-123863/ (Markdown: https://insights.sbomify.com/CVE-2026-123863/index.md)","id":"CVE-2026-123863","markdown":"https://insights.sbomify.com/CVE-2026-123863/index.md","name":"CVE-2026-123863","record":{"aliases":["ALPINE-CVE-2026-123863","BELL-CVE-2026-123863","DEBIAN-CVE-2026-123863","GHSA-cwc7-c9hg-jq89","UBUNTU-CVE-2026-123863"],"analysis":{"component_type":"library","exploitable_when_present":false,"fix_type":"upgrade","impacts":["denial_of_service"],"network_reachable":"yes","non_default_config":false,"product_category":"JavaScript runtime","requires_auth":"none","requires_specific_call":false,"summary":"Unauthenticated HTTP/2 clients can crash Node.js servers via a reachable assertion in session teardown; Node.js HTTP/2 operators should care.","user_interaction":"not_required","vuln_class":"denial_of_service","vulnerable_functions":["Http2Session"]},"analysis_generated_by":"sbomify/insights-2b-fp8","assigner":"openjs","cpe":[],"cvss":{"score":8.2,"severity":"high","source":"cna","vector":"CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:H","version":"3.0"},"cwes":[{"id":"CWE-617","name":"Reachable Assertion"}],"description":"A reachable assertion in Node.js HTTP/2 session teardown lets any unauthenticated client abort the server, over both TLS and cleartext. A client can arrange for an Http2Stream that still holds nghttp2-allocated header buffers to outlive its session: the stream is removed from the session's stream set but never detached, so when ~Http2Session() runs the memory accounting is nonzero and the CHECK_EQ(current_nghttp2_memory_, 0) assertion fails, terminating the process. The trigger needs only a default http2 server whose handler responds before the request body has ended, which is typical. It is a variant of CVE-2024-27983 that the earlier fix did not cover, because that fix only detached streams still tracked in the session. This vulnerability affects Node.js 26.x (since 26.9.0) and 24.x (since 24.22.0).","ecosystems":[],"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":"Node.js is vulnerable to a remote HTTP/2 denial of service via a reachable assertion in Http2Session teardown","id":"CVE-2026-123863","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"denial_of_service","year":"2026"},"n_packages":0,"n_references":2,"next":{"headline":"Node.js is vulnerable to cross-connection memory disclosure via TLS write re-entrancy in the HTTPS request parser","id":"CVE-2026-123864"},"nickname":null,"packages":[],"prev":{"headline":"Node.js is vulnerable to a zlib denial of service via a stream destroy during a pending params() call","id":"CVE-2026-123862"},"products":["node"],"published":"2026-11-11","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2026-11-11","vendors":["nodejs"]},"summary":"Unauthenticated HTTP/2 clients can crash Node.js servers via a reachable assertion in session teardown; Node.js HTTP/2 operators should care.","url":"https://insights.sbomify.com/CVE-2026-123863/"}