{"answers":{"affected":"2 open source packages ship an affected version, including client-certificate-auth. It affects 1 product.","exploited":"There is no known exploitation of CVE-2026-25651 in the wild and no public exploit code.","fix":"Upgrade client-certificate-auth to 1.0.0 or later.","what":"CVE-2026-25651 is a medium-severity vulnerability in tgies client-certificate-auth, published on 6 Feb 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2026-25651 and fix it if it is affected.\n\nWhat it is: CVE-2026-25651 is a medium-severity vulnerability in tgies client-certificate-auth, published on 6 Feb 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2026-25651 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- client-certificate-auth (npm): affected from 0.2.1; fixed in 1.0.0\n- client-certificate-auth (npm): affected from 0.2.1; fixed in 1.0.0\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-25651/ (Markdown: https://insights.sbomify.com/CVE-2026-25651/index.md)","id":"CVE-2026-25651","markdown":"https://insights.sbomify.com/CVE-2026-25651/index.md","name":"CVE-2026-25651","record":{"aliases":["GHSA-m4w9-gch5-c2g4"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"Node.js authentication middleware","requires_auth":"none","summary":"An attacker can redirect users to arbitrary domains via Host Header Injection in the HTTP-to-HTTPS redirect logic of this Node.js middleware.","user_interaction":"required","vuln_class":"open_redirect"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"client-certificate-auth","vendor":"tgies"}],"cvss":{"score":6.1,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N","version":"3.1"},"cwes":[{"id":"CWE-601","name":"URL Redirection to Untrusted Site"}],"description":"client-certificate-auth is middleware for Node.js implementing client SSL certificate authentication/authorization. Versions 0.2.1 and 0.3.0 of client-certificate-auth contain an open redirect vulnerability. The middleware unconditionally redirects HTTP requests to HTTPS using the unvalidated Host header, allowing an attacker to redirect users to arbitrary domains. This vulnerability is fixed in 1.0.0.","ecosystems":["npm"],"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":"client-certificate-auth has an Open Redirect via Host Header Injection in HTTP-to-HTTPS redirect","id":"CVE-2026-25651","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"npm","product":null,"products":[],"type":"open_redirect","year":"2026"},"n_packages":2,"n_references":2,"next":{"headline":"ColdFusion | Incorrect Authorization (CWE-863)","id":"CVE-2026-25652"},"packages":[{"ecosystem":"npm","fixed":["1.0.0"],"introduced":["0.2.1"],"last_affected":[],"package":"client-certificate-auth","purl":null,"source":"GHSA-m4w9-gch5-c2g4"},{"ecosystem":"npm","fixed":["1.0.0"],"introduced":["0.2.1"],"last_affected":[],"package":"client-certificate-auth","purl":"pkg:npm/client-certificate-auth","source":"GHSA-m4w9-gch5-c2g4"}],"prev":{"headline":"MCP Salesforce Connector has arbitrary attribute access which leads to disclosure of Salesforce auth token","id":"CVE-2026-25650"},"products":["client-certificate-auth"],"published":"2026-02-06","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-02-09","vendors":["tgies"]},"summary":"An attacker can redirect users to arbitrary domains via Host Header Injection in the HTTP-to-HTTPS redirect logic of this Node.js middleware.","url":"https://insights.sbomify.com/CVE-2026-25651/"}