CVE-2026-41185: ServiceAccount token disclosure via Azure IPAM CNI plugin logs
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.32% (FIRST EPSS).
- Anyone who can reach it over the internet can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: Tigera Calico 3.32.0; Tigera Calico Cloud 22.4.0; Tigera Calico Enterprise 3.21.7, 3.22.3.
Low priority for now. Upgrade to Tigera Calico 3.32.0; Tigera Calico Cloud 22.4.0; Tigera Calico Enterprise 3.21.7, 3.22.3 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 is configured with the Azure IPAM plugin, the Calico CNI binary mutates the incoming CNI configuration to attach subnet information before delegating to the IPAM plugin. After mutating, the Azure IPAM helper logs the entire unmarshaled configuration map (stdinData) at INFO level to /var/log/calico/cni/cni.log on every CNI ADD and DEL invocation — once per pod scheduled or terminated on the node. When the cluster is deployed using token-based Kubernetes authentication, this log entry contains the ServiceAccount token, client key, and certificate authority in plaintext. Any principal with read access to /var/log/calico/cni/cni.log on a node can read these logs and extract the credentials, which grant cluster-wide Calico networking admin privileges.
- Published
- May 28, 2026
- Updated
- Jun 17, 2026
- EPSS
- 0.3% · 25th percentile
- CWE
- CWE-532
Report tools
Action score
24
Monitor
Low priority for now.
- CVSS
- 24 / 40 · 6.0 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.3%
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:N/AC:L/AT:P/PR:L/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.
Running WordPress? Scan your site free with WP Lens
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 helpAffected 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.
| Vendor | Product | CPE |
|---|---|---|
| tigera | calico | cpe:2.3:a:tigera:calico |
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.32.0
- tigera calicobefore 22.4.0
- tigera calico3.22.0 and later · before 3.22.3
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.32.0affected · 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.3affected · semver
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Go | github.com/projectcalico/calico | from 2.0.0 · before 3.31.6 | 3.31.6 |
| Go | github.com/projectcalico/calico | before 1.11.0-cni-plugin.0.20260417001138-cd73bc2cea0f | 1.11.0-cni-plugin.0.20260417001138-cd73bc2cea0f |
| Go | github.com/projectcalico/calico/v3 | from 0 | — |
Same product
tigera: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-6540L7 policy bypass via unnormalized HTTP path matching31Monitor
- CVE-2026-6720Calicoctl leaks cluster credentials to stderr when verbose logging is enabled28Monitor
- CVE-2024-33522Privilege escalation in Calico CNI install binary26Monitor
Published before and after this one in the same product
- ← EarlierCVE-2022-28224Jun 6, 2022 · Calico and Calico Enterprise may be vulnerable to route hijacking with the floating IP feature22Monitor
- Later →CVE-2026-41184May 28, 2026 · ServiceAccount token disclosure via install-cni container logs24Monitor
- Later →CVE-2026-41186Jul 30, 2026 · Unauthenticated Go pprof exposure in Calico debug server24Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Tigera Calico | 3.32.0 | Vendor (CNA) |
| Tigera Calico Cloud | 22.4.0 | Vendor (CNA) |
| Tigera Calico Enterprise | 3.21.7 | Vendor (CNA) |
| Tigera Calico Enterprise | 3.22.3 | Vendor (CNA) |
| Go:github.com/projectcalico/calico | 1.11.0-cni-plugin.0.20260417001138-cd73bc2cea0f | Package registry (OSV) |
| Go:github.com/projectcalico/calico | 3.31.6 | Package registry (OSV) |
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.
No history yet (it accumulates with the daily EPSS job).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
- Behnam Shobirifinder
- Anthony Tamremediation reviewer
- Matt Dupreremediation reviewer
- Casey Davenportremediation verifier
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
- CVE-2026-67200 days apartCalicoctl leaks cluster credentials to stderr when verbose logging is enabled28Monitor
- CVE-2026-411840 days apartServiceAccount token disclosure via install-cni container logs24Monitor
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
- Anyone who can reach it over the internet can trigger it.
- A low-privileged account is enough.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- Integrity
- Availability
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- None
- Scope
- X
Weakness class (CWE)
CWE-532 · Insertion of Sensitive Information into Log FileCVSS vector
CVSS:4.0/AV:N/AC:L/AT:P/PR:L/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
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Attack patterns (CAPEC)
ATT&CK techniques
—
Change log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (3 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.