# openssl-encrypt (pip package, versions <= 1.4.8) fails to sanitize filenames read from untrusted drive data (outside the AES-GCM authenticated manifest) before printing them in the verify-usb comma...

Advisory record · `GHSA-c793-rj9w-r3wg`

- **Identifiers:** `GHSA-c793-rj9w-r3wg` · `CVE-2026-81694` · `PYSEC-2026-3960`
- **State:** Confirmed
- **Severity:** CVSS 9.3 Critical
- **Critical:** Yes: CVSS 9+
- **Weakness (CWE):** [CWE-117](https://cwe.mitre.org/data/definitions/117.html)
- **Tags:** [Other injection](https://agentprime.io/advisories/tag/injection.md)
- **Published:** 27 Aug 2026
- **Updated:** 10 Sept 2026
- **Reviewed by a person:** No

Published by the GitHub Advisory Database at 27 Aug 2026, 17:20 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

## Critical

Critical, because:

- CVSS score 9.3: 9.0 or more.

How we decide what’s critical: <https://agentprime.io/advisories/critical.md>

## Affected packages

- `openssl-encrypt` (PyPI): affected `<1.4.9`; fixed in `1.4.9`

## Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

> openssl-encrypt versions up to and including 1.4.8 do not sanitize filenames read from untrusted drive data before printing them in the verify-usb command's output. An attacker who can place files on a drive that a user checks can embed terminal control sequences in the filenames, which can repaint a forged PASSED result on screen and hide tamper detection. Upgrade to version 1.4.9, which sanitizes these names before display.

Written 1 Nov 2026.

## Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

## Severity and exploitation

- 9.3 Critical, CVSS 4.0: `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`, from CNA (VulnCheck)

- **CISA KEV:** Not listed.
- **EPSS:** 0.0025, the 16th percentile, on 12 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

## Timeline

- 31 Oct 2026, 14:10 UTC: First seen by agentprime
- 31 Oct 2026, 14:10 UTC: [Confirmed by OSV](https://osv.dev/vulnerability/PYSEC-2026-3960)

## Sources

- [GitHub Advisory Database: GHSA-c793-rj9w-r3wg](https://github.com/advisories/GHSA-c793-rj9w-r3wg)
- [OSV: GHSA-c793-rj9w-r3wg](https://osv.dev/vulnerability/GHSA-c793-rj9w-r3wg)
- <https://github.com/jahlives/openssl_encrypt/security/advisories/GHSA-c793-rj9w-r3wg>
- <https://www.vulncheck.com/advisories/verify-usb-before-1.4.9-output-injection-via-unsanitized-filenames>

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.

## Check whether this affects you

A Match means an installed version is in the affected range above. Most don’t affect the app; agentprime hasn’t analysed this one yet.

- With the agentprime MCP server (<https://api.agentprime.io/mcp>), ask your agent to check the project: `check_lockfile` sends a lockfile, `check_packages` a list of installed packages, and both return the Matches and the upgrades that clear them. `get_advisory` returns this record. Setup: <https://agentprime.io/mcp.md>
- In a browser: <https://agentprime.io/check/> reads your lockfile in the browser, never uploading it.
- Whether it touches your code, with file and line: the Claude Code plugin, <https://agentprime.io/plugin.md>
- As JSON: <https://api.agentprime.io/v1/advisories/GHSA-c793-rj9w-r3wg>, or `POST https://api.agentprime.io/v1/match` with your packages (<https://agentprime.io/api.md>)

---

The web page: <https://agentprime.io/advisories/GHSA-c793-rj9w-r3wg/>. Everything for agents: <https://agentprime.io/llms.txt>.