# CVE-2026-100862: heym before 0.0.91 Multiple Secrets Plaintext Storage

> heym stores multiple secrets in plaintext, allowing attackers with read access to recover credentials and execute workflows or impersonate users.

- **Severity:** Medium 6.9 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 27 Sep 2026
- **Updated:** 30 Sep 2026
- **Also known as:** GHSA-6x65-w7q7-wg93, GHSA-v692-j72v-6h8x

## What is CVE-2026-100862?

CVE-2026-100862 is a medium-severity vulnerability in heymrun heym, published on 27 Sep 2026. An attacker needs administrator access to exploit it, with no action from the victim.

### Official 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.

Weakness: CWE-312 (Cleartext Storage of Sensitive Information)

## Which versions are affected by CVE-2026-100862?


## How do I fix CVE-2026-100862?

No fix has been published for CVE-2026-100862 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-100862 being exploited?

There is no known exploitation of CVE-2026-100862 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-100862 and fix it if it is affected.

What it is: CVE-2026-100862 is a medium-severity vulnerability in heymrun heym, published on 27 Sep 2026. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-100862 in the wild and no public exploit code.

Affected product: heymrun heym. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-100862/ (Markdown: https://insights.sbomify.com/CVE-2026-100862/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-100862
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-100862
- OSV: https://osv.dev/vulnerability/CVE-2026-100862

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-100862/
Summaries are generated and may contain mistakes; the official description above is the record.