{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-123877 in the wild and no public exploit code.","exposure":"An affected version is only exploitable if your software calls https.Agent.prototype.getName(). Many projects that include it are not exposed.","fix":"No fix published yet.","what":"CVE-2026-123877 is a medium-severity security feature bypass vulnerability in nodejs node, published on 11 Nov 2026. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-123877 and fix it if it is affected.\n\nWhat it is: CVE-2026-123877 is a medium-severity security feature bypass vulnerability in nodejs node, published on 11 Nov 2026. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-123877 in the wild and no public exploit code.\nExposure: An affected version is only exploitable if your software calls https.Agent.prototype.getName(). 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 https.Agent.prototype.getName() 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-123877/ (Markdown: https://insights.sbomify.com/CVE-2026-123877/index.md)","id":"CVE-2026-123877","markdown":"https://insights.sbomify.com/CVE-2026-123877/index.md","name":"CVE-2026-123877","record":{"aliases":["ALPINE-CVE-2026-123877","BELL-CVE-2026-123877","DEBIAN-CVE-2026-123877","GHSA-4g6g-xjc7-fh73","UBUNTU-CVE-2026-123877"],"analysis":{"component_type":"library","exploitable_when_present":false,"fix_type":"no_fix_stated","impacts":["security_bypass","data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"JavaScript runtime","requires_auth":"low_privilege","requires_specific_call":true,"summary":"Node.js apps using https.Agent may send TLS data to a server whose policy rejects it, because session reuse skips stricter CA checks.","user_interaction":"not_required","vuln_class":"security_feature_bypass","vulnerable_functions":["https.Agent.prototype.getName()"]},"analysis_generated_by":"sbomify/insights-2b-fp8","assigner":"openjs","cpe":[],"cvss":{"score":6.8,"severity":"medium","source":"cna","vector":"CVSS:3.0/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:N","version":"3.0"},"cwes":[{"id":"CWE-295","name":"Improper Certificate Validation"}],"description":"A certificate validation bypass in Node.js https.Agent lets a cached TLS session authenticated under one CA policy be reused by a later request with a stricter policy. https.Agent.prototype.getName() assigns the same Agent and session-cache key to a request that omits ca and one that explicitly supplies ca: [], because an omitted value appends nothing to the key while an empty array stringifies to an empty string. The two policies differ: omitting ca uses the default trust store, while supplying ca replaces it. Since they share a key, a TLS session authenticated under the broader default policy is handed to a new connection made under the later ca: [] policy, and TLS 1.3 session resumption carries the earlier authentication forward, so the second request reports authorized === true and transmits confidential data to a server its own CA policy would reject on a fresh connection. This vulnerability affects Node.js 26.x, 24.x, and 22.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":"Node.js is vulnerable to a certificate validation bypass in https.Agent via cross-policy TLS session reuse","id":"CVE-2026-123877","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"security_feature_bypass","year":"2026"},"n_packages":0,"n_references":2,"next":{"headline":"OpenBMB Internet of Agents Message app.py fetch_chat_record access control","id":"CVE-2026-123881"},"nickname":null,"packages":[],"prev":{"headline":"A flaw was found in the default seccomp profile used by Podman via containers-common.","id":"CVE-2026-123876"},"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":"Node.js apps using https.Agent may send TLS data to a server whose policy rejects it, because session reuse skips stricter CA checks.","url":"https://insights.sbomify.com/CVE-2026-123877/"}