{"answers":{"affected":"3 open source packages ship an affected version, including github.com/neuvector/neuvector.","exploited":"There is no known exploitation of CVE-2025-54470 in the wild and no public exploit code.","fix":"Upgrade github.com/neuvector/neuvector to 0.0.0-20251020133207-084a437033b4 or later.","what":"CVE-2025-54470 is a high-severity vulnerability in SUSE neuvector, published on 30 Oct 2025. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2025-54470 and fix it if it is affected.\n\nWhat it is: CVE-2025-54470 is a high-severity vulnerability in SUSE neuvector, published on 30 Oct 2025. 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-2025-54470 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 0.0.0-20230727023453-1c4957d53911; fixed in 0.0.0-20251020133207-084a437033b4\n- github.com/neuvector/neuvector (Go): affected from 0.0.0-20230727023453-1c4957d53911; fixed in 0.0.0-20251020133207-084a437033b4\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-54470/ (Markdown: https://insights.sbomify.com/CVE-2025-54470/index.md)","id":"CVE-2025-54470","markdown":"https://insights.sbomify.com/CVE-2025-54470/index.md","name":"CVE-2025-54470","record":{"aliases":["GHSA-qqj3-g7mx-5p4w","GO-2025-4044"],"analysis":{"component_type":"container_or_infrastructure","fix_type":"patch","impacts":["data_read","denial_of_service"],"network_reachable":"yes","non_default_config":true,"product_category":"NeuVector telemetry","requires_auth":"none","summary":"Attackers can intercept telemetry data or cause denial of service in NeuVector when anonymous reporting is enabled due to missing TLS verification and size limits.","user_interaction":"not_required","vuln_class":"security_feature_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"suse","cpe":[],"cvss":{"score":8.6,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:H","version":"3.1"},"cwes":[{"id":"CWE-295","name":"Improper Certificate Validation"}],"description":"This vulnerability affects NeuVector deployments only when the Report anonymous cluster data option is enabled. When this option is enabled, NeuVector sends anonymous telemetry data to the telemetry server.\n\nIn affected versions, NeuVector does not enforce TLS \ncertificate verification when transmitting anonymous cluster data to the\n telemetry server. As a result, the communication channel is susceptible\n to man-in-the-middle (MITM) attacks, where an attacker could intercept \nor modify the transmitted data. Additionally, NeuVector loads the \nresponse of the telemetry server is loaded into memory without size \nlimitation, which makes  it vulnerable to a Denial of Service(DoS) \nattack","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 telemetry sender is vulnerable to MITM and DoS","id":"CVE-2025-54470","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":"NeuVector is shipping cryptographic material into its binary","id":"CVE-2025-54471"},"packages":[{"ecosystem":"Go","fixed":[],"introduced":["0"],"last_affected":[],"package":"github.com/neuvector/neuvector","purl":"pkg:golang/github.com/neuvector/neuvector","source":"GO-2025-4044"},{"ecosystem":"Go","fixed":["0.0.0-20251020133207-084a437033b4"],"introduced":["0.0.0-20230727023453-1c4957d53911"],"last_affected":[],"package":"github.com/neuvector/neuvector","purl":null,"source":"GHSA-qqj3-g7mx-5p4w"},{"ecosystem":"Go","fixed":["0.0.0-20251020133207-084a437033b4"],"introduced":["0.0.0-20230727023453-1c4957d53911"],"last_affected":[],"package":"github.com/neuvector/neuvector","purl":"pkg:golang/github.com/neuvector/neuvector","source":"GHSA-qqj3-g7mx-5p4w"}],"prev":{"headline":"NeuVector Enforcer is vulnerable to Command Injection and Buffer overflow","id":"CVE-2025-54469"},"products":["neuvector"],"published":"2025-10-30","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":"yes","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2025-10-30","vendors":["SUSE"]},"summary":"Attackers can intercept telemetry data or cause denial of service in NeuVector when anonymous reporting is enabled due to missing TLS verification and size limits.","url":"https://insights.sbomify.com/CVE-2025-54470/"}