# CVE-2026-123620: Usermin through 2.570 OS Command Injection via Read Mail IMAP Folder Deletion


- **Severity:** High 7.7 (`CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 6 Nov 2026
- **Updated:** 9 Nov 2026
- **Also known as:** GHSA-x534-mp2r-76p8

## What is CVE-2026-123620?

CVE-2026-123620 is a high-severity vulnerability in webmin usermin, published on 6 Nov 2026. 

### Official description

Usermin through 2.570 contains an OS command injection vulnerability in the Read Mail module that allows authenticated users to execute commands through unsanitized IMAP folder names. Attackers can create a folder containing shell metacharacters via an external IMAP client, then delete it in Usermin to run commands as their system account, bypassing webmail-only restrictions.

Weakness: CWE-78 (Improper Neutralization of Special Elements used in an OS Command)

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


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

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

## Is CVE-2026-123620 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-123620 is a high-severity vulnerability in webmin usermin, published on 6 Nov 2026. 
Exploitation: There is no known exploitation of CVE-2026-123620 in the wild and no public exploit code.

Affected product: webmin usermin. 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-123620/ (Markdown: https://insights.sbomify.com/CVE-2026-123620/index.md)
```

## Sources

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

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