CVE-2026-22822 External Secrets Operator insecurely retrieves secrets through the getSecretKey templating function

Critical 9.3 Published Updated

Attackers can bypass namespace isolation to read secrets from other namespaces using the getSecretKey template function in External Secrets Operator.

Exploited in the wild
Not known
Login needed
Any signed-in user
Attackable
Local or same network only
Victim action needed
Not needed
Fix
Available

What is CVE-2026-22822?

CVE-2026-22822 is a critical missing authorization vulnerability in external-secrets, published on 21 Jan 2026. It can only be exploited from the same machine or local network, with no action from the victim.

Official description

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.

Weakness: CWE-863

Which versions are affected by CVE-2026-22822?

3 open source packages ship an affected version, including github.com/external-secrets/external-secrets. It affects 1 product.

PackageAffectedFixed in
github.com/external-secrets/external-secrets GoFrom 0.20.21.2.0
github.com/external-secrets/external-secrets GoFrom 0.20.21.2.0
github.com/external-secrets/external-secrets GoFrom 0.20.21.2.0

Products include External-Secrets External Secrets Operator.

How do I fix CVE-2026-22822?

Upgrade github.com/external-secrets/external-secrets to 1.2.0 or later.

Upgrade, and check permissions on every request on the server, not only in the interface. More about Missing authorization.

Is CVE-2026-22822 being exploited?

There is no known exploitation of CVE-2026-22822 in the wild and no public exploit code.

Sources

Also known as GHSA-77v3-r3jw-j2v2, GO-2026-4330, MINI-gw6m-9vh7-f9qw.

Is CVE-2026-22822 in your software?

Upload an SBOM and sbomify checks it against every vulnerability here, every day.

Check your SBOMs for free