Loading story…
A high-severity flaw tracked as CVE-2026-54725 affected bank-vaults/vault-secrets-webhook before version 1.23.1, allowing attacker-controlled vault-addr Kubernetes annotations to trigger outbound HTTP requests during admission and send a ServiceAccount JWT to an attacker-controlled endpoint. The issue created a server-side request forgery condition and, in some configurations, could enable cluster-wide service account token theft through the Kubernetes TokenRequest API when the vault-serviceaccount setting was used.
The project fixed the issue in v1.23.1 by no longer trusting object-supplied Vault addresses by default and validating them against an operator-controlled allowlist before any network connection or token minting occurs. The patch also blocks unsafe targets such as metadata endpoints, restricts private-address use unless explicitly allowed, rejects userinfo-bearing addresses, and prevents the vault-skip-verify annotation from disabling TLS verification unless operators explicitly enable that behavior; deployments that relied on per-object Vault address overrides may now be denied at admission time.
See affected versions and whether adversaries are exploiting it.
4 events from the most recent confirmed update back to the earliest known activity.
The CVE record for CVE-2026-54725 was modified to add an additional reference and SSVC information. The SSVC entry listed exploitation as PoC, automatable as no, technical impact as partial, and identified the role as CISA Coordinator.
GitHub security-advisories recorded CVE-2026-54725 for bank-vaults vault-secrets-webhook, describing an SSRF flaw in versions before 1.23.1 where attacker-controlled Vault addresses supplied via Kubernetes annotations could receive a ServiceAccount JWT. The CVE linked the issue to the fixed 1.23.1 release and the patch commit.
bank-vaults released vault-secrets-webhook version 1.23.1, making object-supplied vault-addr values untrusted by default and requiring allowlist validation. The release also stopped vault-skip-verify annotations from disabling TLS verification unless explicitly permitted by operator configuration.
A bank-vaults commit introduced validation for object-supplied Vault addresses and gated object-controlled TLS skip-verification, preventing outbound connections and ServiceAccount token minting to untrusted attacker-controlled endpoints. The change added allowlist and private-address controls and tests covering rejected IMDS and attacker URLs.
Vulnerabilities, threat actors, malware, products, organizations, breaches, and observables Mallory has linked to this story. Indicator values are masked here and available in full in the app.
Indicator values are masked on this page. See the values in Mallory Domains, IPs, hashes, and URLs are exportable to your SIEM.
See whether adversaries are exploiting this yet, and where the affected versions run in your environment.
3 references tracked. Mallory keeps watching after this page renders.
cvefeed.io
Open sourcegithub.com
Open sourcegithub.com
Open sourceMap indicators from this story to your assets and identify affected systems in minutes.
Every observed campaign, victim, and pivot linked to actors named in this story.
Malware, exploits, and IOCs connected to the activity described here.
YARA, Sigma, and Snort rules deployed to your SIEM as soon as they’re published.
Get matching new stories delivered to your team as they break — not the next morning.
Ask questions about this story and take action on the answers.
Other stories Mallory is tracking that overlap on entities, sources, or topic labels.
Datadog Security Labs detailed **CVE-2020-8561**, an unpatchable Kubernetes weakness that can turn the `kube-apiserver` into a high-impact server-side request forgery (**SSRF**) proxy. An attacker with valid Kubernetes credentials and elevated privileges, typically `cluster-admin`, can abuse a `ValidatingWebhookConfiguration` object to make the API server send requests to attacker-controlled or internal destinations. By combining that behavior with profiling-enabled log-level changes, the attacker can cause the API server to log full responses from those privileged network requests rather than merely confirming whether a port is reachable. The issue is most dangerous when the Kubernetes control plane sits in a more trusted network segment than worker nodes, including managed Kubernetes environments hosted inside cloud provider networks. Because there is no straightforward code fix, defenders are being urged to reduce exposure through configuration and architecture changes, notably disabling API server profiling with: ```bash --profiling=false ``` and ensuring that SSRF originating from the API server cannot reach sensitive internal services or metadata endpoints.
Jun 29, 2026
HashiCorp disclosed **CVE-2026-8715**, a critical flaw in **Vault Secrets Operator** that allows arbitrary file reads and credential exfiltration through the AppRole `secretIDPath` configuration. The vulnerability affects versions **1.3.0 through 1.4.1** and can be exploited by a tenant with limited Kubernetes RBAC permissions to read files from the operator pod filesystem and send their contents to a tenant-controlled endpoint. The issue could expose sensitive credentials and create a path to privilege escalation inside a Kubernetes cluster. HashiCorp addressed the flaw in **Vault Secrets Operator 1.5.0**, and the **Canadian Centre for Cyber Security** issued advisory **AV26-817**, referencing HashiCorp bulletin **HCSEC-2026-28** and urging administrators to review the advisory and apply the available update.
Aug 15, 2026
HashiCorp disclosed two security issues in Vault affecting availability and access controls. One advisory, `HCSEC-2026-05`, warns that Vault's KVv2 engine is vulnerable to a policy bypass involving metadata and secret deletion operations, creating a denial-of-service condition and allowing actions that should have been restricted by policy. A second advisory, `HCSEC-2026-08`, says Vault is also vulnerable to denial of service through unauthenticated root token generation and rekey operations. Together, the disclosures indicate that both authenticated policy enforcement paths and unauthenticated operational workflows in Vault can be abused to disrupt service, underscoring the need for organizations running Vault to review affected deployments and apply vendor guidance promptly.
Jun 29, 2026