CVE-2026-41186: CWE-489 Active Debug Code in Tigera Calico
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.
AI Analysis
Technical Summary
This vulnerability arises from Calico's shared debug server binding its Go pprof debug listener to all network interfaces (0.0.0.0) without any authentication when enabled. This exposes internal runtime information including process heap memory, goroutine stacks with function arguments, and command-line arguments to any pod that can reach the listener over the network. The heap may contain sensitive data depending on the process's memory state. The debug server is opt-in and disabled by default, but if enabled, it is unsafe due to lack of authentication and no option to restrict binding to localhost only.
Potential Impact
An attacker with network access to the debug listener can obtain detailed runtime information from the Calico components, potentially exposing sensitive in-memory data. This can lead to information disclosure that may aid further attacks or compromise confidentiality. The vulnerability does not allow direct code execution or privilege escalation but exposes sensitive internal state.
Mitigation Recommendations
Since the debug listener is disabled by default, the primary mitigation is to avoid enabling the shared debug server unless absolutely necessary. If enabled, restrict network access to the debug listener to trusted pods only via network policies or firewall rules. There is no official fix or patch currently available; monitor the vendor advisory for updates. Patch status is not yet confirmed — check the vendor advisory for current remediation guidance.
CVE-2026-41186: CWE-489 Active Debug Code in Tigera Calico
Description
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.
CVSS v4.0
Score 6.0medium
Affected software
pkg:golang/github.com/projectcalico/calicoRun on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
This vulnerability arises from Calico's shared debug server binding its Go pprof debug listener to all network interfaces (0.0.0.0) without any authentication when enabled. This exposes internal runtime information including process heap memory, goroutine stacks with function arguments, and command-line arguments to any pod that can reach the listener over the network. The heap may contain sensitive data depending on the process's memory state. The debug server is opt-in and disabled by default, but if enabled, it is unsafe due to lack of authentication and no option to restrict binding to localhost only.
Potential Impact
An attacker with network access to the debug listener can obtain detailed runtime information from the Calico components, potentially exposing sensitive in-memory data. This can lead to information disclosure that may aid further attacks or compromise confidentiality. The vulnerability does not allow direct code execution or privilege escalation but exposes sensitive internal state.
Mitigation Recommendations
Since the debug listener is disabled by default, the primary mitigation is to avoid enabling the shared debug server unless absolutely necessary. If enabled, restrict network access to the debug listener to trusted pods only via network policies or firewall rules. There is no official fix or patch currently available; monitor the vendor advisory for updates. Patch status is not yet confirmed — check the vendor advisory for current remediation guidance.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- Tigera
- Date Reserved
- 2026-04-17T17:41:35.905Z
- Cvss Version
- 4.0
- State
- PUBLISHED
- Remediation Level
- null
Threat ID: 6a6b81699c2644c7f860ea84
Added to database: 07/30/2026, 16:52:57 UTC
Last enriched: 07/30/2026, 17:10:25 UTC
Last updated: 07/30/2026, 23:43:10 UTC
Views: 6
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.