Vulnerability in openssl_encrypt (CVE-2026-81692)
Summary
Vulnerability in openssl_encrypt (CVE-2026-81692). Risk of unauthorized operations or information disclosure. Mitigation: upgrade to 1.4.9 or later.
Original description
The description as published by the source.
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.
Source: NIST National Vulnerability Database NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-81692 has been found in openssl_encrypt.
Risk of unauthorized operations or information disclosure. CVSS score: 7.5/10.
What to do: upgrade openssl_encrypt to 1.4.9 or later.
If unsure, ask your IT team or search "openssl_encrypt CVE-2026-81692" on the vendor's site.
CVE-2026-81692 (openssl_encrypt) — CWE-789 / CVSS v3 7.5
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Patched: 1.4.9 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
A vulnerability (CWE-789) exists in openssl_encrypt.
Check the vendor advisory for the affected versions of openssl_encrypt.
Severity: High (CVSS 7.5/10). Risk of unauthorized operations or information disclosure.
Update to 1.4.9.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'openssl_encrypt' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'openssl_encrypt' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
openssl_encryptを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade openssl_encrypt to 1.4.9ステージング環境で 1.4.9 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
References
- web disclosure@vulncheck.com
- web disclosure@vulncheck.com
- web nvd.nist.gov
- web github.com