CVE-2026-39401 | jhuckaby Cronicle up to 0.9.110 update_event authorization (GHSA-5j3v-cq96-xw6v / EUVD-2026-19925)
VulDBArchived Apr 08, 2026✓ Full text saved
A vulnerability was found in jhuckaby Cronicle up to 0.9.110 . It has been rated as problematic . Impacted is the function update_event . The manipulation leads to missing authorization. This vulnerability is listed as CVE-2026-39401 . The attack may be initiated remotely. There is no available exploit. Upgrading the affected component is advised.
Full text archived locally
✦ AI Summary· Claude Sonnet
VDB-355944 · CVE-2026-39401 · GHSA-5J3V-CQ96-XW6V
JHUCKABY CRONICLE UP TO 0.9.110 UPDATE_EVENT AUTHORIZATION
HISTORYDIFFRELATEJSONXMLCTI
CVSS Meta Temp Score Current Exploit Price (≈) CTI Interest Score
5.2 $0-$5k 1.47+
Summaryinfo
A vulnerability categorized as problematic has been discovered in jhuckaby Cronicle up to 0.9.110. The affected element is the function update_event. The manipulation results in authorization. This vulnerability is cataloged as CVE-2026-39401. The attack may be launched remotely. There is no exploit available. It is advisable to upgrade the affected component.
Detailsinfo
A vulnerability, which was classified as problematic, was found in jhuckaby Cronicle up to 0.9.110. Affected is the function update_event. The manipulation with an unknown input leads to a authorization vulnerability. CWE is classifying the issue as CWE-862. The product does not perform an authorization check when an actor attempts to access a resource or perform an action. This is going to have an impact on integrity, and availability. CVE summarizes:
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.111.
The advisory is shared for download at github.com. This vulnerability is traded as CVE-2026-39401 since 04/07/2026. The exploitability is told to be easy. It is possible to launch the attack remotely. There are known technical details, but no exploit is available.
Upgrading to version 0.9.111 eliminates this vulnerability.
The vulnerability is also documented in the vulnerability database at EUVD (EUVD-2026-19925).
Productinfo
Vendor
jhuckaby
Name
Cronicle
Version
0.9.110
Website
Product: https://github.com/jhuckaby/Cronicle/
CPE 2.3info
🔒
CPE 2.2info
🔒
CVSSv4info
VulDB Vector: 🔒
VulDB Reliability: 🔍
CNA CVSS-B Score: 🔒
CNA CVSS-BT Score: 🔒
CNA Vector: 🔒
CVSSv3info
VulDB Meta Base Score: 5.4
VulDB Meta Temp Score: 5.2
VulDB Base Score: 5.4
VulDB Temp Score: 5.2
VulDB Vector: 🔒
VulDB Reliability: 🔍
CVSSv2info
Vector Complexity Authentication Confidentiality Integrity Availability
Unlock Unlock Unlock Unlock Unlock Unlock
Unlock Unlock Unlock Unlock Unlock Unlock
Unlock Unlock Unlock Unlock Unlock Unlock
VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍
Exploitinginfo
Class: Authorization
CWE: CWE-862 / CWE-863 / CWE-285
CAPEC: 🔒
ATT&CK: 🔒
Physical: No
Local: No
Remote: Yes
Availability: 🔒
Status: Not defined
Price Prediction: 🔍
Current Price Estimation: 🔒
0-Day Unlock Unlock Unlock Unlock
Today Unlock Unlock Unlock Unlock
Threat Intelligenceinfo
Interest: 🔍
Active Actors: 🔍
Active APT Groups: 🔍
Countermeasuresinfo
Recommended: Upgrade
Status: 🔍
0-Day Time: 🔒
Upgrade: Cronicle 0.9.111
Timelineinfo
04/07/2026 Advisory disclosed
04/07/2026 +0 days CVE reserved
04/07/2026 +0 days VulDB entry created
04/07/2026 +0 days VulDB entry last update
Sourcesinfo
Product: github.com
Advisory: GHSA-5j3v-cq96-xw6v
Status: Confirmed
CVE: CVE-2026-39401 (🔒)
GCVE (CVE): GCVE-0-2026-39401
GCVE (VulDB): GCVE-100-355944
EUVD: 🔒
Entryinfo
Created: 04/07/2026 23:31
Updated: 04/07/2026 23:45
Changes: 04/07/2026 23:31 (67), 04/07/2026 23:45 (1)
Complete: 🔍
Cache ID: 99:1CF:101
Discussion
No comments yet. Languages: en.
Please log in to comment.
◂ PreviousOverviewNext ▸