CVE-2026-34265
Critical RCE in unspecified product enabling remote full system compromise
Is CVE-2026-34265 being exploited?
Not confirmed. CVE-2026-34265 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.57% probability of exploitation in the next 30 days.
How severe is CVE-2026-34265?
CVE-2026-34265 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-34265?
Not known from our data. No patch reference has been recorded for CVE-2026-34265, 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-34265 affect?
CVE-2026-34265 affects Unspecified product(s) - details pending, All deployments of affected software once identified. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-34265?
Inventory for affected software, isolate suspected hosts, apply vendor patch when released, enable EDR/IDS rules.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Remote code execution enabling full system takeover, data theft, persistence and malware installation via network-accessible flaw.
Immediate action required
- affectedKRNL64NUC 7.22
- affected7.22EXT
- affectedKRNL64UC 7.22
- affected7.22EXT2
- affected7.22EXT3
- affected7.53
- affected7.54
- affected7.77
- affected7.89
- affected7.93
- affected8.04
- affected9.16 9.18
- affected9.19
- affectedKERNEL 7.22
- affected9.16
- affected9.18
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.