{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-123871 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-123871 is a medium-severity information disclosure vulnerability in nodejs node, published on 11 Nov 2026. It can only be exploited from the same machine or local network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-123871 and fix it if it is affected.\n\nWhat it is: CVE-2026-123871 is a medium-severity information disclosure vulnerability in nodejs node, published on 11 Nov 2026. It can only be exploited from the same machine or local network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-123871 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-123871/ (Markdown: https://insights.sbomify.com/CVE-2026-123871/index.md)","id":"CVE-2026-123871","markdown":"https://insights.sbomify.com/CVE-2026-123871/index.md","name":"CVE-2026-123871","record":{"aliases":["ALPINE-CVE-2026-123871","BELL-CVE-2026-123871","DEBIAN-CVE-2026-123871","GHSA-8669-428h-mj7x","UBUNTU-CVE-2026-123871"],"analysis":{"component_type":"library","exploitable_when_present":false,"fix_type":"no_fix_stated","impacts":["data_read"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"JavaScript runtime","requires_auth":"none","requires_specific_call":false,"summary":"Node.js error messages can leak proxy credentials to logs and crash reports, exposing secrets to anyone reading them.","user_interaction":"not_required","vuln_class":"information_disclosure","vulnerable_functions":[]},"analysis_generated_by":"sbomify/insights-2b-fp8","assigner":"openjs","cpe":[],"cvss":{"score":6.2,"severity":"medium","source":"cna","vector":"CVSS:3.0/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N","version":"3.0"},"cwes":[{"id":"CWE-209","name":"Generation of Error Message Containing Sensitive Information"}],"description":"Node.js discloses proxy credentials in ERR_PROXY_INVALID_CONFIG error messages. CVE-2026-48615 established that a proxy credential must not appear in a Node.js error message and redacted the username and password from ProxyConfig.href, but that fix missed four error paths in the same subsystem, one of them inside the same constructor, which interpolate the raw proxy URL, credentials included, into an ERR_PROXY_INVALID_CONFIG message. The proxy URL comes from the environment, but the defect is the sink: a secret that Node.js redacts everywhere else is emitted verbatim into a much wider audience than the process environment, such as stderr, container logs, log aggregation, and crash reporting services. 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 proxy credential disclosure via ERR_PROXY_INVALID_CONFIG error messages","id":"CVE-2026-123871","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"information_disclosure","year":"2026"},"n_packages":0,"n_references":2,"next":{"headline":"Node.js is vulnerable to a client certificate authentication bypass via TLS 1.2 renegotiation servername change","id":"CVE-2026-123872"},"nickname":null,"packages":[],"prev":{"headline":"The otterdog webapp evaluates a format-string built from the incoming GitHub webhook JSON body using Python's eval().","id":"CVE-2026-123870"},"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 error messages can leak proxy credentials to logs and crash reports, exposing secrets to anyone reading them.","url":"https://insights.sbomify.com/CVE-2026-123871/"}