CVE-2026-34072: Cr*nMaster (cronmaster) is a Cronjob management UI with human readable syntax, live logging and log history fo
CVE-2026-34072 is a high-severity flaw (CVSS 8.3) affecting cronmaster. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.
Cr*nMaster (cronmaster) is a Cronjob management UI with human readable syntax, live logging and log history for cronjobs. Prior to version 2.2.0, an authentication bypass in middleware allows unauthenticated requests with an invalid session cookie to be treated as authenticated when the middleware’s session-validation fetch fails. This can result in unauthorized access to protected pages and unauthorized execution of privileged Next.js Server Act
Why this priority
- High severity
A fixed release or distro patch exists.
Last updated 2026-10-26 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score
Am I affected?
Timeline
- Published CVE record published
- Updated Record last modified
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.
Quick answers
How do I fix CVE-2026-34072?
cronmaster: upgrade to 2.2.0. Exact commands for each OS are on this page.
Is CVE-2026-34072 being exploited?
CVE-2026-34072 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.
What does CVE-2026-34072 affect?
CVE-2026-34072 affects cronmaster. Severity is high (CVSS 8.3). Cr*nMaster (cronmaster) is a Cronjob management UI with human readable syntax, live logging and log history for cronjobs. Prior to version 2.2.0, an authentication bypass in middleware allows unauthenticated requests with an invalid session
How urgent is CVE-2026-34072?
Priority 39/100. High severity