github.com/crossplane/crossplane/v2
Affected
- introduced
2.3.0-rc.0, fixed2.3.3(semver)
Fixed versions
2.3.3
Fix
- Fixed version
2.3.3go get github.com/crossplane/crossplane/[email protected]
Advisory
Also known as: GO-2026-5709
Crossplane: Signature verification TOCTOU allows installing unverified package content via mutable tag
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:
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:
Credits
This issue was reported, independently, by @bugbunny-research and @tonghuaroot.
Critical Basis: The source's own band: CRITICAL
2.3.0-rc.0, fixed 2.3.3 (semver)2.3.3
2.3.3go get github.com/crossplane/crossplane/[email protected]0, fixed 2.2.3 (semver)2.2.3
2.2.3go get github.com/crossplane/crossplane/[email protected]0, last affected 1.21.0-rc.0 (semver)None listed
No fixed version is listed.
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