CVE-2025-62159: External Secrets Operator's BeyondTrust Provider has Insecure Secret Retrieval
External Secrets Operator reads information from a third-party service and automatically injects the values as Kubernetes Secrets. A vulnerability was discovered in the BeyondTrust provider implementation for External Secrets Operator versions 0.10.1 through 0.19.2. The provider previously retrieved Kubernetes secrets directly, without validating the namespace context or the type of secret store. This allowed unauthorized cross-namespace secret access, violating security boundaries and potentially exposing sensitive credentials. In version 0.20.0, the provider code was updated to use the resolvers.SecretKeyRef utility, which enforces namespace validation and only allows cross-namespace access for ClusterSecretStore types. This ensures secrets are only retrieved from the correct namespace, mitigating the risk of unauthorized access. All users should upgrade to the latest version containing this fix. As a workaround, use a policy engine such as Kyverno or OPA to prevent using BeyondTrust provider and/or validate the (Cluster)SecretStore and ensure the namespace may only be set when using a ClusterSecretStore.
Affected Software
Event History
Frequently Asked Questions
What is the severity of CVE-2025-62159?
CVE-2025-62159 has been classified as a critical severity vulnerability.
How do I fix CVE-2025-62159?
To fix CVE-2025-62159, upgrade the BeyondTrust External Secrets Operator to version 0.19.3 or later.
What versions of BeyondTrust External Secrets Operator are affected by CVE-2025-62159?
CVE-2025-62159 affects BeyondTrust External Secrets Operator versions from 0.10.1 to 0.19.2.
What impact does CVE-2025-62159 have on Kubernetes Secrets?
CVE-2025-62159 can lead to unauthorized access to sensitive information in Kubernetes Secrets.
Is there a workaround for CVE-2025-62159?
There is no documented workaround for CVE-2025-62159; upgrading to a secure version is necessary.