CVE-2026-41184: Calico Exposes Kubernetes ServiceAccount Token in Logs
Summary
CVE-2026-41184: Calico Inserts Sensitive Information into Log File. Affects github.com/projectcalico/calico across 2 version ranges.
< 1.11.0-cni-plugin.0.20260417001138-cd73bc2cea0f
>= 2.0.0, < 3.31.6
Fixed in 1.11.0-cni-plugin.0.20260417001138-cd73bc2cea0f or 3.31.6, depending on the release line you run. How to fix ↓
Check if this vulnerability affects your application
Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.
No signup required · Results in about 60 seconds
Background
Calico is an open-source networking and network security solution for containers, virtual machines, and native host-based workloads. It provides a highly scalable and efficient way to manage networking in Kubernetes environments. The package is widely used for its ability to enforce network policies and provide connectivity between workloads. However, it has a vulnerability that can expose sensitive information, specifically Kubernetes ServiceAccount tokens, through its logging mechanism.
Vulnerability Detail
In Calico, the install-cni init container logs the rendered CNI configuration to standard output. When the configuration template uses the SERVICEACCOUNT_TOKEN placeholder, the installer substitutes the live Kubernetes ServiceAccount bearer token before logging. This exposes the token to any authenticated user with pods/log permission in the namespace with calico-node. The token holds patch privileges on pods/status, enabling annotation-based attacks against cluster workloads. This vulnerability is a direct regression of TTA-2018-001 and poses a significant risk to the security of Kubernetes clusters.
How To Fix
Latest published version: v3.21.1+incompatible as of 23 Oct 2026
go get github.com/projectcalico/calico@v3.21.1+incompatible
Upgrading to it may include breaking changes; the versions below are the minimum fixed release for this vulnerability.
If you can't move to the latest
The minimum fixed version depends on the release line you run.
-
< 1.11.0-cni-plugin.0.20260417001138-cd73bc2cea0f1.11.0-cni-plugin.0.20260417001138-cd73bc2cea0fgo get github.com/projectcalico/calico@v1.11.0-cni-plugin.0.20260417001138-cd73bc2cea0f -
>= 2.0.0, < 3.31.63.31.6go get github.com/projectcalico/calico@v3.31.6
Tip — Not sure which release line you're on? Vulert can find the fix for the version you are using. Scan free →
Workaround
As a temporary workaround, you can modify the logging configuration to avoid logging sensitive information. This may involve changing the logging level or redirecting logs to a secure location where they cannot be accessed by unauthorized users.
Conclusion
CVE-2026-41184 is a significant vulnerability in Calico that exposes sensitive Kubernetes ServiceAccount tokens through logging. It is crucial for users to update to the patched versions to mitigate the risks associated with this vulnerability. Additionally, employing workarounds can help secure your environment until the update is applied.
See every vulnerability recorded for github.com/projectcalico/calico →
FAQ
CVE-2026-41184 is a vulnerability in Calico that exposes Kubernetes ServiceAccount tokens in logs, potentially allowing unauthorized access to sensitive cluster information.
This vulnerability allows authenticated users with log access to view sensitive ServiceAccount tokens, which can be exploited to gain elevated privileges within the cluster.
Versions of Calico from 2.0.0 to 3.31.5 and from 0 to 1.11.0-cni-plugin.0.20260417001138-cd73bc2cea0f are affected by this vulnerability.
You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. You can check your application against this vulnerability using the Vulert playground without any signup.
The CVSS score of this vulnerability is 6.5, indicating a moderate level of severity.
References
Related vulnerabilities
Recent vulnerabilities recorded for github.com/projectcalico/calico.