CVE-2026-26056
Privilege escalation via unvalidated WASM in Yoke ATC; arbitrary Kubernetes resources.
Is CVE-2026-26056 being exploited?
Not confirmed. CVE-2026-26056 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.41% probability of exploitation in the next 30 days.
How severe is CVE-2026-26056?
CVE-2026-26056 is rated High with a CVSS score of 8.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-26056?
Yes. A fix has been recorded for CVE-2026-26056. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-26056 affect?
CVE-2026-26056 affects Yoke ATC (<0.19.0), Kubernetes clusters using Yoke. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-26056?
Upgrade to fixed Yoke version; validate URL handling in overrides.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Attacker with CR create/update perms can execute WASM in ATC context, enabling resource creation and potential cluster-admin privileges.
Patch when possible
- affected< 0.19.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.