Skip to content
Fencer Intel
critical 9.0

GHSA-wfqx-gjrf-g28r json

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

published 4mo ago modified last mo. also GO-2026-5709

cvss
9.0
version 3.1, GitHub
cisa kev
Not listed
not in CISA's catalog
epss
—
no score, EPSS covers CVEs only
public exploits
0
none known

Summary

## 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.

Patch / fix

  • go github.com/crossplane/crossplane/v2 2.2.3, 2.3.3

Is GHSA-wfqx-gjrf-g28r in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

CVSS scores

assigned by version score vector
GitHub 3.1 9.0 CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:H/I:H/A:H

Affected packages

ecosystem package affected fixed in
go github.com/crossplane/crossplane/v2
>=2.3.0-rc.0, <2.3.3
<2.2.3
>=2.3.0-rc.0
2.3.3
2.2.3
go github.com/crossplane/crossplane
<=1.21.0-rc.0
all versions
no fix listed

Classification

Weakness
  • CWE-345 Insufficient Verification of Data Authenticity
  • CWE-367 Time-of-check Time-of-use (TOCTOU) Race Condition

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.