Skip to content
Cryptography

CVE-2026-31985

8.3
High
EPSS 0.20%Jul 9, 2026

n2os-tui disables TLS verification for Remote Collector connections, enabling MitM and token theft.

common questions

Is CVE-2026-31985 being exploited?

Not confirmed. CVE-2026-31985 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.20% probability of exploitation in the next 30 days.

How severe is CVE-2026-31985?

CVE-2026-31985 is rated High with a CVSS score of 8.3. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.

Is there a patch for CVE-2026-31985?

Not known from our data. No patch reference has been recorded for CVE-2026-31985, which is not the same as no patch existing — a fix may have shipped without a tagged reference, or after this record was written. The vendor advisory is the only authority on whether a fix exists, and mitigations may be available regardless.

What does CVE-2026-31985 affect?

CVE-2026-31985 affects n2os-tui, Remote Collector, Guardian, CMC. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2026-31985?

Stop using n2os-tui configs; enforce TLS verification, restrict collector access, and rotate sync tokens.

Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.

executive summary
technical analysis
affected
n2os-tuiRemote CollectorGuardianCMC
impact

Enables MitM of Remote Collector↔Guardian/CMC, theft of sync tokens, server impersonation, spoofed data injection, and data-flow disruption.

action required

Immediate action required

affected versions
Nozomi Networks Remote Collector
  • affected< 26.2.0

As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.

how to fix
Remediation steps are tailored for users whose stack is affected. Add this technology to your stack to see the fix checklist.
references
get alerted

Track only the vulnerabilities that affect your infrastructure.

start for free