Bank-Vaults Webhook Flaw Exposes Secrets

The vault-secrets-webhook, a tool used to manage secrets in Kubernetes, contains a critical vulnerability tracked as CVE-2026-54725. This flaw allows an attacker to force the webhook to make arbitrary outbound HTTP connections and exfiltrate sensitive service account tokens by manipulating specific configuration annotations.

What's at Risk

This vulnerability affects users of the github.com/bank-vaults/vault-secrets-webhook package prior to version 1.23.1. Organizations deploying this webhook in Kubernetes environments are at risk, particularly those that allow untrusted users to create or modify ConfigMaps and Secrets within a watched namespace.

When this webhook is active, it monitors cluster resources for specific annotations. Because the software does not validate the destination address provided in these annotations, any environment utilizing the affected versions is exposed to potential credential theft and unauthorized network activity originating from within the cluster's internal admission process.

How the Flaw Works

This vulnerability is a form of Server-Side Request Forgery, or SSRF. In general, SSRF occurs when an application accepts user-supplied input to define a destination for a network request without proper validation or filtering. This allows an attacker to force the server to act as a proxy, sending requests to internal services that might not be exposed to the public internet or to external malicious endpoints.

When an application performs these requests synchronously during an admission review, it can lead to significant security failures. If the application also possesses elevated permissions—such as the ability to request tokens for service accounts—the SSRF can be leveraged to exfiltrate those tokens. By pointing the application toward an attacker-controlled server, the victim system inadvertently hands over sensitive authentication material, bypassing standard network perimeters and security policies.

How to Protect Your Systems

• Upgrade to vault-secrets-webhook version 1.23.1 or later immediately to patch the vulnerable admission handler.
• Restrict the ability to create or modify ConfigMaps and Secrets in namespaces monitored by the webhook using Kubernetes RBAC.
• Implement network policies to limit the egress traffic of the webhook pod, preventing it from initiating connections to unauthorized external or internal endpoints.
• Audit existing cluster annotations to identify any unauthorized use of the vault.security.banzaicloud.io/vault-addr or vault-serviceaccount configurations.
• Apply the principle of least privilege to the ServiceAccounts associated with the webhook to minimize the potential impact of a token compromise.

Given the critical CVSS score of 9.6 assigned to this vulnerability, prompt patching is essential. Exploitation of this flaw allows for the compromise of cluster-wide credentials, which can lead to full administrative control over the Kubernetes environment. Organizations should prioritize updating their infrastructure to neutralize this vector before it can be leveraged in a production environment.