Bug 2431873 (CVE-2026-22822) - CVE-2026-22822 external-secrets: External Secrets Operator: Cross-Namespace Secret Disclosure via `getSecretKey` Function
Summary: CVE-2026-22822 external-secrets: External Secrets Operator: Cross-Namespace S...
Keywords:
Status: NEW
Alias: CVE-2026-22822
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: All
OS: Linux
high
high
Target Milestone: ---
Assignee: Product Security DevOps Team
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2026-01-21 22:02 UTC by OSIDB Bzimport
Modified: 2026-01-22 18:48 UTC (History)
0 users

Fixed In Version:
Clone Of:
Environment:
Last Closed:
Embargoed:


Attachments (Terms of Use)

Description OSIDB Bzimport 2026-01-21 22:02:10 UTC
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.


Note You need to log in before you can comment on or make changes to this bug.