CVE-2026-45021: Kuma: Default kuma-cp leaks admin token cross-origin via CORS wildcard + LocalhostIsAdmin
Noroxi assessment
Priority: Monitor (action score 20/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.27% (FIRST EPSS).
- Anyone who can reach it over the internet can trigger it. No account or password is required. No special conditions are required; it is repeatable.
- According to CISA the attack is automatable: targets can be found by mass scanning.
- Fixed version: kumahq kuma 2.7.25.
Low priority for now. Upgrade to kumahq kuma 2.7.25 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
Kuma is a modern Envoy-based service mesh that can run on every cloud across both Kubernetes and VMs. Prior to 2.7.25, 2.9.15, 2.11.13, 2.12.10, and 2.13.5, the default kuma-cp config leaks the admin bootstrap token and signing keys to any webpage the operator visits while the control plane is reachable from their browser. CorsAllowedDomains: [".*"] reflects any Origin, and LocalhostIsAdmin: true promotes requests from 127.0.0.1 to mesh-system:admin. A cross-origin fetch() from a malicious page returns the admin JWT and signing material. This vulnerability is fixed in 2.7.25, 2.9.15, 2.11.13, 2.12.10, and 2.13.5.
- Published
- May 28, 2026
- Updated
- Oct 25, 2026
- EPSS
- 0.2% · 20th percentile
- CWE
- CWE-346
Report tools
Action score
20
Low priority for now.
- CVSS
- 20 / 40 · 5.1 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.2%
CISA SSVC decision
- Exploitation
- none
- Automatable
- yes
- Technical impact
- partial
Vulnrichment: CISA's decision-tree inputs.
CNA vs NVD score
- NVD
- —
- CNA · GitHub_M
- 5.1
- NVD has not scored this yet; the score shown is the CNA’s.
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:A/VC:L/VI:L/VA:N/SC:N/SI:N/SA:N
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.
Is your version affected? Check itNoroxi 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.
—
Versions reported by the vendor
Affected version ranges reported by the assigning authority (GitHub_M). Independent of NVD's CPE analysis and usually ahead of it.
kumahq kuma
- < 2.7.25, >= 2.9.0, < 2.9.15, >= 2.11.0, < 2.11.13, >= 2.12.0, < 2.12.10, >= 2.13.0, < 2.13.5affected
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/kumahq/kuma | from 0 | — |
| Go | github.com/kumahq/kuma | from 2.11.0 · before 2.11.13 | 2.11.13 |
| Go | github.com/kumahq/kuma | from 2.12.0 · before 2.12.10 | 2.12.10 |
| Go | github.com/kumahq/kuma | from 2.13.0 · before 2.13.5 | 2.13.5 |
| Go | github.com/kumahq/kuma | from 2.9.0 · before 2.9.15 | 2.9.15 |
| Go | github.com/kumahq/kuma | before 2.7.25 | 2.7.25 |
| Go | github.com/kumahq/kuma/v2 | from 2.12.4 · before 2.12.10 | 2.12.10 |
| Go | github.com/kumahq/kuma/v2 | from 2.13.0 · before 2.13.5 | 2.13.5 |
| Go | github.com/kumahq/kuma/v2 | from 2.9.13 · before 2.11.13 | 2.11.13 |
| Go | github.com/kumahq/kuma/v2 | before 2.7.25 | 2.7.25 |
Same product
kumahq: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-52724kuma-dp connects to control plane without verifying TLS certificate when no CA is configured23Monitor
- CVE-2026-50166Kuma: kumactl connects to control plane without verifying TLS certificate when no CA is configured22Monitor
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 |
|---|---|---|
| kumahq kuma | 2.7.25 · description | Vendor (CNA) |
| Go:github.com/kumahq/kuma | 2.11.13 | Package registry (OSV) |
| Go:github.com/kumahq/kuma | 2.12.10 | Package registry (OSV) |
| Go:github.com/kumahq/kuma | 2.13.5 | Package registry (OSV) |
| Go:github.com/kumahq/kuma | 2.7.25 | Package registry (OSV) |
| Go:github.com/kumahq/kuma | 2.9.15 | Package registry (OSV) |
| Go:github.com/kumahq/kuma/v2 | 2.11.13 | Package registry (OSV) |
| Go:github.com/kumahq/kuma/v2 | 2.12.10 | Package registry (OSV) |
| Go:github.com/kumahq/kuma/v2 | 2.13.5 | Package registry (OSV) |
| Go:github.com/kumahq/kuma/v2 | 2.7.25 | 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.
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
Not on record for this CVE: EPSS history · researcher credit · variant or chain candidate · public bounty program.
Technical details
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- No account or password is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- Integrity
- Availability
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- A
- Scope
- X
Weakness class (CWE)
CWE-346 · Origin Validation ErrorCVSS vector
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:A/VC:L/VI:L/VA:N/SC:N/SI:N/SA:N/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)
- JSON Hijacking (aka JavaScript Hijacking)CAPEC-111likelihood: High · High
- Cache PoisoningCAPEC-141likelihood: High · High
- DNS Cache PoisoningCAPEC-142likelihood: High · High
- Exploit Script-Based APIsCAPEC-160Medium
- Exploitation of Trusted IdentifiersCAPEC-21likelihood: High · High
- Application API Message Manipulation via Man-in-the-MiddleCAPEC-384Low
- Transaction or Event Tampering via Application API ManipulationCAPEC-385Medium
- Application API Navigation RemappingCAPEC-386Medium
ATT&CK techniques
- Access Token ManipulationT1134
- Access Token Manipulation:Token Impersonation/TheftT1134.001
- Steal Application Access TokenT1528
- Steal Web Session CookieT1539
- Use Alternate Authentication Material:Web Session CookieT1550.004
- Adversary-in-the-Middle: ARP Cache PoisoningT1557.002
- Compromise Infrastructure: DNS ServerT1584.002
Change log (1)
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (7 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.