github.com/external-secrets/external-secrets/apis
Affected
- introduced
0.1.0, fixed2.4.1(semver)
Fixed versions
2.4.1
Fix
- Fixed version
2.4.1go get github.com/external-secrets/external-secrets/[email protected]
Advisory
Also known as: CVE-2026-42876, GO-2026-5377
ExternalSecrets vulnerable to privilege escalation with secret overwriting
ExternalSecrets allows users to craft Service Account tokens for misconfigured Service Accounts in namespaces the users have access to.
Impact
A user who only has permission to create ExternalSecret resources can cause the operator to create a Secret that Kubernetes will automatically populate with a long-lived token for the sepcified service account. This effectively allows the user to impersonate any service account in the namespace without needing direct create permissions on TokenRequest or Secrets of that type.
The problem is mitigated in severity by the fact that the user must have pre-existing permissions already at almost the same level as the escalation later gives. The attacker cannot use this method to gain access to more information without other things also being misconfigured in the ESO installation.
Patches
Disallow this combination including the bootstrap token secret type.
Workarounds
Medium Basis: The source's own band: MODERATE
0.1.0, fixed 2.4.1 (semver)2.4.1
2.4.1go get github.com/external-secrets/external-secrets/[email protected]Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.
Check your own computer: guard packages check
Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0