How severe is CVE-2026-41185?

No CVSS score has been assigned to CVE-2026-41185 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by CVE-2026-41185?

CVE-2026-41185 affects the following packages: github.com/projectcalico/calico (Go), github.com/projectcalico/calico (Go). Ecosystems affected: Go.

How do I fix CVE-2026-41185?

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 CVE-2026-41185 is resolved across your whole dependency graph.

How do I detect CVE-2026-41185 in my Go dependencies?

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.

How do I mitigate CVE-2026-41185 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 CVE-2026-41185 actively exploited in the wild?

No public exploit code has been indexed for CVE-2026-41185 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 CVE-2026-41185?

CVE-2026-41185 has an EPSS (Exploit Prediction Scoring System) score of 0.3%, placing it in the 25th 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 CVE-2026-41185?

CVE-2026-41185 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 CVE-2026-41185 published, and has it been updated?

CVE-2026-41185 was published on May 28, 2026 and was last updated on August 12, 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

CVE-2026-41185 — calico

Fix: projectcalico/calico#12502

CVE-2026-41185 is a CWE-532 vulnerability in github.com/projectcalico/calico. A fix is available for github.com/projectcalico/calico — see the affected versions and patch details below.

ServiceAccount token disclosure via Azure IPAM CNI plugin logs

Also known asGHSA-m67g-87rx-v42cGO-2026-5891

Published

May 28, 2026

Updated

Aug 12, 2026

Affected

2 pkgs

Patched

2 / 2

Exploits

None indexed

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

Exploitation Status

No confirmed exploitation observed yet

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 CVE-2026-41185.

EPSS Exploitation Probability

via FIRST.org ↗

0.3%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs25th percentile — riskier than 25% 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/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 get github.com/projectcalico/calico@v3.31.6`
🐹Go	`github.com/projectcalico/calico`	all versions	1.11.0-cni-plugin.0.20260417001138-cd73bc2cea0f`go get github.com/projectcalico/calico@v1.11.0-cni-plugin.0.20260417001138-cd73bc2cea0f`

Affected Products

1 product · 4 configurations

Application

calicotigera

≥ 3.22.0 && < 3.22.3

range

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, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
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 CVE-2026-41185 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.