dbcve.org
Server-Side Request Forgery (SSRF)Weakness · CWE-918

CVE-2026-54725

CRITICAL · 9.6 CVSS v3.1 Published 2026-07-31
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable Zero-click 3 weeks old

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

The vault-secrets-webhook accepts the vault.security.banzaicloud.io/vault-addr annotation without validation, allowing an attacker who can create or modify Pods to specify an attacker-controlled Vault address. When the webhook processes such Pods, it sends the ServiceAccount JWT to the malicious Vault endpoint, enabling credential theft and potential privilege escalation within the cluster.

MitigationUpgrade vault-secrets-webhook to version 1.23.1 or later. Additionally, implement network policies to restrict the webhook's outbound network access and validate that vault-addr annotations point only to trusted endpoints.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
Low
User interaction
None
Scope
Changed
Confidentiality
High
Integrity
High
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify vault-secrets-webhook installation
    Run 'kubectl get pods -A | grep vault-secrets-webhook' or 'kubectl get deployments -A | grep vault-secrets-webhook' to find the webhook pod or deployment.
    Affected if The webhook is not installed in the cluster.
  2. Determine vault-secrets-webhook version
    Check the image tag of the vault-secrets-webhook pod or deployment: 'kubectl get deployment -A -o jsonpath="{.items[?(@.metadata.name=='vault-secrets-webhook')].spec.template.spec.containers[0].image}"' or inspect the pod directly.
    Affected if The installed version is earlier than 1.23.1.
  3. Find ConfigMaps with vault-addr annotation
    Run 'kubectl get configmaps -A -o jsonpath="{.items[?(@.metadata.annotations.vault\.security\.banzaicloud\.io/vault-addr)]}"' to list ConfigMaps containing the annotation.
    Affected if ConfigMaps exist with the vault.security.banzaicloud.io/vault-addr annotation pointing to an untrusted or external address.
  4. Find Secrets with vault-addr annotation
    Run 'kubectl get secrets -A -o jsonpath="{.items[?(@.metadata.annotations.vault\.security\.banzaicloud\.io/vault-addr)]}"' to list Secrets containing the annotation.
    Affected if Secrets exist with the vault.security.banzaicloud.io/vault-addr annotation pointing to an untrusted or external address.
  5. Review annotation values for suspicious addresses
    For each identified ConfigMap or Secret, inspect the annotation value: 'kubectl get configmap <name> -n <namespace> -o jsonpath="{.metadata.annotations.vault\.security\.banzaicloud\.io/vault-addr}"'. Look for addresses that are not the intended Vault server, especially external or attacker-controlled IPs/domains.
    Affected if The vault-addr annotation points to any address other than the legitimate, cluster-internal Vault server.

You are affected if vault-secrets-webhook version is below 1.23.1 AND any ConfigMap or Secret in the cluster uses the vault.security.banzaicloud.io/vault-addr annotation with an untrusted or external address, as this enables token theft via JWT exfiltration.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade vault-secrets-webhook to version 1.23.1 or later. Additionally, implement network policies to restrict the webhook's outbound network access and validate that vault-addr annotations point only to trusted endpoints.

Recommended fix High confidence

1.23.1

  1. Identify the namespace where vault-secrets-webhook is deployed (typically 'vault-secrets-operator' or similar)
  2. Check the current version of the vault-secrets-webhook deployment: kubectl get deployment -n <namespace> -o jsonpath='{.items[*].spec.template.spec.containers[*].image}'
  3. Upgrade the vault-secrets-webhook to version 1.23.1 by updating the Deployment: kubectl set image deployment/<deployment-name> vault-secrets-webhook=banzaicloud/vault-secrets-webhook:1.23.1 -n <namespace>
  4. Verify the upgrade was successful: kubectl rollout status deployment/<deployment-name> -n <namespace>
  5. Confirm the new version is running: kubectl get deployment -n <namespace> -o jsonpath='{.items[*].spec.template.spec.containers[*].image}'

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-54725 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-54725 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data