Is there a patch available for CVE-2026-41186?

Yes, a patch is available for CVE-2026-41186. Update the affected software to the latest version immediately.

Tigera Calico CVE-2026-41186

Q: What is the CVSS score of CVE-2026-41186?

CVE-2026-41186 has a CVSS 4.0 base score of 6.0 (Medium). CVSS vector: CVSS:4.0/AV:A/AC:L/AT:P/PR:N/UI:N/VC:H/VI:N/VA:N/SC:L/SI:L/SA:L/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X. EPSS exploitation probability: 0.2%.

EUVD-2026-51155 MEDIUM

Active Debug Code (CWE-489)

2026-07-30 Tigera

GHSA-h3h4-j2qv-pv4j

Information Disclosure Calico Calico Enterprise Calico Cloud

6.0

CVSS 4.0 · Vendor: Tigera

Severity by source

Vendor (Tigera) PRIMARY

6.0 MEDIUM

CVSS:4.0/AV:A/AC:L/AT:P/PR:N/UI:N/VC:H/VI:N/VA:N/SC:L/SI:L/SA:L/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

vuln.today AI

5.3 MEDIUM

Adjacent vector for cluster-internal pod access; AC:H because debug server must be explicitly enabled by operator; PR:N since the endpoint itself is entirely unauthenticated once reachable.

3.1 AV:A/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N

4.0 AV:A/AC:L/AT:P/PR:N/UI:N/VC:H/VI:N/VA:N/SC:L/SI:L/SA:L

Primary rating from Vendor (Tigera).

CVSS VectorVendor: Tigera

Attack Vector

Adjacent

Attack Complexity

Low

Privileges Required

None

User Interaction

None

Scope

Lifecycle Timeline

Source Code Evidence Fetched

Jul 30, 2026 - 15:35 vuln.today

Analysis Generated

Jul 30, 2026 - 15:35 vuln.today

CVE Published

Jul 30, 2026 - 14:45 cve.org

MEDIUM 6.0

DescriptionCVE.org

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 listener is opt-in but is unsafe when enabled because it offers no authentication and no safe localhost-only binding option.

AnalysisAI

Unauthenticated exposure of Go pprof debug endpoints in Calico kube-controllers and Goldmane components allows any pod with adjacent network access to retrieve sensitive in-memory data when the shared debug server feature is enabled. Affected products span Calico, Calico Enterprise, and Calico Cloud across all versions per CPE. The vulnerability is opt-in (debug server disabled by default), but carries high confidentiality impact when enabled because heap dumps and goroutine stacks may contain credentials, tokens, or other sensitive runtime state. No public exploit identified at time of analysis and no CISA KEV listing.

Technical ContextAI

Calico is a widely deployed Kubernetes CNI networking and security plugin. The affected components - kube-controllers and Goldmane - optionally expose a Go pprof (performance profiling) HTTP debug server used for heap, goroutine, and CPU profiling. The root cause is CWE-489 (Active Debug Code): when the feature is enabled, the listener binds to 0.0.0.0 on the configured port rather than to localhost, making it reachable from any pod in the cluster without authentication. The fix confirmed in PR #12491 and #12633/#12634 changes the bind address to 'localhost', requiring kubectl port-forward for legitimate remote access. Affected CPEs are cpe:2.3:a:tigera:calico:*, cpe:2.3:a:tigera:calico_enterprise:*, and cpe:2.3:a:tigera:calico_cloud:*.

RemediationAI

The primary fix is to upgrade to patched releases of Calico, Calico Enterprise, or Calico Cloud once published - exact patched version numbers are not independently confirmed from the available data, so refer to the Tigera advisory at https://www.tigera.io/security-bulletins/tta-2026-004/ for the specific target release. If upgrade is not immediately possible, the most effective compensating control is to disable the shared debug server feature entirely - since it is opt-in and disabled by default, any cluster that has not explicitly enabled it is already unexposed. If the debug server must remain enabled for operational reasons, apply Kubernetes NetworkPolicy to restrict access to the pprof port to trusted operator pods or namespaces only; note that NetworkPolicy enforcement depends on the CNI being functional, so a backup approach is to configure a host-level firewall or iptables rule blocking the debug port from general pod CIDR ranges. The upstream code change (PRs #12491/#12633/#12634) rebinds the listener to localhost, so patched versions require kubectl port-forward for any remote pprof access - a trade-off of operational convenience for security.