← Übersicht Flux

Flux notification-controller GCR Receiver missing email validation allows unauthorized reconciliation triggering

CVE-2026-40109 · DHI-2a3v-e3nd-5k2b-wtrx · GHSA-h9cx-xjg6-5v2w · GO-2026-5419

Niedrig · CVSS 3.1 Netzwerk · mit Login Fix verfügbar

Veröffentlicht
09.04.2026 23:06
Zuletzt geändert
18.11.2026
EPSS (30 Tage)
0.1 %
CVSS-Vektor
CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:N/I:L/A:N

Beschreibung

Originaltext der Quelle, nicht übersetzt.

Flux notification-controller is the event forwarder and notification dispatcher for the GitOps Toolkit controllers. Prior to 1.8.3, the gcr Receiver type in Flux notification-controller does not validate the email claim of Google OIDC tokens used for Pub/Sub push authentication. This allows any valid Google-issued token, to authenticate against the Receiver webhook endpoint, triggering unauthorized Flux reconciliations. Exploitation requires the attacker to know the Receiver's webhook URL. The webhook path is generated as /hook/sha256sum(token+name+namespace), where the token is a random string stored in a Kubernetes Secret. There is no API or endpoint that enumerates webhook URLs. An attacker cannot discover the path without either having access to the cluster and permissions to read the Receiver's .status.webhookPath in the target namespace, or obtaining the URL through other means (e.g. leaked secrets or access to Pub/Sub config). Upon successful authentication, the controller triggers a reconciliation for all resources listed in the Receiver's .spec.resources. However, the practical impact is limited: Flux reconciliation is idempotent, so if the desired state in the configured sources (Git, OCI, Helm) has not changed, the reconciliation results in a no-op with no effect on cluster state. Additionally, Flux controllers deduplicate reconciliation requests, sending many requests in a short period results in only a single reconciliation being processed. This vulnerability is fixed in 1.8.3.

Betroffene Pakete im beobachteten Stack

CVEfluxcd/notification-controllerkein Fix bekanntCVE-2026-40109
Gogithub.com/fluxcd/notification-controller1.8.3GHSA-h9cx-xjg6-5v2w
Gogithub.com/fluxcd/notification-controller1.8.3GO-2026-5419
Weitere betroffene Pakete (5)
Docker Hardened Images:Alpine:3.23fluxcd-notification-controllerkein Fix bekanntDHI-2a3v-e3nd-5k2b-wtrx
Docker Hardened Images:Alpine:3.23fluxcd-notification-controller-devkein Fix bekanntDHI-2a3v-e3nd-5k2b-wtrx
Docker Hardened Images:Alpine:3.23fluxcd-notification-controller-fipskein Fix bekanntDHI-2a3v-e3nd-5k2b-wtrx
Docker Hardened Images:Alpine:3.23fluxcd-notification-controller-fips-devkein Fix bekanntDHI-2a3v-e3nd-5k2b-wtrx
openSUSE:Leap 16.0govulncheck-vulndb0.0.20260723T184607-160000.1.1openSUSE-SU-2026:21483-1

Empfohlene Prüfung

  1. Feststellen, ob und in welcher Version die betroffenen Pakete in Ihren Systemen, Images und Abhängigkeiten vorkommen.
  2. Wo eine Fix-Version genannt ist: aktualisieren. Wo nicht: Hersteller-Advisory und Referenzen auf Workarounds prüfen.
  3. 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.