Is CVE-2026-31985 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2026-31985 being exploited in the wild.

How severe is CVE-2026-31985?

High severity, with a CVSS score of 8.1, published 9 July 2026.

Which products and versions are affected?

Nozomi Networks Remote Collector before v26.2.0.

Is there a fix for CVE-2026-31985?

No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.

How is CVE-2026-31985 attacked?

It is attacked over the network, in a network appliance.

Am I affected by CVE-2026-31985?

Check whether you run Nozomi Networks Remote Collector at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-31985: Nozomi Networks Remote Collector disabled TLS verification in n2os-tui

CVE-2026-31985 · Severity: high · CVSS 8.1 · Published 2026-07-09

Nozomi Networks Remote Collector, a tool used to gather data from industrial networks, contains a flaw where it fails to verify the security certificates of the central management servers it connects to. This allows a malicious actor positioned on the network to intercept or tamper with the data being sent between systems. An attacker could use this to steal authentication tokens, provide false information about network vulnerabilities, or disrupt monitoring operations.

Vendors: Nozomi Networks.

Quick answers

Is CVE-2026-31985 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-31985 being exploited in the wild.
How severe is CVE-2026-31985?: High severity, with a CVSS score of 8.1, published 9 July 2026.
Which products and versions are affected?: Nozomi Networks Remote Collector before v26.2.0.
Is there a fix for CVE-2026-31985?: No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
How is CVE-2026-31985 attacked?: It is attacked over the network, in a network appliance.
Am I affected by CVE-2026-31985?: Check whether you run Nozomi Networks Remote Collector at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

Technical details

A vulnerability exists in the Nozomi Networks Remote Collector where the n2os-tui configuration utility generates configurations that explicitly disable TLS certificate verification (CWE-671). This occurs when connecting the Remote Collector to an upstream Guardian or Central Management Console (CMC). A network-positioned attacker can perform a man-in-the-middle (MitM) attack to intercept communications, steal synchronization tokens, or inject spoofed asset and vulnerability data. The issue is resolved in version 26.2.0; a manual workaround involves editing the 'n2os.conf.user' file to remove the '!' prefix from the upstream endpoint entry.

Affected products

Nozomi Networks Remote Collector before v26.2.0

Timeline

2026-07-07: advisory: Initial internal advisory published by Nozomi Networks
2026-07-09: disclosed: CVE published to NVD

References

https://security.nozominetworks.com/NN-2026:12-01

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.