In Calico, the install-cni init container logs the rendered CNI configuration to standard output. When the configuration template uses the SERVICEACCOUNT_TOKEN placeholder (Canal/Flannel-Calico deployments), the installer substitutes the live Kubernetes ServiceAccount bearer token before logging, exposing 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. The default kubeconfig-based authentication path is not affected. This is a direct regression of TTA-2018-001.
{
"osv_generated_from": "https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/41xxx/CVE-2026-41184.json",
"cwe_ids": [
"CWE-532"
],
"cna_assigner": "Tigera"
}{
"source": "CPE_RANGE",
"cpe": [
"cpe:2.3:a:tigera:calico:*:*:*:*:open_source:*:*:*",
"cpe:2.3:a:tigera:calico:*:*:*:*:enterprise:*:*:*"
],
"extracted_events": [
{
"introduced": "0"
},
{
"fixed": "3.32.0"
},
{
"introduced": "3.22.0"
},
{
"fixed": "3.22.3"
}
]
}