CVE-2026-54725
vault-secrets-webhook can leak ServiceAccount JWTs to attacker-controlled Vault addresses.
Is CVE-2026-54725 being exploited?
Not confirmed. CVE-2026-54725 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-54725?
CVE-2026-54725 is rated Critical with a CVSS score of 9.6. 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-54725?
Yes. A fix has been recorded for CVE-2026-54725. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-54725 affect?
CVE-2026-54725 affects vault-secrets-webhook <1.23.1, Kubernetes clusters using BanzaiCloud webhook, Pods annotated with vault.security.banzaicloud.io/*. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-54725?
Upgrade to v1.23.1, remove untrusted vault annotations, rotate SA tokens and audit Vault endpoints.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Attackers can exfiltrate ServiceAccount JWTs via crafted annotations, obtain Vault access, read/inject secrets and potentially compromise the cluster.
Immediate action required
- affected< 1.23.1
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.