{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-123868 in the wild and no public exploit code.","exposure":"An affected version is exposed as installed. No special setting or call is needed.","fix":"No fix published yet.","what":"CVE-2026-123868 is a medium-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-123868 and fix it if it is affected.\n\nWhat it is: CVE-2026-123868 is a medium-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-123868 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-123868/ (Markdown: https://insights.sbomify.com/CVE-2026-123868/index.md)","id":"CVE-2026-123868","markdown":"https://insights.sbomify.com/CVE-2026-123868/index.md","name":"CVE-2026-123868","record":{"aliases":["ALPINE-CVE-2026-123868","BELL-CVE-2026-123868","DEBIAN-CVE-2026-123868","GHSA-fxrg-pjjh-rp27","UBUNTU-CVE-2026-123868"],"analysis":{"component_type":"library","exploitable_when_present":false,"fix_type":"no_fix_stated","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 exhaust Node.js server memory by sending DATA on undrained streams, affecting Node.js servers using HTTP/2.","user_interaction":"not_required","vuln_class":"denial_of_service","vulnerable_functions":["Http2Session::CanAddStream"]},"analysis_generated_by":"sbomify/insights-2b-fp8","assigner":"openjs","cpe":[],"cvss":{"score":5.9,"severity":"medium","source":"cna","vector":"CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H","version":"3.0"},"cwes":[{"id":"CWE-400","name":"Uncontrolled Resource Consumption"}],"description":"An unauthenticated HTTP/2 client can exhaust Node.js server memory because inbound DATA queued on an undrained stream is charged to no session budget. Each inbound DATA frame creates one JavaScript Buffer view in the receiving stream's readable queue, but nothing charges that queue to current_session_memory_: the socket read buffer is accounted only during parsing and released immediately, so whatever stays queued is accounted to nothing. A peer that fills a stream's receive window with one-byte DATA frames pays about 10 wire bytes per frame while the server retains about 114 bytes per frame, so a single stream on one connection can retain hundreds of megabytes from tens of megabytes sent. maxSessionMemory neither bounds the growth nor refuses new streams, because Http2Session::CanAddStream gates admission on the same counter that never sees the queue. This vulnerability affects Node.js 26.x and 24.x.","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":"Denial of service in node","id":"CVE-2026-123868","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":"The otterdog webapp evaluates a format-string built from the incoming GitHub webhook JSON body using Python's eval().","id":"CVE-2026-123870"},"nickname":null,"packages":[],"prev":{"headline":"Node.js is vulnerable to a per-host mTLS authorization bypass via a CA-only SNI context failing open to the default CA","id":"CVE-2026-123867"},"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 exhaust Node.js server memory by sending DATA on undrained streams, affecting Node.js servers using HTTP/2.","url":"https://insights.sbomify.com/CVE-2026-123868/"}