Vulnerability in Cronicle (CVE-2026-39401)
Summary
Vulnerability in Cronicle (CVE-2026-39401). Risk of unauthorized operations or information disclosure. Mitigation: upgrade to 0.9.111 or later.
Original description
The description as published by the source.
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.
Source: NIST National Vulnerability Database NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-39401 has been found in Cronicle.
Risk of unauthorized operations or information disclosure. CVSS score: 5.4/10.
What to do: upgrade Cronicle to 0.9.111 or later.
If unsure, ask your IT team or search "Cronicle CVE-2026-39401" on the vendor's site.
CVE-2026-39401 (Cronicle) — CWE-862 / CVSS v3 5.4
Attack vector: remote (network-reachable) / no user interaction
Patched: 0.9.111 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
A vulnerability (CWE-862) exists in Cronicle.
Check the vendor advisory for the affected versions of Cronicle.
Severity: Medium (CVSS 5.4/10). Risk of unauthorized operations or information disclosure.
Update to 0.9.111.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'Cronicle' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'Cronicle' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
Cronicleを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade Cronicle to 0.9.111ステージング環境で 0.9.111 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
References
- advisory github.com
- advisory github.com
- advisory nvd.nist.gov