# CVE-2026-81718: openssl_encrypt before 1.4.9 Weak Cryptographic Parameters

> Attackers can brute-force weak PBKDF2 parameters to decrypt PQC keyfiles and encrypted files, exposing sensitive data.

- **Severity:** High 8.7 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/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:** Not needed
- **Fix available:** No
- **Published:** 27 Aug 2026
- **Updated:** 1 Oct 2026
- **Also known as:** GHSA-8pv3-p4p2-f6pr, GHSA-fmjx-p826-6fvr

## What is CVE-2026-81718?

CVE-2026-81718 is a high-severity 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 versions before 1.4.9 use under-parameterized PBKDF2-HMAC-SHA256 with only 100,000 iterations to protect PQC keyfile private keys and 10,000 iterations for dual-encryption file-password verification. Attackers who obtain keyfiles or encrypted files can brute-force wrapping passwords offline using GPU or ASIC acceleration.

Weakness: CWE-326 (Inadequate Encryption Strength)

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


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

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

## Is CVE-2026-81718 being exploited?

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

## Fix prompt for AI coding agents

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

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

## Sources

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

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