CVE-2026-25538
Devtron API token exposure enables JWT forgery and full control.
Is CVE-2026-25538 being exploited?
Not confirmed. CVE-2026-25538 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.41% probability of exploitation in the next 30 days.
How severe is CVE-2026-25538?
CVE-2026-25538 is rated High with a CVSS score of 8.7. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2026-25538?
Yes. A fix has been recorded for CVE-2026-25538. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-25538 affect?
CVE-2026-25538 affects Devtron Platform (2.0.0 and prior), Kubernetes cluster via Devtron. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-25538?
Upgrade to patched Devtron; rotate API tokens.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Attacker retrieves API signing key via Attributes API, forges JWTs offline for any user, gaining full Devtron and Kubernetes access.
Patch when possible
- affected<= 2.0.0
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.