# CVE-2026-58255 — jhuckaby Cronicle

> As of 2026-10-28, CVE-2026-58255 is a HIGH-severity vulnerability in jhuckaby Cronicle, CVSS v3.1 8.8, EPSS 0.4% (35.6th percentile). No Threadlinqs-tracked threat campaign has been attributed to CVE-2026-58255 as of 2026-10-28; the identifier is re-checked against the Threadlinqs threat corpus on every daily ingest.

**Last updated:** 2026-10-28

## What is CVE-2026-58255?

Cronicle is a multi-server task scheduler and runner, with a web based front-end UI. Prior to 0.9.121, a non-administrator user or scoped API key with `create_events` and `run_events` privileges can inject top-level `uid` and `gid` fields through `/api/app/create_event` or `/api/app/update_event`. In `lib/api.js`, `requireValidEventData` uses `validateOptionalParams` as a partial allow-list that silently passes unknown keys, storing the injected fields verbatim. In `lib/job.js`, `launchJob` copies the whole event into the job, and a plugin `uid` overrides the event `uid` only when the plugin defines one. The default `shellplug` and `urlplug` plugins do not define a `uid`, so the event-controlled identity survives into child-process launch. On a root-daemon installation, this lets a low-privileged user run jobs as arbitrary users, including root, bypassing the otherwise administrator-only run-as-user control. This API-side event injection is distinct from the job-output `uid`/`gid` injection addressed by CVE-2026-39401. This issue is fixed in version 0.9.121.

The record classifies CVE-2026-58255 under weakness classes [CWE-269](https://intel.threadlinqs.com/cwe/CWE-269), [CWE-862](https://intel.threadlinqs.com/cwe/CWE-862), [CWE-915](https://intel.threadlinqs.com/cwe/CWE-915). Its CVSS v3 base vector states that the flaw is reachable remotely over the network, needs low-privilege credentials, needs no user interaction, and has high impact on confidentiality, integrity, availability. 1 affected-product entry is recorded, across 1 vendor, listed below. The identifier was first published 23 days ago.

## Severity and exploitation probability

- **CVSS v3.1 base score:** 8.8 — HIGH (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **EPSS (FIRST):** 0.4% probability of exploitation in the next 30 days, higher than 35.6% of all scored CVEs
- **CISA KEV:** Not listed in the CISA Known Exploited Vulnerabilities catalog
- **Threadlinqs priority:** 5.8/10 — a Threadlinqs composite of the CVSS base score, the EPSS percentile and public exploit availability
- **Published:** 2026-10-27

## Is CVE-2026-58255 being exploited?

It currently carries a trending score of 39 in the Threadlinqs vulnerability feed.

## Affected products and versions

- **jhuckaby**: Cronicle

## How to fix CVE-2026-58255

No vendor patch reference has been recorded for CVE-2026-58255 in the tracked sources. Follow the references below for a fix, and treat the products listed above as exposed until the vendor states otherwise.

## Threat activity tracking CVE-2026-58255

No threat campaign in the Threadlinqs corpus currently references CVE-2026-58255, in its CVE list or as an indicator. The linkage is recomputed from the live corpus on every daily ingest, so this section fills in as soon as a tracked campaign cites the identifier.

## Sources

Enriched from CVE.org, NVD, FIRST EPSS. This product uses the NVD API but is not endorsed or certified by the NVD.

**Vendor advisory and patch**

- [github.com](https://github.com/jhuckaby/Cronicle/security/advisories/GHSA-9xpg-9w3g-mpwj)

**Other references**

- [github.com](https://github.com/jhuckaby/Cronicle/commit/f3d3550d0f3fe89bab52d3788f0db1dd10860df2)
- [github.com (v0.9)](https://github.com/jhuckaby/Cronicle/releases/tag/v0.9.121)

Canonical: https://intel.threadlinqs.com/cve/CVE-2026-58255
No Threadlinqs detection currently covers CVE-2026-58255; it is re-checked on every ingest.
Indicator values unlock with TL Creds (https://threadlinqs.com/tl-creds); MCP access for AI agents needs Purple: https://intel.threadlinqs.com/mcp
