# CVE-2026-81692: openssl_encrypt before 1.4.9 Denial of Service via STREAMINFO

> A crafted FLAC file causes excessive memory allocation in openssl_encrypt, leading to denial of service during stego extraction.

- **Severity:** High 8.7 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/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-jvx4-p844-xhj6, GHSA-wr9q-p3rj-vqq7

## What is CVE-2026-81692?

CVE-2026-81692 is a high-severity denial of service 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 (pip: openssl-encrypt) versions 1.4.8 and earlier fail to validate the 36-bit STREAMINFO total_samples field of FLAC files before using it to size an allocation (np.random.randint(size=(total_samples, channels))). A ~50-byte crafted FLAC file declaring ~100 million samples causes a multi-gigabyte memory allocation, leading to out-of-memory denial of service during 'decrypt --stego-extract'. The issue is fixed in 1.4.9; both the 1.4.x and 1.5.x lines are affected.

Weakness: CWE-789 (Memory Allocation with Excessive Size Value)

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


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

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

## Is CVE-2026-81692 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-81692 is a high-severity denial of service 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-81692 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-81692/ (Markdown: https://insights.sbomify.com/CVE-2026-81692/index.md)
```

## Sources

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

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