CVE-2026-62979 Details
Description
jack lets users share media libraries through their Radarr/Sonarr stack, peer-to-peer. Prior to 0.1.0, `middleware/handle-error.ts` serializes raw `FetchError` objects into HTTP responses. `lib/servers/base.ts` attaches outbound request headers on upstream non-success responses and schema-validation failures; the public `extras` field in `lib/errors/FetchError.ts` remains enumerable and is emitted by JSON serialization. These headers include the internal Radarr/Sonarr `X-Api-Key` and custom connector headers such as `CF-Access-Client-Secret`. `lib/redact.ts` redacts logs and spans but not this response path. Any client with the shared peer API key, plus Cloudflare Access credentials if required by the deployment, can force an error without a race or user interaction. `GET /peer/items/:id` and `GET /servers/health` can expose the internal media-server key, while `GET /torznab/download/:id` can expose another peer's key and Cloudflare Access secrets. The /peer/search and /items routes catch these errors and are not affected. Disclosed internal keys grant full administrative control of the corresponding Radarr/Sonarr instance, crossing the intended boundary between friends' shared peer access and private backend credentials. This issue is fixed in version 0.1.0.
A vulnerability in Jack prior to version 0.1.0 allows for the exposure of internal Radarr/Sonarr API keys through serialized error responses. When Jack encounters a fetch error while communicating with Radarr/Sonarr or another peer, it includes outbound request headers in the response. These headers can contain the internal Radarr/Sonarr API key and Cloudflare Access tokens, which are returned verbatim without redaction. This issue can be exploited by any client with the shared peer API key and, if necessary, Cloudflare Access credentials.
Users should update to Jack version 0.1.0, where this vulnerability has been fixed. After updating, it is recommended to rotate any Radarr or Sonarr API keys that may have been exposed.
Metrics
CVSS 4.0 Severity and Vector Strings:
CVSS 3.x Severity and Vector Strings:
No data available for CVSS Version 2.0 on this CVE.
Volerion
Assessed Oct 30, 2026CISA-ADP
Assessed Oct 30, 2026References to Advisories, Solutions, and Tools
By selecting these links, you will be leaving this site. These are references gathered from the official CVE record and are not endorsed by Volerion.
| URL | Source(s) | Tag(s) |
|---|---|---|
| https://github.com/roziscoding/jack/commit/2b296b5137acca476f34a23b692dd8c04ae1f148 | [email protected] | Source CodeVendor |
| https://github.com/roziscoding/jack/releases/tag/v0.1.0 | [email protected] | Release NotesVendor |
| https://github.com/roziscoding/jack/security/advisories/GHSA-8gw5-7585-4997 | [email protected] | AdvisoryExploitRemedyVendor |
Weakness Enumeration
| CWE-ID | CWE Name | Source |
|---|---|---|
| CWE-200 | Exposure of Sensitive Information to an Unauthorized Actor | [email protected] |
| CWE-209 | Generation of Error Message Containing Sensitive Information | [email protected] |
Affected Products
| Product | Versions |
|---|---|
| roziscoding jack | < 0.1.0 (semver) |
CPE
Remediation
| |
Change History
2 change records found show changes
| Date | Action | Recorded By |
|---|---|---|
| Oct 30, 2026 | CVE Modified | CISA-ADP |
| Oct 30, 2026 | New CVE Received | [email protected] |
Volerion