Analysis and contextual insights are available on OpenCVE Cloud.
No vendor fix or workaround currently provided.
Additional remediation guidance may be available on OpenCVE Cloud.
Tracking
Sign in to view the affected projects.
No advisories yet.
Wed, 15 Apr 2026 20:30:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Cronicle
Cronicle cronicle |
|
| CPEs | cpe:2.3:a:cronicle:cronicle:*:*:*:*:*:*:*:* | |
| Vendors & Products |
Cronicle
Cronicle cronicle |
|
| Metrics |
cvssV3_1
|
Wed, 08 Apr 2026 19:45:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Jhuckaby
Jhuckaby cronicle |
|
| Vendors & Products |
Jhuckaby
Jhuckaby cronicle |
Wed, 08 Apr 2026 17:15:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
Tue, 07 Apr 2026 20:45:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Description | 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. | |
| Title | Privilege Escalation via update_event Job Output in Cronicle | |
| Weaknesses | CWE-862 | |
| References |
| |
| Metrics |
cvssV4_0
|
Status: PUBLISHED
Assigner: GitHub_M
Published:
Updated: 2026-04-08T16:14:54.345Z
Reserved: 2026-04-06T22:06:40.516Z
Link: CVE-2026-39401
Updated: 2026-04-08T16:11:38.507Z
Status : Analyzed
Published: 2026-04-07T21:17:18.547
Modified: 2026-04-15T20:23:40.270
Link: CVE-2026-39401
No data.
OpenCVE Enrichment
Updated: 2026-04-08T19:45:48Z