Skip to content
Applications

CVE-2026-64597

9.8
Critical
EPSS 0.36%Aug 9, 2026

High-severity (9.8) CVE with details withheld; treat as critical remote compromise risk.

common questions

Is CVE-2026-64597 being exploited?

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

How severe is CVE-2026-64597?

CVE-2026-64597 is rated Critical with a CVSS score of 9.8. 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-64597?

Not known from our data. No patch reference has been recorded for CVE-2026-64597, 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-64597 affect?

CVE-2026-64597 affects Unknown affected products (details withheld), All internet-facing instances of the vendor product until identified. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2026-64597?

Inventory assets, isolate exposed systems, deploy vendor patches/mitigations when available

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

executive summary
technical analysis
affected
Unknown affected products (details withheld)All internet-facing instances of the vendor product until identified
impact

Likely remote code execution allowing attackers to run arbitrary code and achieve full system/root compromise remotely.

action required

Immediate action required

affected versions
Linux Linux
  • affected>= 433042a91f9373241307725b52de573933ffedbf and < 037511726228aaf165c7067ff2bfc88eaecdf1f3
  • affected>= 4f1fffa2376922f3d1d506e49c0fd445b023a28e and < 0aa97edf7c347c0f54e7e60c4740574b8120c66a
  • affected>= 4f1fffa2376922f3d1d506e49c0fd445b023a28e and < d15d83125007f673aec4323e1bbbaaffbe87ea13
  • affected>= 4f1fffa2376922f3d1d506e49c0fd445b023a28e and < b18ed621dbfceecea5539848cddcb9272c9a61e1
  • affected>= 4f1fffa2376922f3d1d506e49c0fd445b023a28e and < f96e1cdcb63ed3321142ff2fcdf784e32cda8fee
  • affected>= 6.6.32 and < 6.6.145
  • affected6.8
vendor says fixed in< 6.8, >= 6.6.145 and <= 6.6.*, >= 6.12.96 and <= 6.12.*, >= 6.18.39 and <= 6.18.*, >= 7.1.4 and <= 7.1.*, >= 7.2 and <= *

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