# CVE-2026-72589: alseambusher crontab-ui - Unauthenticated RCE via Shell Injection in Imported Database hook Field

> Unauthenticated attackers can execute arbitrary system commands by uploading a malicious database file to the import endpoint.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 10 Aug 2026
- **Updated:** 10 Aug 2026
- **Also known as:** GHSA-r4j6-x8h7-4f8w

## What is CVE-2026-72589?

CVE-2026-72589 is a critical command injection vulnerability in alseambusher crontab-ui, published on 10 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

An OS command injection vulnerability in alseambusher/crontab-ui through 0.4.2 allows an unauthenticated remote attacker to execute arbitrary system commands by importing a crafted crontab database file. The POST /import endpoint accepts arbitrary .db files and overwrites the application database without validation.

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

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


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

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

## Is CVE-2026-72589 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-72589 is a critical command injection vulnerability in alseambusher crontab-ui, published on 10 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-72589 in the wild and no public exploit code.

Affected product: alseambusher crontab-ui. 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-72589/ (Markdown: https://insights.sbomify.com/CVE-2026-72589/index.md)
```

## Sources

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

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