How severe is GHSA-m67g-87rx-v42c?

GHSA-m67g-87rx-v42c has a CVSS score of 6.5/10, rated MEDIUM. Review your exposure and patch according to your risk tolerance.

Which packages are affected by GHSA-m67g-87rx-v42c?

GHSA-m67g-87rx-v42c affects the following packages: github.com/projectcalico/calico (Go), github.com/projectcalico/calico (Go). Ecosystems affected: Go.

How do I fix GHSA-m67g-87rx-v42c?

Update github.com/projectcalico/calico to 3.31.6 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-m67g-87rx-v42c is resolved across your whole dependency graph.

How do I detect GHSA-m67g-87rx-v42c in my Go dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/projectcalico/calico. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

How do I mitigate GHSA-m67g-87rx-v42c 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.

How does O3 Security protect against GHSA-m67g-87rx-v42c?

O3 pinpoints whether GHSA-m67g-87rx-v42c is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Is GHSA-m67g-87rx-v42c actively exploited in the wild?

No public exploit code has been indexed for GHSA-m67g-87rx-v42c 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-m67g-87rx-v42c?

GHSA-m67g-87rx-v42c has an EPSS (Exploit Prediction Scoring System) score of 0.3%, placing it in the 24th 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-m67g-87rx-v42c?

GHSA-m67g-87rx-v42c is classified as CWE-532 (CWE-532). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was GHSA-m67g-87rx-v42c published, and has it been updated?

GHSA-m67g-87rx-v42c was published on May 28, 2026 and was last updated on July 7, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

GHSA-m67g-87rx-v42c: Calico Inserts Sensitive Information into…

EPSS Exploitation Probability

via FIRST.org ↗

0.3%probability of exploitation in next 30 days

Lower Risk24th percentile0.00%

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.

Blast Radius

2 pkgs affected

🐹github.com/projectcalico/calico🐹github.com/projectcalico/calico

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

When Calico is configured with the Azure IPAM plugin, the Calico CNI binary mutates the incoming CNI configuration to attach subnet information before delegating to the IPAM plugin. After mutating, the Azure IPAM helper logs the entire unmarshaled configuration map (stdinData) at INFO level to /var/log/calico/cni/cni.log on every CNI ADD and DEL invocation — once per pod scheduled or terminated on the node. When the cluster is deployed using token-based Kubernetes authentication, this log entry contains the ServiceAccount token, client key, and certificate authority in plaintext. Any principal with read access to /var/log/calico/cni/cni.log on a node can read these logs and extract the credentials, which grant cluster-wide Calico networking admin privileges.

Affected Packages

2 total 2 fixed

Ecosystem	Package	Vulnerable range	Fix
🐹Go	`github.com/projectcalico/calico`	≥ 2.0.0&&< 3.31.6	3.31.6
🐹Go	`github.com/projectcalico/calico`	all versions	1.11.0-cni-plugin.0.20260417001138-cd73bc2cea0f

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/projectcalico/calico. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
Update github.com/projectcalico/calico to 3.31.6 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-m67g-87rx-v42c 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 pinpoints whether GHSA-m67g-87rx-v42c is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to GHSA-m67g-87rx-v42c. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

When Calico is configured with the Azure IPAM plugin, the Calico CNI binary mutates the incoming CNI configuration to attach subnet information before delegating to the IPAM plugin. After mutating, the Azure IPAM helper logs the entire unmarshaled configuration map (stdinData) at INFO level to /var/log/calico/cni/cni.log on every CNI ADD and DEL invocation — once per pod scheduled or terminated on the node. When the cluster is deployed using token-based Kubernetes authentication, this log entry contains the ServiceAccount token, client key, and certificate authority in plaintext. Any principal

O3 Security · Impact-Aware SCA

Is GHSA-m67g-87rx-v42c in your dependencies?

O3 detects GHSA-m67g-87rx-v42c across Go dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

Scan my dependencies How O3 SCA works

GHSA-m67g-87rx-v42c