{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2025-40896 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2025-40896 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-40896 is a medium-severity vulnerability in Nozomi Networks Arc, published on 4 Mar 2026. 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-40896 and fix it if it is affected.\n\nWhat it is: CVE-2025-40896 is a medium-severity vulnerability in Nozomi Networks Arc, published on 4 Mar 2026. 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-40896 in the wild and no public exploit code.\n\nAffected product: Nozomi Networks Arc. 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-2025-40896/ (Markdown: https://insights.sbomify.com/CVE-2025-40896/index.md)","id":"CVE-2025-40896","markdown":"https://insights.sbomify.com/CVE-2025-40896/index.md","name":"CVE-2025-40896","record":{"aliases":["GHSA-32r6-gffx-pj25"],"analysis":{"component_type":"server_software","fix_type":"upgrade","impacts":["data_read","data_modify"],"network_reachable":"yes","non_default_config":false,"product_category":"Nozomi Networks Arc","requires_auth":"none","summary":"Attackers can intercept Arc agent communications via man-in-the-middle attacks due to missing TLS validation, stealing tokens and injecting spoofed data.","user_interaction":"not_required","vuln_class":"security_feature_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Nozomi","cpe":[{"product":"arc","vendor":"nozominetworks"}],"cvss":{"score":6.3,"severity":"medium","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:L/VI:L/VA:N/SC:N/SI:N/SA:N","version":"4.0"},"cwes":[{"id":"CWE-295","name":"Improper Certificate Validation"}],"description":"The server certificate was not verified when an Arc agent connected to a Guardian or CMC.\n\nA malicious actor could perform a man-in-the-middle attack and intercept the communication between the Arc agent and the Guardian or CMC. This could result in theft of the client token and sensitive information (such as assets and alerts), impersonation of the server, or injection of spoofed data (such as false asset information or vulnerabilities) into the Guardian or CMC.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":null,"headline":"Lack of TLS certificate validation when connecting Arc to a Guardian or CMC, in Arc before v2.2.0","id":"CVE-2025-40896","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"security_feature_bypass","year":"2025"},"n_packages":0,"n_references":1,"next":{"headline":"Incorrect authorization for Threat Intelligence in Guardian/CMC before 26.0.0","id":"CVE-2025-40897"},"packages":[],"prev":{"headline":"HTML injection in Sensor Map in CMC before 25.6.0","id":"CVE-2025-40895"},"products":["Arc"],"published":"2026-03-04","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"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":"yes","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-03-04","vendors":["Nozomi Networks"]},"summary":"Attackers can intercept Arc agent communications via man-in-the-middle attacks due to missing TLS validation, stealing tokens and injecting spoofed data.","url":"https://insights.sbomify.com/CVE-2025-40896/"}