ServiceAccount token disclosure via rendered CNI logs
Published May 28, 2026 · Updated May 28, 2026
Information disclosure in Tigera Calico before 3.31.6 allows remote authenticated users to read a ServiceAccount token from pod logs. The install-cni init container replaces SERVICEACCOUNT_TOKEN in Canal or Flannel-Calico CNI templates with a live bearer token, then writes the fully rendered configuration to standard output. Access requires pods/log permission in the calico-node namespace; the exposed token can patch pods/status cluster-wide, while kubeconfig-based deployments are unaffected.
Summary
What happened
Information disclosure in Tigera Calico before 3.31.6 allows remote authenticated users to read a ServiceAccount token from pod logs. The install-cni init container replaces SERVICEACCOUNT_TOKEN in Canal or Flannel-Calico CNI templates with a live bearer token, then writes the fully rendered configuration to standard output. Access requires pods/log permission in the calico-node namespace; the exposed token can patch pods/status cluster-wide, while kubeconfig-based deployments are unaffected.
The record
- CVE
- CVE-2026-41184
- Published
- May 28, 2026
- Updated
- May 28, 2026
- Vendor
- Tigera
- Product
- Calico
- Classifications
- CWE-200, CWE-532, CAPEC-150, T1552.001
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- May 28, 2026CVE publishedPublication date reported by the CVE source.
- May 28, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0 <3.31.6
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo