# CVE-2026-78237: Insufficient input validation in Admin By Request (ABR)

> A low-privileged user can inject malicious entries into the sudoers file to gain persistent root access.

- **Severity:** High 7.8 (`CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:C/C:H/I:H/A:H`)
- **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:** 26 Aug 2026
- **Updated:** 28 Aug 2026
- **Also known as:** GHSA-9v6j-cr5f-p2gx

## What is CVE-2026-78237?

CVE-2026-78237 is a high-severity vulnerability in Admin By Request (ABR), published on 26 Aug 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Insufficient input validation in ABR allows a low-privileged user to inject malicious entries into the sudoers file, resulting in persistent root access that remained effective after the ABR session ended.

Weakness: CWE-20 (Improper Input Validation)

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


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

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

## Is CVE-2026-78237 being exploited?

There is no known exploitation of CVE-2026-78237 in the wild and no public exploit code.

## Fix prompt for AI coding agents

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

What it is: CVE-2026-78237 is a high-severity vulnerability in Admin By Request (ABR), published on 26 Aug 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-78237 in the wild and no public exploit code.

Affected product: Admin By Request (ABR). 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-78237/ (Markdown: https://insights.sbomify.com/CVE-2026-78237/index.md)
```

## Sources

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

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