CVE-2026-25538: devtron · Missing Authorization
Affects devtronSource CVE Database V5
Not known to be exploited · CVSS 8.7 High.
Data as of 26 Oct 2026, 06:26 UTC
- EPSS
- 0.4% chance of exploitation in 30 days – higher than 38% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:NExploitation evidence
Disclosed: evidence found.
CVE published 4 Feb 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-26.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| devtron-labsdevtron | Affected
| Fixed in– |
GitHubdevtron-labs/devtronpkg:github/devtron-labs/devtronOther threats | Affected
| Fixed in– |
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
1. Immediately upgrade Devtron installations to versions later than 2.0.0 where the vulnerability is patched. 2. Restrict access to the /orchestrator/attributes API endpoint to only highly trusted and necessary users or service accounts. 3. Implement strict role-based access controls (RBAC) within Devtron and Kubernetes to minimize privileges of CI/CD developers and other users. 4. Monitor API access logs for suspicious requests to the Attributes API, especially attempts to access apiTokenSecret keys. 5. Rotate API token signing keys after patching to invalidate any potentially compromised tokens. 6. Employ network segmentation and zero-trust principles to limit lateral movement opportunities within Kubernetes clusters. 7. Conduct regular security audits and penetration testing focused on authorization controls in DevOps tools. 8. Educate development and operations teams about the risks of excessive privileges and the importance of secure CI/CD practices.
Description
CVE-2026-25538 is a high-severity vulnerability in Devtron versions 2.0.0 and earlier, where an authorization bypass in the Attributes API allows any authenticated user, including low-privileged CI/CD developers, to retrieve the global API token signing key. With this key, attackers can forge JWT tokens for any user identity, gaining full control over the Devtron platform and enabling lateral movement into the underlying Kubernetes cluster. The vulnerability requires no user interaction and can be exploited remotely with low complexity. This flaw has been patched in later versions. European organizations using Devtron for Kubernetes integration are at risk of severe confidentiality, integrity, and availability impacts if unpatched. Mitigation involves immediate upgrading to patched versions and restricting access to the Attributes API endpoint. Countries with significant Kubernetes adoption and Devtron usage, such as Germany, the UK, France, and the Netherlands, are most likely affected.