CVE-2026-40868
Kyverno API call may leak serviceaccount token to attacker URL (confused deputy)
Is CVE-2026-40868 being exploited?
Not confirmed. CVE-2026-40868 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.29% probability of exploitation in the next 30 days.
How severe is CVE-2026-40868?
CVE-2026-40868 is rated High. 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-40868?
Yes. A fix has been recorded for CVE-2026-40868. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-40868 affect?
CVE-2026-40868 affects Kyverno < 1.16.4. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-40868?
Upgrade Kyverno to 1.16.4+
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Leaked Kyverno serviceaccount token to attacker-controlled URL via policy context, enabling token theft and potential cluster access.
Patch when possible
- affected< 1.16.4
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.