Free and open · new CVEs checked every 20 minutesStatusRSSOpen dataContact

CVE-2026-41186: When Calico's shared debug server is enabled (disabled by default), the Calico kube-controllers and Goldmane c

44
This month
HIGH 7.5REMOTEUPGRADE

CVE-2026-41186 is a high-severity flaw (CVSS 7.5) affecting calico. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

When Calico's shared debug server is enabled (disabled by default), the Calico kube-controllers and Goldmane components bind their Go pprof debug listener to 0.0.0.0 without authentication. Any pod with network reachability to the listener can retrieve the process heap, goroutine stacks (including function arguments), and command-line arguments. Depending on the process's in-memory state, the heap may contain sensitive material. The debug listene

Why this priority

  • High severity
  • Remotely exploitable, no login, no user action

A fixed release or distro patch exists.

Risk facts

CVSS score7.5 (High)
Attack vectorNetwork (remote)
Attack complexityLow
Privileges neededNone
User interactionNone
EPSS exploit chance0.7% (top 48%)
CISA exploited listNo
WeaknessCWE-200, CWE-489
Published2026-07-30
Last modified2026-08-08
Publisher (CNA): Tigera, Inc. · Vendor: tigera

Share: LinkedIn · X · Reddit

Last updated 2026-08-08 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

tigera calico UPGRADE
Affected: < 3.21.7 · < 3.31.6 · <= 22.4.0 · >= 3.22.0 and < 3.22.4 · >= 3.32.0 and < 3.32.1
Fixed in: 3.21.7, 3.22.4, 3.31.6, 3.32.1
Safe to downgrade to: a release before 3.22.0
1. Check installed version
apt-cache policy calico || rpm -q calico || calico --version
2. UPGRADE to 3.21.7 (Debian / Ubuntu)
sudo apt update && sudo apt install --only-upgrade calico
2. UPGRADE (RHEL / Amazon Linux / Fedora)
sudo dnf upgrade calico
Note
Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.
3. If no update is available yet, DOWNGRADE to a release before 3.22.0 (Debian / Ubuntu)
apt-cache madison calico sudo apt install calico=<VERSION_BEFORE_3.22.0> sudo apt-mark hold calico
3. If no update is available yet, DOWNGRADE (RHEL / Amazon Linux / Fedora)
dnf --showduplicates list calico sudo dnf downgrade calico-<VERSION_BEFORE_3.22.0> sudo dnf versionlock add calico
Downgrade risk
Downgrading can break dependent software and may reopen older bugs. Read the distro advisory first and test on a non-production host.
After downgrade
Restart the service, and keep the package held until a fixed release ships.
Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2026-41186?

calico: upgrade to 3.21.7, 3.22.4, 3.31.6, 3.32.1. Exact commands for each OS are on this page.

Is CVE-2026-41186 being exploited?

CVE-2026-41186 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2026-41186 affect?

CVE-2026-41186 affects calico. Severity is high (CVSS 7.5). When Calico's shared debug server is enabled (disabled by default), the Calico kube-controllers and Goldmane components bind their Go pprof debug listener to 0.0.0.0 without authentication. Any pod with network reachability to the listener

How urgent is CVE-2026-41186?

Priority 44/100. High severity; Remotely exploitable, no login, no user action

Related CVEs

References

← Back to latest CVEs

Get the weekly exploited-CVE digest by emailThe CVEs being attacked this week and how to fix them. No spam, unsubscribe any time.