CVE-2026-82710

Terminal escape sequence injection in mix usage_rules.search_docs via package documentation metadata

LOW
2.3
CVSS Score
Published: September 8, 2026 at 12:23 AM UTC
Updated: September 8, 2026 at 03:18 PM UTC
1 product affected across 1 vendorUsageRules

Using usage_rules by ash-project?

Get instant alerts when new vulnerabilities affect usage_rules - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
LOW2.3
Exploit prediction
EPSS 0.7%
SSVC
No known exploit

Description

Improper Neutralization of Escape, Meta, or Control Sequences vulnerability in ash-project usage_rules allows a malicious package publisher to inject terminal control sequences into the output of mix usage_rules.search_docs. mix usage_rules.search_docs searches Hex documentation through search.hexdocs.pm, which indexes the documentation of every published package, and prints the matching results (title, package, type, doc reference, and highlighted snippets) to the terminal. The formatter in Mix.Tasks.UsageRules.SearchDocs interpolated those publisher-controlled fields verbatim, neutralizing no terminal control characters; the only transform it applied adds escape sequences rather than removing them. A malicious package can embed ANSI terminal escape sequences (cursor movement, line erase, carriage returns, OSC 52 clipboard writes) in its indexed documentation, so when a developer runs a search that surfaces those docs the sequences reach the terminal unchanged — forging the displayed hexdocs URL or a suggested command, hiding text, or writing to the clipboard. No authentication or privileged position is required; only publishing a package. This issue affects usage_rules: from 0.1.18 before 1.2.8.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

0.1.18 ≤ v < 1.2.80.1.182da7a99536041d63ec1f391d019565789a59595f
Vendor states this is fixed in 3b8ebb4117d3272bbd436e6c2432113ba6685dbb (fixed)
Affected range stops below 1.2.8, so it looks safe — our inference, not a vendor statement

Remediation

No guide yet

No remediation guidance has been written for this CVE yet. What the record does show:

SSVC — Action Prioritization

SSVCNo known exploitNot automatablePartial impact

SSVC signals action urgency (what to patch first), separate from CVSS which measures severity.

CVSS

2.3LOWEEF
Vector?

Quick Info

StatusDEFERRED
CWE
CWE-150

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card