# CVE-2026-82457: su-exec through 0.3 Privilege Escalation via Numeric User ID

> Attackers can escalate privileges to root by supplying large numeric user IDs that truncate to zero in su-exec.

- **Severity:** High 8.5 (`CVSS:4.0/AV:L/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:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 29 Aug 2026
- **Updated:** 24 Sep 2026
- **Also known as:** GHSA-qpg9-jg2w-m84x

## What is CVE-2026-82457?

CVE-2026-82457 is a high-severity vulnerability in ncopa su-exec, published on 29 Aug 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

su-exec through 0.3 fails to validate numeric user and group identifiers parsed with strtol before assigning to uid_t and gid_t, allowing truncation of out-of-range values to zero. Attackers can supply large numeric identifiers that truncate to root's identifier, causing su-exec to execute target programs with root privileges instead of intended unprivileged accounts.

Weakness: CWE-681 (Incorrect Conversion between Numeric Types)

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


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

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

## Is CVE-2026-82457 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-82457 is a high-severity vulnerability in ncopa su-exec, published on 29 Aug 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-82457 exists.

Affected product: ncopa su-exec. 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-82457/ (Markdown: https://insights.sbomify.com/CVE-2026-82457/index.md)
```

## Sources

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

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