Loading vulnerability…
CVE-2026-54725 is a server-side request forgery vulnerability in bank-vaults vault-secrets-webhook prior to version 1.23.1. The webhook, which performs secret injection for Kubernetes workloads, accepts a user-controlled Vault address through annotation parsing in parseVaultConfig() and subsequently uses that address when creating a Vault client during mutation flows. In the affected code path, annotation-controlled configuration can direct the webhook to connect to an attacker-controlled Vault endpoint. When combined with the service account selection annotation, this can cause the webhook to transmit a Kubernetes ServiceAccount JWT to that attacker-controlled endpoint. The flaw therefore allows untrusted annotation input to influence outbound server-side connections and exfiltrate authentication material.
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
No public exploits tracked yet. Mallory keeps watching.
No public exploit code observed for this vulnerability.
7 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.