- Veröffentlicht
- 16.10.2026 11:54
- Zuletzt geändert
- 16.10.2026
- EPSS (30 Tage)
- unbekannt
- CVSS-Vektor
- CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:L/I:L/A:N
Beschreibung
Originaltext der Quelle, nicht übersetzt.
## In a nutshell
ExternalSecrets allowed 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 specified 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.
## Workarounds
- Add admission control logic to prevent the use of Templates targeting undesired Types
- Remove Service Account Token generation via kube-controller-manager flags
- Restrict User RBAC on production clusters and sensitive namespaces
## Background
CVE-2026-42876's fix covered a validation before the secret's create/update. The guard introduced in the fix can be bypassed by using a target not matching the exact string "Annotations", but behaving the same way (`metadata.annotations` (or `metadata.annotations.kubernetes.io/service-account.name`, or mixed-case `Metadata.Annotations`).
We are now _rejecting_ path style for secrets to prevent this from happening.
Betroffene Pakete im beobachteten Stack
Gogithub.com/external-secrets/external-secrets2.4.0 → 2.13.0GHSA-v6x5-m838-gqph
Empfohlene Prüfung
- Feststellen, ob und in welcher Version die betroffenen Pakete in Ihren Systemen, Images und Abhängigkeiten vorkommen.
- Wo eine Fix-Version genannt ist: aktualisieren. Wo nicht: Hersteller-Advisory und Referenzen auf Workarounds prüfen.
- Erreichbarkeit beachten: Der Angriffsweg (Netzwerk · mit Login) ist aus dem CVSS-Vektor abgeleitet.
Diese Seite sagt nichts darüber, ob Ihre Systeme betroffen sind. Das klärt erst eine Prüfung Ihrer Versionen.