Skip to content
Noroxi
NVD / CVE Program· CNA Tigera

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

Noroxi assessment

Priority: Monitor (action score 24/100)

  • The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
  • Probability of exploitation in the next 30 days: 0.66% (FIRST EPSS); higher than 51.5% of all records.
  • Someone on the same network segment can trigger it. No account or password is required. No user action is required. No special conditions are required; it is repeatable.
  • Fixed version: Tigera Calico 3.31.6, 3.32.1; Tigera Calico Cloud 22.4.0; Tigera Calico Enterprise 3.21.7, 3.22.4.

Low priority for now. Upgrade to Tigera Calico 3.31.6, 3.32.1; Tigera Calico Cloud 22.4.0; Tigera Calico Enterprise 3.21.7, 3.22.4 or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

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.

MediumCVSS 6.0 · v4.0—No exploit Fix available
Published
Jul 30, 2026
Updated
Aug 7, 2026
EPSS
0.6% · 51th percentile

Report tools

JSON

Action score

24

Monitor

Low priority for now.

CVSS
24 / 40 · 6.0 / 10
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.6%

CISA SSVC decision

Exploitation
none
Automatable
no
Technical impact
partial

Vulnrichment: CISA's decision-tree inputs.

CNA vs NVD score

NVD
—
CNA · Tigera
6.0
NVD has not scored this yet; the score shown is the CNA’s.

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

The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.

Get told when this record changes

  • Not in KEV: no record of exploitation in the wild
  • No public exploit code on record
  • A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Follow CVE-2026-41186

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits instantly.

Your free account also gets you

Running WordPress? Scan your site free with WP Lens

  • Stack alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

VendorProduct
tigeracalico

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

  • tigera calicobefore 3.21.7
  • tigera calicobefore 3.31.6
  • tigera calicoup to 22.4.0 inclusive
  • tigera calico3.22.0 and later · before 3.22.4
  • tigera calico3.32.0 and later · before 3.32.1

Versions reported by the vendor

Affected version ranges reported by the assigning authority (Tigera). Independent of NVD's CPE analysis and usually ahead of it.

  • Tigera Calico

    • before 3.31.6affected · semver
    • 3.32.0 and later · before 3.32.1affected · semver
  • Tigera Calico Cloud

    • before 22.4.0affected · semver
  • Tigera Calico Enterprise

    • before 3.21.7affected · semver
    • 3.22.0 and later · before 3.22.4affected · semver

Other highest-scoring records for the same primary product.

  • CVE-2026-6540L7 policy bypass via unnormalized HTTP path matching
    31Monitor
  • CVE-2026-6720Calicoctl leaks cluster credentials to stderr when verbose logging is enabled
    28Monitor
  • CVE-2024-33522Privilege escalation in Calico CNI install binary
    26Monitor

Published before and after this one in the same product

  • ← EarlierCVE-2026-41184May 28, 2026 · ServiceAccount token disclosure via install-cni container logs
    24Monitor
  • ← EarlierCVE-2026-41185May 28, 2026 · ServiceAccount token disclosure via Azure IPAM CNI plugin logs
    24Monitor
  • Later →CVE-2026-41187Jul 30, 2026 · Calico Tier Authorization Bypass via DeleteCollection
    24Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
Tigera Calico3.31.6Vendor (CNA)
Tigera Calico3.32.1Vendor (CNA)
Tigera Calico Cloud22.4.0Vendor (CNA)
Tigera Calico Enterprise3.21.7Vendor (CNA)
Tigera Calico Enterprise3.22.4Vendor (CNA)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

EPSS, last 120 days

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

Technical details

Attack conditions

  • Someone on the same network segment can trigger it.
  • No account or password is required.
  • No user action is required.
  • No special conditions are required; it is repeatable.

If successful

Confidentiality
Integrity
Availability
Attack vector
Adjacent
Attack complexity
Low
Privileges required
None
User interaction
None
Scope
X

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

nvd-secondary

Root cause

The extension requests broader permissions than its function needs and sends the data it collects out for purposes beyond its stated function.

A representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.

Vulnerable

json
{  "permissions": ["tabs", "<all_urls>"],  "background": { "service_worker": "analytics.js" }}

Fixed

json
{  "permissions": ["activeTab"],  "host_permissions": ["https://yildiz.example/*"]}

Change log

  1. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

Show all references (3 more)

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records