CVSS 4.0
9.0 criticalCVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:HCVE-2026-85076 jhuckaby cronicle: Injection
Critical (9.0) in jhuckaby cronicle. EPSS 0.4% estimated probability of exploitation activity in the next 30 days.
On this page
Cronicle is a multi-server task scheduler and runner, with a web based front-end UI. Prior to 0.9.124, an authenticated non-admin with run_events, create_events, or edit_events privilege can supply undeclared keys in event params through api_create_event, api_update_event, or api_run_event. lib/api.js and lib/api/event.js validate the parameter object without restricting its keys, and lib/job.js uppercases those keys and applies them to the child process environment after administrator-defined plugin variables. A key that collides with a security-sensitive environment variable can therefore override the plugin execution context and may cause privilege escalation, arbitrary code execution, data access, or service disruption depending on the plugin and runtime. This issue is fixed in version 0.9.124.
Severity
- EPSS
- 0.4% (unchanged from 0.4% a week ago) estimated probability of exploitation activity in the next 30 days; 35th percentile. Scored 2026-11-13. A forecast for this CVE across the internet, not for your own systems.
- CISA's assessment (SSVC)
- Exploitation: none · Automatable: no · Technical impact: total, assessed 2026-11-09. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
- CWEs
- CWE-74 Improper Neutralization of Special Elements in Output Used by a Downstream Component (Injection)
CWE-863 Incorrect Authorization - OWASP Top 10
- A01:2025 Broken Access Control, A05:2025 Injection
- Published
- Modified
- NVD analysis
- Deferred: the NVD does not plan to analyze it
- Record from
- the NVD, synced
Ask an AI about this CVE
Show the prompt
Explain CVE-2026-85076 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-85076?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-85076?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-85076 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.
Badge for a README or a site
An image that stays current: it is drawn from the data each time it is fetched (a host that proxies images, as GitHub does, may show its copy for a while). Markdown:
[](https://cve.bz/cve/CVE-2026-85076)
HTML:
<a href="https://cve.bz/cve/CVE-2026-85076"><img src="https://cve.bz/cve/badge/CVE-2026-85076.svg" alt="CVE-2026-85076"></a>
Affected
Versions
From the CNA's record in the CVE List.
| Product | Affected |
|---|---|
| jhuckaby Cronicle | < 0.9.124 |
Attack patterns (CAPEC)
The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits. More on the page of CWE-74 (37).
History
- The NVD deferred its analysis
Changes since this site first stored the record. The same for every record: /api/public/changes.