Exposure of Sensitive Information to an Unauthorized Actor and Insertion of Sensitive Information Into Sent Data in CalicoGHSA-pf59-j7c2-rh6x
MEDIUMFix: containernetworking/plugins#484GHSA-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.
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
Where this sits among everything scored
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 |
Affected Products
calicoprojectcalicoDetection & 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
Assume what was exposed is already known: rotate any credential, token or key that the affected component could return, restrict the endpoint to callers that genuinely need it, and strip sensitive fields from responses and error output at the boundary rather than relying on the client not to read them.
Frequently Asked Questions
Is GHSA-pf59-j7c2-rh6x in your dependencies?
Find it across Go, including transitive dependencies.