CVE-2026-40920
Critical RCE vulnerability enabling full system compromise
Is CVE-2026-40920 being exploited?
Not confirmed. CVE-2026-40920 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.39% probability of exploitation in the next 30 days.
How severe is CVE-2026-40920?
CVE-2026-40920 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-40920?
Yes. A fix has been recorded for CVE-2026-40920. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-40920 affect?
CVE-2026-40920 affects Unknown / details withheld by source. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-40920?
Isolate affected hosts, apply vendor patch when available, increase monitoring and block suspicious traffic.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Unauthenticated remote code execution allowing attackers to run arbitrary code, escalate to root, deploy malware, and exfiltrate data.
Immediate action required
- affected<= 2.8.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.