CVE-2026-34072

What it is

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 Actions. This issue has been patched in version 2.2.0.

At a glance

Exploitability

Can be exploited from the same network segment without logging in. High risk of data exposure, data tampering.

Exploit odds

0.5% chance of exploitation in the next 30 days (EPSS).

Fix

A patch, advisory or fixed version is referenced. Upgrade or apply it.

Timeline

1. 2026-04-01 18:16 UTC PublishedDisclosed publicly on CVE.org and NVD
2. 2026-10-26 22:10 UTC Last updatedMost recent change to the record

Why it ranks here

• Exploited in the wild: no, CISA does not list it.
• Exploit odds: 0.5% in the next 30 days (EPSS).
• Severity: 8.3 HIGH (CVSS).
• Fix: a patch or advisory is linked.

Details

Published

2026-04-01 18:16 UTC

Last modified

2026-10-26 22:10 UTC

Exploit probability

0.5% · EPSS, next 30 days

Weakness

CWE-287 · Improper authentication

Record status

Analyzed

Affected

• Fccview Cronmaster < 2.2.0

Attack profile CVSS 3.1 · 8.3

Attack vector

Adjacent network

Complexity

Low

Privileges needed

None

User interaction

None

Scope

Unchanged

Confidentiality

High

Integrity

High

Availability

Low

Is it in your code?

Hand this to your coding agent. It searches your project for the affected products and checks versions. Nothing leaves your machine.

Read https://cve-list.com/agent/cve/CVE-2026-34072.md and follow it. Check whether this project is affected by CVE-2026-34072. Read only. Don't change anything and don't upload my code. Tell me yes, no or not sure, with the file as proof.

Copy as ticket · More options · Status badge