Quick answers
- Is CVE-2026-81856 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-81856 being exploited in the wild.
- How severe is CVE-2026-81856?
- Informational severity, published 12 October 2026.
- Which products and versions are affected?
- Hexpm Hex from 0.0.1 before 2.5.2.
- Is there a fix for CVE-2026-81856?
- Yes: fixed in Hex 2.5.2. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-81856 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-81856?
- Check whether you run Hexpm Hex at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- Fixed in: Hex 2.5.2
Technical details
A CWE-150 improper neutralization vulnerability allows injection of ANSI escape sequences and Unicode bidirectional overrides through unescaped package repository and search service output in multiple Mix tasks. Hex.Shell.info/1 and Hex.Shell.error/1 print server-supplied strings directly to the terminal without sanitization, affecting metadata, URLs, and API error bodies. An unauthenticated attacker can publish a malicious package with embedded escape sequences in any indexed field to forge displayed content or execute clipboard writes via OSC 52 when a developer runs affected Mix tasks.
Affected products
- hexpm Hex from 0.0.1 before 2.5.2
Timeline
- 2026-10-12: disclosed