Skip to main content
VulnerabilityPublished

CVE-2025-40896: Nozomi Networks Arc · Improper Certificate Validation

Affects Nozomi Networks ArcSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 6.3 Medium : upgrade to 2.2.0 when convenient.

Data as of 30 Oct 2026, 11:52 UTC

CVSS 4.0 base score
6.3Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.1% chance of exploitation in 30 days – higher than 1% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 2.2.0
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

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 4 Mar 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 30 Oct 2026.

What to do

Upgrade Nozomi Networks Arc to 2.2.0.

Affected software

ProductAffectedFixed in
Nozomi NetworksArcAffected
  • <2.2.0
Fixed in
  • 2.2.0

AI-suggested

To mitigate CVE-2025-40896, organizations should immediately verify if their Nozomi Networks Arc deployments are affected and monitor vendor communications for official patches or updates. In the absence of a patch, network-level mitigations should be applied, including enforcing strict TLS interception policies and deploying network segmentation to isolate Arc agents and Guardian/CMC communications from untrusted networks. Implementing VPNs or secure tunnels with mutual authentication can help protect the communication channel. Additionally, organizations should enable and review detailed logging and anomaly detection on network traffic between Arc components to identify potential MitM attempts. Employing certificate pinning or manual certificate validation where possible can reduce the risk of accepting spoofed certificates. Regularly auditing and rotating client tokens and credentials can limit the window of exposure if tokens are compromised. Finally, educating security teams about this vulnerability and incorporating it into incident response plans will improve preparedness against exploitation attempts.

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.

References

Community reviews

Loading reviews…