{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-123874 in the wild and no public exploit code.","exposure":"An affected version is only exploitable if your software calls respondWithFile() or respondWithFD(). Many projects that include it are not exposed.","fix":"Upgrade to a fixed version.","what":"CVE-2026-123874 is a high-severity use after free 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-123874 and fix it if it is affected.\n\nWhat it is: CVE-2026-123874 is a high-severity use after free 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-123874 in the wild and no public exploit code.\nExposure: An affected version is only exploitable if your software calls respondWithFile() or respondWithFD(). Many projects that include it are not exposed.\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.\n   If an affected version is present, also search the code for calls to respondWithFile() or respondWithFD() and report whether any exist.\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-123874/ (Markdown: https://insights.sbomify.com/CVE-2026-123874/index.md)","id":"CVE-2026-123874","markdown":"https://insights.sbomify.com/CVE-2026-123874/index.md","name":"CVE-2026-123874","record":{"aliases":["ALPINE-CVE-2026-123874","BELL-CVE-2026-123874","DEBIAN-CVE-2026-123874","GHSA-vgqh-cxw6-x64x","UBUNTU-CVE-2026-123874"],"analysis":{"component_type":"library","exploitable_when_present":false,"fix_type":"upgrade","impacts":["denial_of_service","code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"JavaScript runtime","requires_auth":"none","requires_specific_call":true,"summary":"Unauthenticated HTTP/2 clients can trigger a use-after-free in Node.js servers serving files with stream.respondWithFile, corrupting memory.","user_interaction":"not_required","vuln_class":"use_after_free","vulnerable_functions":["respondWithFile()","respondWithFD()"]},"analysis_generated_by":"sbomify/insights-2b-fp8","assigner":"openjs","cpe":[],"cvss":{"score":7.5,"severity":"high","source":"cna","vector":"CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H","version":"3.0"},"cwes":[{"id":"CWE-416","name":"Use After Free"}],"description":"A use-after-free in Node.js HTTP/2 lets an unauthenticated client corrupt server memory, over both TLS and cleartext, when the server serves files with respondWithFile() or respondWithFD(). A client can make the server free an Http2Stream while a write request that points to it is still queued on the socket; when that write completes, the code dereferences and makes a virtual call through the freed object. The only precondition is that the application serves a file with stream.respondWithFile() or stream.respondWithFD(), with default settings otherwise. 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 an HTTP/2 use-after-free via respondWithFile() stream reset during a pending write","id":"CVE-2026-123874","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"use_after_free","year":"2026"},"n_packages":0,"n_references":2,"next":{"headline":"Null dereference in node","id":"CVE-2026-123875"},"nickname":null,"packages":[],"prev":{"headline":"Node.js is vulnerable to a client certificate authentication bypass via TLS 1.2 renegotiation servername change","id":"CVE-2026-123872"},"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 trigger a use-after-free in Node.js servers serving files with stream.respondWithFile, corrupting memory.","url":"https://insights.sbomify.com/CVE-2026-123874/"}