{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2025-62159 in the wild and no public exploit code.","fix":"Upgrade to a fixed version.","what":"CVE-2025-62159 is a high-severity missing authorization vulnerability in external-secrets, published on 10 Oct 2025. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2025-62159 and fix it if it is affected.\n\nWhat it is: CVE-2025-62159 is a high-severity missing authorization vulnerability in external-secrets, published on 10 Oct 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2025-62159 in the wild and no public exploit code.\n\nAffected product: external-secrets. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. 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.\n2. 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.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2025-62159/ (Markdown: https://insights.sbomify.com/CVE-2025-62159/index.md)","id":"CVE-2025-62159","markdown":"https://insights.sbomify.com/CVE-2025-62159/index.md","name":"CVE-2025-62159","record":{"aliases":["GHSA-vf79-2pjx-phpp","MINI-pwqf-v92f-29qc"],"analysis":{"component_type":"container_or_infrastructure","fix_type":"upgrade","impacts":["data_read","security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"Kubernetes secrets operator","requires_auth":"none","summary":"Attackers can access secrets across namespaces without proper validation, exposing sensitive credentials in Kubernetes environments using the BeyondTrust provider.","user_interaction":"not_required","vuln_class":"missing_authorization"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":8.7,"severity":"high","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N","version":"4.0"},"cwes":[{"id":"CWE-284","name":"Improper Access Control"}],"description":"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`.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"External Secrets Operator's BeyondTrust Provider has Insecure Secret Retrieval","id":"CVE-2025-62159","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"missing_authorization","year":"2025"},"n_packages":0,"n_references":1,"next":{"headline":"youki container escape via \"masked path\" abuse due to mount race conditions","id":"CVE-2025-62161"},"packages":[],"prev":{"headline":"Frappe had attachments made by students to their assignments of type Text set to public","id":"CVE-2025-62158"},"products":["external-secrets"],"published":"2025-10-10","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2025-10-14","vendors":["external-secrets"]},"summary":"Attackers can access secrets across namespaces without proper validation, exposing sensitive credentials in Kubernetes environments using the BeyondTrust provider.","url":"https://insights.sbomify.com/CVE-2025-62159/"}