# CVE-2026-25538: Devtron Attributes API Unauthorized Access Leading to API Token Signing Key Leakage

> Low-privileged users can access an API endpoint to leak the signing key, allowing them to forge tokens and gain full control over the Devtron platform and Kubernetes cluster.

- **Severity:** High 8.7 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 4 Feb 2026
- **Updated:** 5 Feb 2026
- **Also known as:** GHSA-8wpc-j9q9-j5m2, GO-2026-4416

## What is CVE-2026-25538?

CVE-2026-25538 is a high-severity missing authorization vulnerability in devtron-labs devtron, published on 4 Feb 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Devtron is an open source tool integration platform for Kubernetes. In version 2.0.0 and prior, a vulnerability exists in Devtron's Attributes API interface, allowing any authenticated user (including low-privileged CI/CD Developers) to obtain the global API Token signing key by accessing the /orchestrator/attributes?key=apiTokenSecret endpoint. After obtaining the key, attackers can forge JWT tokens for arbitrary user identities offline, thereby gaining complete control over the Devtron platform and laterally moving to the underlying Kubernetes cluster. This issue has been patched via commit d2b0d26.

Weakness: CWE-862 (Missing Authorization)

## Which versions are affected by CVE-2026-25538?

3 open source packages ship an affected version, including github.com/devtron-labs/devtron. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `github.com/devtron-labs/devtron` | Go | All versions | None |
| `github.com/devtron-labs/devtron` | Go | All versions to 2.0.0 | None |
| `github.com/devtron-labs/devtron` | Go | All versions to 2.0.0 | None |

Products: Devtron Devtron.

## How do I fix CVE-2026-25538?

Apply the vendor's patch.

## Is CVE-2026-25538 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-25538 exists.

## Other vulnerabilities in devtron-labs devtron

- [CVE-2024-45794](https://insights.sbomify.com/CVE-2024-45794/): SQL Injection in CreateUser API in devtron (high 8.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-25538 and fix it if it is affected.

What it is: CVE-2026-25538 is a high-severity missing authorization vulnerability in devtron-labs devtron, published on 4 Feb 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-25538 exists.

Affected packages and fixed versions:
- github.com/devtron-labs/devtron (Go): affected all versions; no fix listed
- github.com/devtron-labs/devtron (Go): affected all versions up to 2.0.0; no fix listed
- github.com/devtron-labs/devtron (Go): affected all versions up to 2.0.0; no fix listed

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-25538/ (Markdown: https://insights.sbomify.com/CVE-2026-25538/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-25538
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-25538
- OSV: https://osv.dev/vulnerability/CVE-2026-25538

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-25538/
Summaries are generated and may contain mistakes; the official description above is the record.