# CVE-2026-41185: ServiceAccount token disclosure via Azure IPAM CNI plugin logs

> Attackers with node log access can steal ServiceAccount tokens from Calico Azure IPAM logs, enabling cluster-wide privilege escalation.

- **Severity:** Medium 6.0 (`CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:H/VI:N/VA:N/SC:L/SI:L/SA:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 28 May 2026
- **Updated:** 28 May 2026
- **Also known as:** GHSA-m67g-87rx-v42c, GO-2026-5891, MINI-8mmx-x2c5-p8qv, MINI-cw38-3x25-p6qx, MINI-fhv4-88xw-vj9h, MINI-fv9p-j2c4-vwv2, MINI-h3j8-xfj4-xfwx, MINI-p3f5-h3cw-rh3x

## What is CVE-2026-41185?

CVE-2026-41185 is a medium-severity vulnerability in Tigera Calico, published on 28 May 2026. Any signed-in user can exploit it over the network, with no action from the victim.

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

Weakness: CWE-532 (Insertion of Sensitive Information into Log File)

## Which versions are affected by CVE-2026-41185?

6 open source packages ship an affected version, including github.com/projectcalico/calico and github.com/projectcalico/calico/v3. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `github.com/projectcalico/calico` | Go | All versions | 1.11.0-cni-plugin.0.20260417001138-cd73bc2cea0f |
| `github.com/projectcalico/calico` | Go | All versions | 1.11.0-cni-plugin.0.20260417001138-cd73bc2cea0f |
| `github.com/projectcalico/calico` | Go | All versions | 1.11.0-cni-plugin.0.20260417001138-cd73bc2cea0f |
| `github.com/projectcalico/calico` | Go | From 2.0.0 | 3.31.6 |
| `github.com/projectcalico/calico` | Go | From 2.0.0 | 3.31.6 |
| `github.com/projectcalico/calico/v3` | Go | All versions | None |

Products: Tigera Calico.

## How do I fix CVE-2026-41185?

Upgrade github.com/projectcalico/calico to a fixed version for your release line: 1.11.0-cni-plugin.0.20260417001138-cd73bc2cea0f or 3.31.6.

## Is CVE-2026-41185 being exploited?

There is no known exploitation of CVE-2026-41185 in the wild and no public exploit code.

## Other vulnerabilities in Tigera Calico

- [CVE-2026-6540](https://insights.sbomify.com/CVE-2026-6540/): L7 policy bypass via unnormalized HTTP path matching (high 7.9)
- [CVE-2026-41187](https://insights.sbomify.com/CVE-2026-41187/): Calico Tier Authorization Bypass via DeleteCollection (medium 6.2)
- [CVE-2026-41186](https://insights.sbomify.com/CVE-2026-41186/): Unauthenticated Go pprof exposure in Calico debug server (medium 6.0)
- [CVE-2026-41184](https://insights.sbomify.com/CVE-2026-41184/): ServiceAccount token disclosure via install-cni container logs (medium 6.0)
- [CVE-2022-28224](https://insights.sbomify.com/CVE-2022-28224/): Calico and Calico Enterprise may be vulnerable to route hijacking with the floating IP feature (medium 5.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-41185 and fix it if it is affected.

What it is: CVE-2026-41185 is a medium-severity vulnerability in Tigera Calico, published on 28 May 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-41185 in the wild and no public exploit code.

Affected packages and fixed versions:
- github.com/projectcalico/calico (Go): affected all versions; fixed in 1.11.0-cni-plugin.0.20260417001138-cd73bc2cea0f
- github.com/projectcalico/calico (Go): affected all versions; fixed in 1.11.0-cni-plugin.0.20260417001138-cd73bc2cea0f
- github.com/projectcalico/calico (Go): affected all versions; fixed in 1.11.0-cni-plugin.0.20260417001138-cd73bc2cea0f
- github.com/projectcalico/calico (Go): affected from 2.0.0; fixed in 3.31.6
- github.com/projectcalico/calico (Go): affected from 2.0.0; fixed in 3.31.6
- github.com/projectcalico/calico/v3 (Go): affected all versions; no fix listed

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-41185/ (Markdown: https://insights.sbomify.com/CVE-2026-41185/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-41185
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-41185
- OSV: https://osv.dev/vulnerability/CVE-2026-41185

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-41185/
Summaries are generated and may contain mistakes; the official description above is the record.