CVE-2026-39401: Cronicle is a multi-server task scheduler and runner, with a web based front-end UI

Q: How do I fix CVE-2026-39401?

cronicle: upgrade to 0.9.111. Exact commands for each OS are on this page.

Q: Is CVE-2026-39401 being exploited?

CVE-2026-39401 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

Q: What does CVE-2026-39401 affect?

CVE-2026-39401 affects cronicle. Severity is medium (CVSS 5.4). Cronicle is a multi-server task scheduler and runner, with a web based front-end UI. Prior to 0.9.111, jb child processes can include an update_event key in their JSON output. The server applies this directly to the parent event's stored co

Q: How urgent is CVE-2026-39401?

Priority 26/100. Public exploit reference

Routine

MEDIUM 5.4UPGRADE

CVE-2026-39401 is a medium-severity flaw (CVSS 5.4) affecting cronicle. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

Cronicle is a multi-server task scheduler and runner, with a web based front-end UI. Prior to 0.9.111, jb child processes can include an update_event key in their JSON output. The server applies this directly to the parent event's stored configuration without any authorization check. A low-privilege user who can create and run events can modify any event property, including webhook URLs and notification emails. This vulnerability is fixed in 0.9.

Why this priority

Public exploit reference

A fixed release or distro patch exists.

Risk facts

CVSS score	5.4 (Medium)
Attack vector	Network (remote)
Attack complexity	Low
Privileges needed	Low
User interaction	None
EPSS exploit chance	0.2% (top 93%)
CISA exploited list	No
Weakness	CWE-862
Published	2026-04-07
Last modified	2026-07-20

Publisher (CNA): GitHub, Inc. · Vendor: cronicle

Last updated 2026-07-20 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2026-04-07 21:17 UTCPublished CVE record published
2026-07-20 20:10 UTCUpdated Record last modified

cronicle cronicle UPGRADE

Affected: < 0.9.111

Fixed in: 0.9.111

Safe to downgrade to: no unaffected older release

1. Check installed version

apt-cache policy cronicle || rpm -q cronicle || cronicle --version

2. UPGRADE to 0.9.111 (Debian / Ubuntu)

sudo apt update && sudo apt install --only-upgrade cronicle

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade cronicle

Note

Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.

Verify at the official source NVD · CVE Program · Report a problem with this page
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-39401?

cronicle: upgrade to 0.9.111. Exact commands for each OS are on this page.

Is CVE-2026-39401 being exploited?

CVE-2026-39401 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-39401 affect?

CVE-2026-39401 affects cronicle. Severity is medium (CVSS 5.4). Cronicle is a multi-server task scheduler and runner, with a web based front-end UI. Prior to 0.9.111, jb child processes can include an update_event key in their JSON output. The server applies this directly to the parent event's stored co

How urgent is CVE-2026-39401?

Priority 26/100. Public exploit reference

Related CVEs

CVE-2026-39400 MEDIUM 6.1 UPGRADE Cronicle is a multi-server task scheduler and runner, with a web based front-end UI

References

← Back to latest CVEs