# CVE-2026-82882: Devtron through 2.2.0 Missing Authorization via webhook API token endpoint

> Authenticated users can retrieve admin API tokens via an unprotected endpoint, enabling full platform control and privilege escalation.

- **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:** No
- **Published:** 31 Aug 2026
- **Updated:** 24 Sep 2026
- **Also known as:** GHSA-mrqp-7v92-wchj

## What is CVE-2026-82882?

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

### Official description

Devtron through 2.2.0 fails to enforce authorization checks on the GET /orchestrator/api-token/webhook endpoint, allowing authenticated users to retrieve admin API tokens. Attackers with any authenticated account can query the endpoint with arbitrary project, environment, and application parameters to retrieve plaintext super-admin JWT tokens for full platform control.

Weakness: CWE-862 (Missing Authorization)

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


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

No fix has been published for CVE-2026-82882 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-82882 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-82882 is a high-severity missing authorization vulnerability in devtron-labs devtron, published on 31 Aug 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-82882 exists.

Affected product: devtron-labs devtron. No package-level version data is available, so check the vendor advisory linked from the reference page.

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-82882/ (Markdown: https://insights.sbomify.com/CVE-2026-82882/index.md)
```

## Sources

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

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