heym before 0.0.91 Multiple Secrets Plaintext Storage (CVE-2026-100862) | HOL Guard CVE

Medium · CVSS 6.9CVE-2026-100862

heym before 0.0.91 Multiple Secrets Plaintext Storage

Answer in brief

CVE-2026-100862 records a Medium severity (CVSS 6.9) vulnerability in heym before 0.0.91 Multiple Secrets Plaintext Storage. The current sources do not mark it as known exploited. The current feed maps heymrun/heym (generic). Check affected ranges and fixed versions before updating.

Analysis pending evidence review

HOL Guard separates source facts from reviewed analysis. See the methodology.

Published Sep 27, 2026Updated Sep 27, 2026Source checked Sep 27, 2026First seen by HOL Sep 27, 2026Material review Sep 27, 2026

Upstream Advisory

Key facts

Risk: Medium · CVSS 6.9
Exploitation: Not marked as known exploited
Affected software: 1 mapped package or product
Fix availability: Available

Why this deserves its current priority

CVSS is 6.9. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.

Analysis status

Analysis pending evidence review

Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.

Affected scope and exposure questions

The current feed maps heymrun/heym (generic). Check affected ranges and fixed versions before updating.

Mapped affected packages and fixed versions
Package	Affected range	Fixed version
heymrun/heymgeneric	>=0 <0.0.91	0.0.91

Recommended response

Check inventory. Check lockfiles and deployed manifests for heymrun/heym.
Review the reported fix. Update heymrun/heym to 0.0.91 if you use the affected versions. Test the change in a non-production environment first.

Evidence timeline and material changes

Published upstream
Sep 27, 2026
Evidence: source:cvelist:source_dates:source-dates:record
Source modified
Sep 27, 2026
Evidence: source:cvelist:source_dates:source-dates:record
First seen by HOL
Sep 27, 2026

Sources and claim methodology

Upstream source description

heym, a workflow automation platform, stores and returns multiple capability secrets in plaintext in versions prior to 0.0.91. Affected secrets include webhook header-auth values (returned in cleartext by GET /api/workflows/{id} and persisted unsanitized into execution history), MCP API keys (stored as a plaintext column, returned in config/list responses, and accepted via the ?key= query string so they leak into logs, proxies and Referer headers), portal session tokens (stored and validated by plaintext equality with a 168-hour TTL), workflow execution JWTs (stored in full and re-listed by GET .../execution-tokens), Discord interaction tokens (the full interaction body is stored in execution history), and global variables. A user with read access to a workflow, share/team membership, or anyone able to read the database, a backup, or logs can recover these secrets and replay them to execute workflows or act as the secret owner.

Quoted source text, attributed separately from HOL analysis.