ServiceAccount token theft via annotation-driven SSRF
Published Jul 31, 2026 · Updated Jul 31, 2026
SSRF in Bank-Vaults Vault Secrets Webhook 1.22.2 and earlier allows remote authenticated users to exfiltrate ServiceAccount tokens. parseVaultConfig accepts an unvalidated vault-addr annotation, and admission handlers send a selected ServiceAccount JWT to that address when processing a vault-prefixed Secret or ConfigMap. Create or update rights for Secrets or ConfigMaps are sufficient; the stolen token grants the Vault access assigned to that ServiceAccount.
Summary
What happened
SSRF in Bank-Vaults Vault Secrets Webhook 1.22.2 and earlier allows remote authenticated users to exfiltrate ServiceAccount tokens. parseVaultConfig accepts an unvalidated vault-addr annotation, and admission handlers send a selected ServiceAccount JWT to that address when processing a vault-prefixed Secret or ConfigMap. Create or update rights for Secrets or ConfigMaps are sufficient; the stolen token grants the Vault access assigned to that ServiceAccount.
The record
- CVE
- CVE-2026-54725
- Published
- Jul 31, 2026
- Updated
- Jul 31, 2026
- Vendor
- Bank-Vaults
- Product
- Vault Secrets Webhook
- Classifications
- CWE-918, T1552.007
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Jul 31, 2026CVE publishedPublication date reported by the CVE source.
- Jul 31, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=< 1.23.1
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
- GitHub advisory ConfigMap proof of conceptproof of concept · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo