Approved changes feed: RSS · Atom
cpe:2.3:a:tigera:calico:3.32.0:*:*:*:*:*:*:*
part: a version: 3.32.0 update: *
| Vendor | Tigera (651f039a-f41c-57e4-b4a9-d5d438e9d3c1) |
|---|---|
| Product | Calico (a7143295-6c02-59c2-ad22-1fcb5b68e0ee) |
| Edition | * |
| Language | * |
| Software edition | * |
| Target software | * |
| Target hardware | * |
| Other | * |
| Notes | Imported from gcve-enriched-dumps CVE data |
PURL mappings
| PURL | Source | Last updated |
|---|---|---|
| No PURL mappings for this CPE yet. | ||
Vulnerability references
| Identifier | cpeApplicability | Submitted | db.gcve.eu details | Rationale |
|---|---|---|---|---|
CVE:CVE-2026-41184 |
not_vulnerable | 2026-06-08 08:03:15.039275 |
ServiceAccount token disclosure via install-cni container logs
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.
Published: 2026-05-28T15:47:42.173Z
Updated: 2026-05-28T17:04:36.059Z |
Imported from gcve-enriched-dumps CVE data |
Contribute
You can submit an edit proposal for this CPE entry or suggest a related product/vendor addition using the action button above.