Calico Enterprise
Approved changes feed: RSS · Atom
cpe:2.3:a:tigera:calico_enterprise:3.22.3:*:*:*:*:*:*:*
part: a version: 3.22.3 update: *
| Vendor | Tigera (651f039a-f41c-57e4-b4a9-d5d438e9d3c1) |
|---|---|
| Product | Calico Enterprise (e2076448-6a97-524d-bb5f-21f88bd15574) |
| 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-6720 |
not_vulnerable | 2026-06-08 08:07:05.012406 |
Calicoctl leaks cluster credentials to stderr when verbose logging is enabled
When calicoctl is invoked with --log-level=info or --log-level=debug, the client prints the full contents of its loaded connection-configuration struct to stderr in a single log line. The struct embeds every credential calicoctl uses to talk to the cluster — inline kubeconfig (with bearer token), Kubernetes API bearer token, etcd password, and inline PEM-encoded etcd client certificate and key. Any reader of that stderr stream — CI job logs, session-recording archives, shared support-ticket transcripts, or local filesystem viewers on the host that ran calicoctl — can extract these credentials with zero Kubernetes privilege. calicoctl's default log level is panic, so this issue only triggers when verbose logging is explicitly enabled.
Published: 2026-05-28T15:47:42.519Z
Updated: 2026-05-28T17:04:11.659Z |
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.