How severe is GHSA-mf7q-r4rv-jv94?

No CVSS score has been assigned to GHSA-mf7q-r4rv-jv94 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-mf7q-r4rv-jv94?

GHSA-mf7q-r4rv-jv94 affects the following packages: github.com/crossplane/crossplane-runtime/v2 (Go), github.com/crossplane/crossplane-runtime/v2 (Go). Ecosystems affected: Go.

How do I fix GHSA-mf7q-r4rv-jv94?

Update github.com/crossplane/crossplane-runtime/v2 to 2.4.0-rc.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-mf7q-r4rv-jv94 is resolved across your whole dependency graph.

How do I detect GHSA-mf7q-r4rv-jv94 in my Go dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/crossplane/crossplane-runtime/v2, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate GHSA-mf7q-r4rv-jv94 if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Is GHSA-mf7q-r4rv-jv94 actively exploited in the wild?

No public exploit code has been indexed for GHSA-mf7q-r4rv-jv94 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for GHSA-mf7q-r4rv-jv94?

GHSA-mf7q-r4rv-jv94 has an EPSS (Exploit Prediction Scoring System) score of 0.3%, placing it in the 23th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is GHSA-mf7q-r4rv-jv94?

GHSA-mf7q-r4rv-jv94 is classified as CWE-362 (CWE-362), CWE-367 (CWE-367). These weakness types describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was GHSA-mf7q-r4rv-jv94 published, and has it been updated?

GHSA-mf7q-r4rv-jv94 was published on August 27, 2026 and was last updated on October 5, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐹 Go

Not in CISA KEV

Crossplane's TOCTOU between cosign verification and image fetch in xpkg.CachedClient allows tag-based package install to bypass signature checkGHSA-mf7q-r4rv-jv94

GHSA-mf7q-r4rv-jv94 is a CWE-362 vulnerability in github.com/crossplane/crossplane-runtime/v2. A fix is available for github.com/crossplane/crossplane-runtime/v2 — see the affected versions and patch details below.

Also known asCVE-2026-105163GO-2026-6302

Published

Aug 27, 2026

Updated

Oct 5, 2026

Affected

2 pkgs

Patched

2 / 2

Exploits

None indexed

Exploitation data as of Oct 11, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

No confirmed exploitation observed yet

CISA assesses this as automatable — exploitation doesn’t require manual, per-target effort, which raises the odds of mass scanning and opportunistic attacks.
CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for GHSA-mf7q-r4rv-jv94.

EPSS Exploitation Probability

via FIRST.org ↗

0.3%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs23th percentile — riskier than 23% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

Real-World Exposure

2 pkgs affected

🐹github.com/crossplane/crossplane-runtime/v2🐹github.com/crossplane/crossplane-runtime/v2

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Go packages — download data is not available via public APIs for these ecosystems.

Description

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:

Configure signature verification for packages,
Install packages using tag references rather than digests, and
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.

Credits

This issue was reported, independently, by @bugbunny-research and @tonghuaroot.

Affected Packages

2 total 2 fixed

Ecosystem	Package	Vulnerable range	Fix
🐹Go	`github.com/crossplane/crossplane-runtime/v2`	≥ 2.4.0-rc.0&&< 2.4.0-rc.1	2.4.0-rc.1`go get github.com/crossplane/crossplane-runtime/v2@v2.4.0-rc.1`
🐹Go	`github.com/crossplane/crossplane-runtime/v2`	≥ 2.3.0&&< 2.3.3	2.3.3`go get github.com/crossplane/crossplane-runtime/v2@v2.3.3`

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/crossplane/crossplane-runtime/v2, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update github.com/crossplane/crossplane-runtime/v2 to 2.4.0-rc.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-mf7q-r4rv-jv94 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Frequently Asked Questions

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

O3 Security · Impact-Aware SCA

Is GHSA-mf7q-r4rv-jv94 in your dependencies?

Find it across Go, including transitive dependencies.

Scan my dependencies How O3 SCA works