GHSA-pf59-j7c2-rh6x is a medium-severity (CVSS 6) CWE-201 vulnerability in github.com/projectcalico/calico. A fix is available for github.com/projectcalico/calico — see the affected versions and patch details below.
Exposure of Sensitive Information to an Unauthorized Actor and Insertion of Sensitive Information Into Sent Data in Calico
EPSS Exploitation Probability
EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.
How urgent is this, really
GHSA-pf59-j7c2-rh6x plotted by exploitation likelihood (EPSS) against impact (CVSS). The shaded corner — EPSS 50%+ and CVSS 7.0+ — is where this CVE doesn't sit, though severity or exploitability alone can still warrant action.
Where this sits among everything scored
Of 379,145 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Real counts from FIRST.org, not a sample — log-scaled since the landscape is heavily right-skewed.
Real-World Exposure
github.com/projectcalico/calico🐹github.com/projectcalico/calico🐹github.com/projectcalico/calico🐹github.com/projectcalico/calico🐹github.com/projectcalico/calico🐹github.com/projectcalico/calico🐹github.com/projectcalico/calicoReal-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
Clusters using Calico (version 3.14.0 and below), Calico Enterprise (version 2.8.2 and below), may be vulnerable to information disclosure if IPv6 is enabled but unused. A compromised pod with sufficient privilege is able to reconfigure the node’s IPv6 interface due to the node accepting route advertisement by default, allowing the attacker to redirect full or partial network traffic from the node to the compromised pod.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐹Go | github.com/projectcalico/calico | ≥ 3.14.0&&< 3.14.1 | 3.14.1go get github.com/projectcalico/calico@v3.14.1 |
| 🐹Go | github.com/projectcalico/calico | ≥ 3.13.0&&< 3.13.4 | 3.13.4go get github.com/projectcalico/calico@v3.13.4 |
| 🐹Go | github.com/projectcalico/calico | ≥ 3.12.0&&< 3.12.2 | 3.12.2go get github.com/projectcalico/calico@v3.12.2 |
| 🐹Go | github.com/projectcalico/calico | ≥ 3.11.0&&< 3.11.3 | 3.11.3go get github.com/projectcalico/calico@v3.11.3 |
| 🐹Go | github.com/projectcalico/calico | ≥ 3.10.0&&< 3.10.4 | 3.10.4go get github.com/projectcalico/calico@v3.10.4 |
| 🐹Go | github.com/projectcalico/calico | ≥ 3.9.0&&< 3.9.6 | 3.9.6go get github.com/projectcalico/calico@v3.9.6 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/projectcalico/calico, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update github.com/projectcalico/calico to 3.14.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-pf59-j7c2-rh6x 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.
How O3 protects you
O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-pf59-j7c2-rh6x can be triaged on real exposure rather than presence alone.
Tailored to GHSA-pf59-j7c2-rh6x. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is GHSA-pf59-j7c2-rh6x in your dependencies?
O3 Security finds GHSA-pf59-j7c2-rh6x across Go dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.