# CVE-2026-31985: Weak cryptography in Remote Collector

> Disabled TLS validation allows man-in-the-middle attacks to steal tokens, impersonate servers, or inject spoofed data in Nozomi Remote Collector.

- **Severity:** High 8.3 (`CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:L/VI:H/VA:L/SC:L/SI:L/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 9 Jul 2026
- **Updated:** 9 Jul 2026
- **Also known as:** GHSA-r8ph-vcp7-p3mx

## What is CVE-2026-31985?

CVE-2026-31985 is a high-severity vulnerability in Nozomi Networks Remote Collector, published on 9 Jul 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

When the upstream Guardian or CMC was configured in the Remote Collector via n2os-tui, the generated configuration disabled TLS certificate verification, and no option was provided to enable it. A malicious actor could perform a man-in-the-middle attack and intercept the communication between the Remote Collector and the Guardian or CMC. This could result in theft of the sync token, impersonation of the server, injection of spoofed data (such as false asset information or vulnerabilities) into the Guardian or CMC, or disruption of the data flow between the Remote Collector and the Guardian or CMC.

Weakness: CWE-671 (Lack of Administrator Control over Security)

## Which versions are affected by CVE-2026-31985?


## How do I fix CVE-2026-31985?

No fix has been published for CVE-2026-31985 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-31985 being exploited?

There is no known exploitation of CVE-2026-31985 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-31985 and fix it if it is affected.

What it is: CVE-2026-31985 is a high-severity vulnerability in Nozomi Networks Remote Collector, published on 9 Jul 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-31985 in the wild and no public exploit code.

Affected product: Nozomi Networks Remote Collector. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. 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.
2. 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.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-31985/ (Markdown: https://insights.sbomify.com/CVE-2026-31985/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-31985
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-31985
- OSV: https://osv.dev/vulnerability/CVE-2026-31985

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-31985/
Summaries are generated and may contain mistakes; the official description above is the record.