Skip to content
Patch Next
Sign inAdd to your agent

← Public intelligence

Go package

github.com/projectcalico/calicoctl/v3

Open actionable advisories and recorded vendor fixes. This public package view has no inventory attached and cannot establish whether your deployment is affected. A vendor fix never resolves your finding; verify your installed version and the source guidance.

Open advisories

1 actionable advisory, newest first. Withdrawn advisories and news are excluded. Coverage is partial.

  1. High, CVSS 7.2GoPublished

    Calico Inserts Sensitive Information into Log File

    CVE-2026-6720 · GHSA-3m4q-ggcj-j6m4

    Affected
    • Go github.com/projectcalico/calicoctl/v3 < 3.31.6
    Fixed in
    3.31.6· Vendor fix available
    Issue
    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.

    Recommended action: Upgrade to 3.31.6 or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.

    Sources:github.comSource checked Evidence →