# CVE-2026-26287: External Secrets Operator: label enforcement bypass in webhook generator enables secret exfiltration

> A bug in External Secrets Operator bypasses label enforcement, allowing attackers to exfiltrate secrets that should have been restricted.

- **Severity:** High 7.1 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 6 Oct 2026
- **Updated:** 6 Oct 2026
- **Also known as:** GHSA-q7hv-xx6h-q2x8, GO-2026-6667, MINI-fv26-wcpg-f8wr

## What is CVE-2026-26287?

CVE-2026-26287 is a high-severity vulnerability in external-secrets, published on 6 Oct 2026. Any signed-in user can exploit it over the 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.10.0 and prior to version 1.3.2, a bug in the `webhook` generator initialization order incorrectly cleared the label-enforcement flag (`EnforceLabels`) after it was set, resulting in the provider-side check for `external-secrets.io/type=webhook` being skipped (and the operation to succeed while it should have failed with `secret does not contain needed label 'external-secrets.io/type: webhook'. Update secret label to use it with webhook`. Version 1.3.2 contains a patch.

Weakness: CWE-696 (Incorrect Behavior Order)

## Which versions are affected by CVE-2026-26287?

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


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `github.com/external-secrets/external-secrets` | Go | From 0.10.0 | 1.3.2 |
| `github.com/external-secrets/external-secrets` | Go | From 0.10.0 | 1.3.2 |
| `github.com/external-secrets/external-secrets` | Go | From 0.10.0 | 1.3.2 |

## How do I fix CVE-2026-26287?

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

## Is CVE-2026-26287 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-26287 and fix it if it is affected.

What it is: CVE-2026-26287 is a high-severity vulnerability in external-secrets, published on 6 Oct 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-26287 in the wild and no public exploit code.

Affected packages and fixed versions:
- github.com/external-secrets/external-secrets (Go): affected from 0.10.0; fixed in 1.3.2
- github.com/external-secrets/external-secrets (Go): affected from 0.10.0; fixed in 1.3.2
- github.com/external-secrets/external-secrets (Go): affected from 0.10.0; fixed in 1.3.2

Task:
1. 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.
2. 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.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-26287/ (Markdown: https://insights.sbomify.com/CVE-2026-26287/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-26287
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-26287
- OSV: https://osv.dev/vulnerability/CVE-2026-26287

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-26287/
Summaries are generated and may contain mistakes; the official description above is the record.