Skip to content
Systems

CVE-2026-31984

8.7
High
EPSS 0.51%Patch availableJul 9, 2026

Unauthenticated DoS via unbounded audit log input exhausting disk space.

common questions

Is CVE-2026-31984 being exploited?

Not confirmed. CVE-2026-31984 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.51% probability of exploitation in the next 30 days.

How severe is CVE-2026-31984?

CVE-2026-31984 is rated High with a CVSS score of 8.7. 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-31984?

Yes. A fix has been recorded for CVE-2026-31984. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.

What does CVE-2026-31984 affect?

CVE-2026-31984 affects Systems with vulnerable audit logging, Custom or third-party apps that record unbounded audit entries. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2026-31984?

Apply vendor patch when available; meanwhile enforce input size limits, enable log rotation/disk quotas, monitor disk usage.

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

executive summary
technical analysis
affected
Systems with vulnerable audit loggingCustom or third-party apps that record unbounded audit entries
impact

Unauthenticated attacker can submit oversized audit entries to exhaust disk, causing denial-of-service and system inoperability.

action required

Immediate action required

affected versions
Nozomi Networks CMC
  • affected< 26.2.0
Nozomi Networks Guardian
  • 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