{"items":[{"id":"NVI-00017657","kind":"vulnerability","title":"Calico Inserts Sensitive Information into Log File","revision":1,"unknowns":["Customer inventory, deployment, reachability and exploitation have not been inspected."],"lifecycle":"active","identifiers":["GHSA-3m4q-ggcj-j6m4","CVE-2026-6720"],"plain_summary":"GitHub lists this reviewed advisory for github.com/projectcalico/calicoctl/v3. Published version ranges and source prerequisites are shown below; this is not an inspection of a visitor’s application.","review_status":"source_listed","control_topics":[],"public_actions":[{"summary":"Identify the exact component and deployed version, examine the linked publisher’s conditions, and retain evidence of any mitigation.","source_ids":["sr-3c3d27b37b7a7bb9c07e39086940f75f"],"action_type":"investigate","limitations":"Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system.","current_supported_target":null}],"schema_version":"1.1.0","source_metrics":[],"why_it_matters":"Published affected context helps an owner decide what evidence to gather. This report has not examined your application.","related_sources":[{"id":"sr-3c3d27b37b7a7bb9c07e39086940f75f","url":"https://github.com/advisories/GHSA-3m4q-ggcj-j6m4","basis":"vendor_advisory","notes":"GitHub Advisory Database; CC-BY-4.0. Each advisory links its original attribution. Null normalizes fields.","title":"GHSA-3m4q-ggcj-j6m4","publisher":"GitHub Advisory Database","observed_at":"2026-11-05T03:47:42.887Z"}],"affected_context":[{"certainty":"source_listed","source_ids":["sr-3c3d27b37b7a7bb9c07e39086940f75f"],"technology":"github.com/projectcalico/calicoctl/v3","known_exclusions":[],"conditions_summary":"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.","public_affected_ranges":["< 3.31.6"]}],"null_published_at":"2026-11-05T19:10:21.447Z","source_updated_at":"2026-07-02T18:08:05.000Z","source_disclosed_at":"2026-05-28T18:30:32.000Z","is_synthetic_fixture":false,"null_last_reviewed_at":null,"public_change_summary":"First indexed by Null; source disclosure date is shown separately.","null_first_observed_at":"2026-11-05T03:47:42.887Z"}],"next_cursor":null,"snapshot_revision":"42594"}