# CVE-2026-82710: Terminal escape sequence injection in mix usage_rules.search_docs via package documentation metadata

> A malicious package publisher can inject terminal escape sequences into search results, potentially executing commands or modifying the clipboard when developers run searches.

- **Severity:** Low 2.3 (`CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:P/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 8 Sep 2026
- **Updated:** 8 Sep 2026
- **Also known as:** EEF-CVE-2026-82710, GHSA-j59f-776f-23hp

## What is CVE-2026-82710?

CVE-2026-82710 is a low-severity vulnerability in ash-project usage_rules, published on 8 Sep 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

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

Weakness: CWE-150 (Improper Neutralization of Escape, Meta, or Control Sequences)

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

1 open source package ship an affected version, including usage_rules.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `usage_rules` | Hex | From 0.1.18 | 1.2.8 |

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

Upgrade usage_rules to 1.2.8 or later.

## Is CVE-2026-82710 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-82710 is a low-severity vulnerability in ash-project usage_rules, published on 8 Sep 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2026-82710 in the wild and no public exploit code.

Affected packages and fixed versions:
- usage_rules (Hex): affected from 0.1.18; fixed in 1.2.8

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-82710/ (Markdown: https://insights.sbomify.com/CVE-2026-82710/index.md)
```

## Sources

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

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