CVE-2026-72590: alseambusher crontab-ui - Unauthenticated RCE via Newline Injection in env_vars Parameter
An OS command injection vulnerability in alseambusher/crontab-ui through 0.4.2 allows an unauthenticated remote attacker to inject arbitrary cron job entries by sending a crafted GET request to /crontab with URL-encoded newlines in the env_vars parameter.
Security readout for executives and security teams
Plain-English summary
CVE-2026-72590 is a critical flaw in crontab-ui through version 0.4.2. An attacker who can reach the application may alter scheduled tasks without authentication, potentially running commands, stealing data, changing systems, or disrupting service.
Executive priority
Treat as an immediate remediation priority for reachable deployments. First isolate exposed instances, then determine versions and inspect scheduled tasks for compromise. Systems limited to trusted administrative networks remain vulnerable but have lower practical exposure.
Technical view
The /crontab endpoint accepts env_vars in a GET request. URL-encoded newline characters can inject additional cron entries, creating an OS command-injection path without privileges or user interaction. The supplied CVSS 3.1 score is 9.8, with high confidentiality, integrity, and availability impact.
Likely exposure
Deployments through 0.4.2 are potentially exposed when crontab-ui is reachable by untrusted users, especially from the internet. Actual exposure depends on deployed version, network controls, and whether access is independently restricted. The source bundle provides no deployment prevalence data.
Exploitation context
The attack is remotely reachable, low complexity, unauthenticated, and requires no user interaction according to the supplied CVSS vector. However, the CVE is not listed as KEV, and the provided sources do not establish active exploitation or public exploit availability.
Researcher notes
The issue is classified as CWE-93 newline injection and affects crontab-ui through 0.4.2 according to the description. The bundle does not identify a patched version, vendor advisory, exploitation evidence, or affected deployment configurations. Its affected-version array contains only “0,” so authoritative version confirmation is warranted.
Mitigation direction
Identify and restrict access to all crontab-ui deployments immediately.
Remove internet exposure and limit access to trusted administrative networks.
Check vendor guidance and upgrade when a confirmed fixed release is available.
Review scheduled tasks and affected hosts for unauthorized changes.
Use existing gateway controls to reject suspicious newline-bearing requests as a temporary safeguard.
Validation and detection
Inventory crontab-ui instances and record their deployed versions.
Confirm whether untrusted users can reach the /crontab endpoint.
Review application and proxy logs for suspicious env_vars requests.
Inspect cron configuration for unexpected entries or environment-variable changes.
Verify network restrictions prevent unauthenticated access from untrusted sources.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · low confidence lookup
CWE-93: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
1CVSS vectors
5Timeline events
1ADP providers
3Source links
SSVC decision data
CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: yesTechnical Impact: total
CVSS vector scores
1 official score
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-93 · source CWE mapping
Improper Neutralization of CRLF Sequences ('CRLF Injection')
Improper Neutralization of CRLF Sequences ('CRLF Injection') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.