# CVE-2026-54725: vault-addr annotation SSRF -- webhook makes outbound HTTP call to attacker URL during admission; vault-serviceaccount enables cluster-wide SA token theft via TokenRequest API

> An attacker can trigger server-side request forgery and steal service account tokens by manipulating Vault annotations in Kubernetes pods.

- **Severity:** Critical 9.6 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 31 Jul 2026
- **Updated:** 31 Jul 2026
- **Also known as:** GHSA-r2v3-8gwf-7ghm, GO-2026-6160

## What is CVE-2026-54725?

CVE-2026-54725 is a critical server-side request forgery vulnerability in bank-vaults vault-secrets-webhook, published on 31 Jul 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

vault-secrets-webhook is a Kubernetes mutating webhook that makes direct secret injection into Pods possible. Prior to 1.23.1, parseVaultConfig() in pkg/webhook/config.go accepts the vault.security.banzaicloud.io/vault-addr annotation, MutateConfigMap and MutateSecret call newVaultClient in pkg/webhook/webhook.go, and vault.security.banzaicloud.io/vault-serviceaccount can cause a ServiceAccount JWT to be sent to an attacker-controlled Vault address. This issue is fixed in version 1.23.1.

Weakness: CWE-918 (Server-Side Request Forgery)

## Which versions are affected by CVE-2026-54725?

3 open source packages ship an affected version, including github.com/bank-vaults/vault-secrets-webhook.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `github.com/bank-vaults/vault-secrets-webhook` | Go | All versions | 1.23.1 |
| `github.com/bank-vaults/vault-secrets-webhook` | Go | All versions | 1.23.1 |
| `github.com/bank-vaults/vault-secrets-webhook` | Go | All versions | 1.23.1 |

## How do I fix CVE-2026-54725?

Upgrade github.com/bank-vaults/vault-secrets-webhook to 1.23.1 or later.

## Is CVE-2026-54725 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-54725 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-54725 and fix it if it is affected.

What it is: CVE-2026-54725 is a critical server-side request forgery vulnerability in bank-vaults vault-secrets-webhook, published on 31 Jul 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-54725 exists.

Affected packages and fixed versions:
- github.com/bank-vaults/vault-secrets-webhook (Go): affected all versions; fixed in 1.23.1
- github.com/bank-vaults/vault-secrets-webhook (Go): affected all versions; fixed in 1.23.1
- github.com/bank-vaults/vault-secrets-webhook (Go): affected all versions; fixed in 1.23.1

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-54725/ (Markdown: https://insights.sbomify.com/CVE-2026-54725/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-54725
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-54725
- OSV: https://osv.dev/vulnerability/CVE-2026-54725

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-54725/
Summaries are generated and may contain mistakes; the official description above is the record.