Privilege Escalation via update_event Job Output in Cronicle
Key facts
- Attack vector
- Network
- Privileges required
- Low
- User interaction
- None
- Attack complexity
- Low
- Attack requirements
- None
- Impact type
- Security bypass
- Confidentiality · integrity · availability
- None · Low · None
- Fix status
- Fixed
Attack profile from CVSS 4.0 · CNA. Fix status from CNA. Impact type from CWE-862.
Summary
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.
Why it matters now
SSVC decision points
CISA ADP · SSVC 2.0.3
- Exploitation
- Poc
- Automatable
- No
- Technical impact
- Partial
The decision (Track, Attend, Act) also depends on your mission and well-being impact; see CISA's SSVC guide.
Affected products
Remediation
- Fix · CNA Cronicle (jhuckaby) Fixed in 0.9.111
Timeline
- 2026-10-02 Threatist record created from CVE-2026-39401
References
More jhuckaby vulnerabilities
- TI-2026-71909 Stored cross-site scripting in Cronicle admin Activity Log CVSS 3.1CRITICAL 9.0
- TI-2026-81575 Cronicle lets non-admin users set run-as uid and gid in events CVSS 3.1HIGH 8.8
- TI-2026-85660 Environment variable injection in Cronicle event params CVSS 4.0CRITICAL 9.0
Sources
This product uses the NVD API but is not endorsed or certified by the NVD. Sources and licences