← Übersicht Crossplane

Crossplane: Signature verification TOCTOU allows installing unverified package content via mutable tag

GHSA-wfqx-gjrf-g28r · DHI-4blu-gjyt-osk7-nxfq · GO-2026-5709

Kritisch · CVSS 9.0 Netzwerk · ohne Login Kein Fix bekannt

Veröffentlicht
19.06.2026 22:47
Zuletzt geändert
16.11.2026
EPSS (30 Tage)
unbekannt
CVSS-Vektor
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:H/I:H/A:H

Beschreibung

Originaltext der Quelle, nicht übersetzt.

## Summary Crossplane allows package signature verification to be configured via the `ImageConfig` mechanism. When enabled, the package manager uses cosign to verify that packages are correctly signed before pulling and installing them. When a package is installed using a tag reference (e.g., a semantic version), a malicious OCI registry could serve a correctly signed image for verification, then subsequently serve an unsigned image for installation. This is possible because Crossplane resolves the tag reference separately for each step. This vulnerability is relevant only for users who do all three of the following: 1. Configure signature verification for packages, 2. Install packages using tag references rather than digests, and 3. Install packages from registries they do not control. ## Mitigation Installing packages by image digest rather than using tags avoids this issue. ## Fix The package manager has been updated to resolve tag references once and use the resulting digest for both signature verification and image fetching. This ensures that Crossplane pulls the same content that had its signature verified. The fix has been applied to Crossplane's `main` branch and backported to the v2.3 and v2.2 release branches; it will be released in v2.3.3 and v2.2.3. ## Note on Fixed Versions The Crossplane maintainers are *not* planning to backport the fix for this advisory to the 1.20 branch, for two reasons: 1. The advisory is relevant only when an alpha feature is enabled and configured, and has a reasonable mitigation that is already a security best practice. 2. Doing so would require a major refactor of package manager internals to match the refactor that shipped in Crossplane v2.2. Such a refactor would be an unnecessary risk given the policy that v1.20 receives only critical fixes and that this advisory affects only users of an alpha feature. ## Credits This issue was reported, independently, by @bugbunny-research and @tonghuaroot.

Betroffene Pakete im beobachteten Stack

Gogithub.com/crossplane/crossplanekein Fix bekanntGHSA-wfqx-gjrf-g28r
Gogithub.com/crossplane/crossplanekein Fix bekanntGO-2026-5709
Weitere betroffene Pakete (15)
Docker Hardened Images:Alpine:3.24crossplane-1.20kein Fix bekanntDHI-4blu-gjyt-osk7-nxfq
Docker Hardened Images:Alpine:3.24crossplane-1.20-devkein Fix bekanntDHI-4blu-gjyt-osk7-nxfq
Docker Hardened Images:Alpine:3.24crossplane-1.20-fipskein Fix bekanntDHI-4blu-gjyt-osk7-nxfq
Docker Hardened Images:Alpine:3.24crossplane-1.20-fips-devkein Fix bekanntDHI-4blu-gjyt-osk7-nxfq
Docker Hardened Images:Alpine:3.24crossplane-2.0kein Fix bekanntDHI-4blu-gjyt-osk7-nxfq
Docker Hardened Images:Alpine:3.24crossplane-2.0-devkein Fix bekanntDHI-4blu-gjyt-osk7-nxfq
Docker Hardened Images:Alpine:3.24crossplane-2.0-fipskein Fix bekanntDHI-4blu-gjyt-osk7-nxfq
Docker Hardened Images:Alpine:3.24crossplane-2.0-fips-devkein Fix bekanntDHI-4blu-gjyt-osk7-nxfq
Docker Hardened Images:Alpine:3.24crossplane-2.1kein Fix bekanntDHI-4blu-gjyt-osk7-nxfq
Docker Hardened Images:Alpine:3.24crossplane-2.1-devkein Fix bekanntDHI-4blu-gjyt-osk7-nxfq
Docker Hardened Images:Alpine:3.24crossplane-2.1-fipskein Fix bekanntDHI-4blu-gjyt-osk7-nxfq
Docker Hardened Images:Alpine:3.24crossplane-2.1-fips-devkein Fix bekanntDHI-4blu-gjyt-osk7-nxfq
Gogithub.com/crossplane/crossplane/v22.3.0-rc.0 → 2.3.3GHSA-wfqx-gjrf-g28r
Gogithub.com/crossplane/crossplane/v22.2.3GHSA-wfqx-gjrf-g28r
Gogithub.com/crossplane/crossplane/v2kein Fix bekanntGO-2026-5709

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 · ohne 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.