# CVE-2026-41186: Unauthenticated Go pprof exposure in Calico debug server

> Unauthenticated access to Go pprof endpoints in Calico debug server allows attackers to read sensitive process memory and command-line arguments.

- **Severity:** Medium 6.0 (`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`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 30 Jul 2026
- **Updated:** 30 Jul 2026
- **Also known as:** GHSA-h3h4-j2qv-pv4j, MINI-2chq-629r-v3fj, MINI-5rq9-22fh-j2cx, MINI-93cm-mxjp-29q4, MINI-g572-cvhf-j396, MINI-hp9h-h8c5-8gq5, MINI-m6p8-fjfp-9hr4, MINI-v92v-x4h6-h648, MINI-vrpp-h8gp-5wwm

## What is CVE-2026-41186?

CVE-2026-41186 is a medium-severity vulnerability in Tigera Calico, published on 30 Jul 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official 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.

Weakness: CWE-489 (Active Debug Code), CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

## Which versions are affected by CVE-2026-41186?

It affects 1 product.


Products: Tigera Calico.

## How do I fix CVE-2026-41186?

Change a configuration setting.

## Is CVE-2026-41186 being exploited?

There is no known exploitation of CVE-2026-41186 in the wild and no public exploit code.

## Other vulnerabilities in Tigera Calico

- [CVE-2026-6540](https://insights.sbomify.com/CVE-2026-6540/): L7 policy bypass via unnormalized HTTP path matching (high 7.9)
- [CVE-2026-41187](https://insights.sbomify.com/CVE-2026-41187/): Calico Tier Authorization Bypass via DeleteCollection (medium 6.2)
- [CVE-2026-41184](https://insights.sbomify.com/CVE-2026-41184/): ServiceAccount token disclosure via install-cni container logs (medium 6.0)
- [CVE-2026-41185](https://insights.sbomify.com/CVE-2026-41185/): ServiceAccount token disclosure via Azure IPAM CNI plugin logs (medium 6.0)
- [CVE-2022-28224](https://insights.sbomify.com/CVE-2022-28224/): Calico and Calico Enterprise may be vulnerable to route hijacking with the floating IP feature (medium 5.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-41186 and fix it if it is affected.

What it is: CVE-2026-41186 is a medium-severity vulnerability in Tigera Calico, published on 30 Jul 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-41186 in the wild and no public exploit code.

Affected product: Tigera Calico. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-41186/ (Markdown: https://insights.sbomify.com/CVE-2026-41186/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-41186
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-41186
- OSV: https://osv.dev/vulnerability/CVE-2026-41186

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-41186/
Summaries are generated and may contain mistakes; the official description above is the record.