{"answers":{"affected":"3 open source packages ship an affected version, including github.com/neuvector/neuvector.","exploited":"There is no known exploitation of CVE-2025-66001 in the wild and no public exploit code.","fix":"Upgrade github.com/neuvector/neuvector to 5.4.8 or later.","what":"CVE-2025-66001 is a high-severity vulnerability in SUSE neuvector, published on 8 Jan 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-2025-66001 and fix it if it is affected.\n\nWhat it is: CVE-2025-66001 is a high-severity vulnerability in SUSE neuvector, published on 8 Jan 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-2025-66001 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- github.com/neuvector/neuvector (Go): affected all versions; no fix listed\n- github.com/neuvector/neuvector (Go): affected from 5.3.0; fixed in 5.4.8\n- github.com/neuvector/neuvector (Go): affected from 5.3.0; fixed in 5.4.8\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-2025-66001/ (Markdown: https://insights.sbomify.com/CVE-2025-66001/index.md)","id":"CVE-2025-66001","markdown":"https://insights.sbomify.com/CVE-2025-66001/index.md","name":"CVE-2025-66001","record":{"aliases":["GHSA-4jj9-cgqc-x9h5","GO-2025-4235"],"analysis":{"component_type":"container_or_infrastructure","fix_type":"patch","impacts":["security_bypass","account_takeover"],"network_reachable":"yes","non_default_config":false,"product_category":"NeuVector security platform","requires_auth":"none","summary":"Attackers can intercept OpenID Connect authentication traffic due to disabled TLS verification, potentially leading to credential theft or session hijacking.","user_interaction":"required","vuln_class":"security_feature_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"suse","cpe":[],"cvss":{"score":8.8,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-295","name":"Improper Certificate Validation"}],"description":"NeuVector supports login authentication through OpenID Connect. However, the TLS verification (which verifies the remote server's authenticity and integrity) for OpenID Connect is not enforced by default. As a result this may expose the system to man-in-the-middle (MITM) attacks.","ecosystems":["Go"],"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":"NeuVector OpenID Connect is vulnerable to man-in-the-middle (MITM)","id":"CVE-2025-66001","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Go","product":null,"products":[],"type":"security_feature_bypass","year":"2025"},"n_packages":3,"n_references":2,"next":{"headline":"Local users can perform arbitrary unmounts via smb4k mount helper due to lack of input validation","id":"CVE-2025-66002"},"packages":[{"ecosystem":"Go","fixed":[],"introduced":["0"],"last_affected":[],"package":"github.com/neuvector/neuvector","purl":"pkg:golang/github.com/neuvector/neuvector","source":"GO-2025-4235"},{"ecosystem":"Go","fixed":["5.4.8"],"introduced":["5.3.0"],"last_affected":[],"package":"github.com/neuvector/neuvector","purl":null,"source":"GHSA-4jj9-cgqc-x9h5"},{"ecosystem":"Go","fixed":["5.4.8"],"introduced":["5.3.0"],"last_affected":[],"package":"github.com/neuvector/neuvector","purl":"pkg:golang/github.com/neuvector/neuvector","source":"GHSA-4jj9-cgqc-x9h5"}],"prev":{"headline":"Information disclosure in Affinity","id":"CVE-2025-66000"},"products":["neuvector"],"published":"2026-01-08","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":"CC BY 4.0","name":"Go Vulnerability Database","prefix":"GO"},{"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":"total"},"state":"PUBLISHED","updated":"2026-01-08","vendors":["SUSE"]},"summary":"Attackers can intercept OpenID Connect authentication traffic due to disabled TLS verification, potentially leading to credential theft or session hijacking.","url":"https://insights.sbomify.com/CVE-2025-66001/"}