# CVE-2026-81707: openssl_encrypt before 1.4.9 ANSI Escape Injection via Identity Email

> Attackers can inject ANSI escape sequences into identity emails to forge fingerprint verification lines, bypassing out-of-band verification in openssl_encrypt.

- **Severity:** Critical 9.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 27 Aug 2026
- **Updated:** 1 Oct 2026
- **Also known as:** GHSA-fhj3-wp77-vmvw, GHSA-qjr2-x6mr-8xgf

## What is CVE-2026-81707?

CVE-2026-81707 is a critical vulnerability in jahlives openssl_encrypt, published on 27 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

openssl_encrypt before 1.4.9 fails to sanitize the email field of imported identity documents, allowing attackers to inject ANSI escape sequences that forge the fingerprint verification line displayed to users. Attackers can deliver a crafted identity bundle through normal contact-exchange flows or keyserver responses to manipulate terminal output and display a fraudulent fingerprint, bypassing the out-of-band verification mechanism that protects against key substitution attacks.

Weakness: CWE-20 (Improper Input Validation)

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


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

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

## Is CVE-2026-81707 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-81707 is a critical vulnerability in jahlives openssl_encrypt, published on 27 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-81707 in the wild and no public exploit code.

Affected product: jahlives openssl_encrypt. 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-81707/ (Markdown: https://insights.sbomify.com/CVE-2026-81707/index.md)
```

## Sources

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

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