جزئیات آسیب‌پذیری

External Secrets Operator reads information from a third-party service and automatically injects the values as Kubernetes Secrets. Starting in version 0.20.2 and prior to version 1.2.0, the `getSecretKey` template function, while introduced for senhasegura Devops Secrets Management (DSM) provider, has the ability to fetch secrets cross-namespaces with the roleBinding of the external-secrets controller, bypassing our security mechanisms. This function was completely removed in version 1.2.0, as everything done with that templating function can be done in a different way while respecting External Secrets Operator's safeguards As a workaround, use a policy engine such as Kubernetes, Kyverno, Kubewarden, or OPA to prevent the usage of `getSecretKey` in any ExternalSecret resource.

• https://github.com/external-secrets/external-secrets/security/advisories/GHSA-77v3-r3jw-j2v2 x_refsource_CONFIRM
• https://github.com/external-secrets/external-secrets/issues/5690 x_refsource_MISC
• https://github.com/external-secrets/external-secrets/pull/3895 x_refsource_MISC
• https://github.com/external-secrets/external-secrets/commit/17d3e22b8d3fbe339faf8515a95ec06ec92b1feb x_refsource_MISC
• https://github.com/external-secrets/external-secrets/releases/tag/v1.2.0 x_refsource_MISC
• https://access.redhat.com/security/cve/CVE-2026-22822 vdb-entryx_refsource_REDHAT
• https://bugzilla.redhat.com/show_bug.cgi?id=2431873 issue-trackingx_refsource_REDHAT
• https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-22822.json x_sadp-csaf-vex