SSRF (Server-Side Request Forgery) in github.com/bank-vaults/vault-secrets-webhook (CVE-2026-54725)
Summary
SSRF in github.com/bank-vaults/vault-secrets-webhook (CVE-2026-54725). Confidential information can be exposed externally. Exploitable via VaultAddrAnnotation. Mitigation: upgrade to 1.23.1 or later.
Original description
The description as published by the source.
Summary
The vault-secrets-webhook reads the vault.security.banzaicloud.io/vault-addr annotation from any ConfigMap or Secret being admitted and uses it as the Vault server address without any validation or allowlist. When a ConfigMap or Secret contains a value prefixed with vault:, the webhook's admission handler synchronously calls the Vault API at the attacker-supplied address from inside the webhook process during the admission review. The webhook additionally grants serviceaccounts/token:create cluster-wide, and the vault-serviceaccount annotation controls which ServiceAccount's JWT is fetched and sent to that address. An attacker who can create ConfigMaps or Secrets in a watched namespace can cause the webhook process to make arbitrary outbound HTTP connections and exfiltrate ServiceAccount JWTs.
Details
parseVaultConfig() at pkg/webhook/config.go:102-107 reads VaultAddrAnnotation unconditionally into vaultConfig.Addr:
if value, ok := annotations[common.VaultAddrAnnotation]; ok {
vaultConfig.Addr = value
}
No URL scheme validation, no hostname allowlist, no RFC-1918 or link-local filter.
MutateConfigMap and MutateSecret at pkg/webhook/configmap.go and pkg/webhook/secret.go call mw.newVaultClient(ctx, vaultConfig) when the object contains at least one vault:... value. Inside newVaultClient, at pkg/webhook/webhook.go:285:
clientConfig.Address = vaultConfig.Addr
vault.NewClientFromConfigWithContext then…
Source: GitHub Security Advisories (Global) NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-54725 has been found in github.com/bank-vaults/vault-secrets-webhook.
Attackers can target a specific entry point like VaultAddrAnnotation over the network to misuse the product.
Confidential information can be exposed externally. CVSS score: 9.6/10.
What to do: upgrade github.com/bank-vaults/vault-secrets-webhook to 1.23.1 or later.
If unsure, ask your IT team or search "github.com/bank-vaults/vault-secrets-webhook CVE-2026-54725" on the vendor's site.
CVE-2026-54725 (github.com/bank-vaults/vault-secrets-webhook) — CWE-918 / CVSS v3 9.6
Attack vector: remote (network-reachable) / no user interaction
Attack surface: VaultAddrAnnotation / vaultConfig.Addr / MutateConfigMap / MutateSecret
Patched: 1.23.1 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
SSRF (CWE-918) exists in github.com/bank-vaults/vault-secrets-webhook. Attackers reach the vulnerable code path via VaultAddrAnnotation.
Check the vendor advisory for the affected versions of github.com/bank-vaults/vault-secrets-webhook. Attack surface: VaultAddrAnnotation / vaultConfig.Addr / MutateConfigMap / MutateSecret.
Severity: Critical (CVSS 9.6/10). Confidential information can be exposed externally.
Update to 1.23.1.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'github.com/bank-vaults/vault-secrets-webhook' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'github.com/bank-vaults/vault-secrets-webhook' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
github.com/bank-vaults/vault-secrets-webhookを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade github.com/bank-vaults/vault-secrets-webhook to 1.23.1ステージング環境で 1.23.1 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- package github.com
- web github.com
- web github.com
- web github.com
- web github.com