CVE-2026-72590
Unauthenticated OS command injection in crontab-ui allowing arbitrary cron job creation.
Is CVE-2026-72590 being exploited?
Not confirmed. CVE-2026-72590 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 1.3% probability of exploitation in the next 30 days.
How severe is CVE-2026-72590?
CVE-2026-72590 is rated Critical with a CVSS score of 9.8. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2026-72590?
Not known from our data. No patch reference has been recorded for CVE-2026-72590, which is not the same as no patch existing — a fix may have shipped without a tagged reference, or after this record was written. The vendor advisory is the only authority on whether a fix exists, and mitigations may be available regardless.
What does CVE-2026-72590 affect?
CVE-2026-72590 affects alseambusher/crontab-ui <= 0.4.2, self-hosted crontab-ui instances, containers/images bundling crontab-ui. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-72590?
Remove/disable or isolate crontab-ui; apply vendor patch when released; block /crontab and restrict access.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Remote unauthenticated OS command injection via /crontab env_vars; attacker can create cron jobs to execute arbitrary commands.
Immediate action required
- affected<= 0.4.2
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.