openssl_encrypt versions before 1.4.9 contain a shell injection vulnerability in the info command's reconstructed CLI block that interpolates untrusted metadata fields without quoting. Attackers can craft metadata values like pepper_name containing shell commands that execute when users copy the printed CLI block into a shell.
CVE-2026-81698
Score 7.5 from GitHub Security Advisory (severity: CRITICAL) published 2026-08-27. a secondary CVSS source baseline 7.5; sources differ by 0.0.
- High severity, but no confirmed exploitation yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 7.5
- EG Score
- 7.5(high)
- EG Risk
- 34(Track)EG Risk 34/100SSVC: Track
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computedSeverity75% × 45%Exploitation0% × 40%Automatability0% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- 0%
- EPSS %ILE
- 21%
- KEV
- Not listed
Published
August 27, 2026
Last Modified
August 28, 2026
Advisory Details (2)
Auto-updated Aug 27, 2026openssl_encrypt before 1.4.9 Shell Injection via info command | Advisories | VulnCheck
https://www.vulncheck.com/advisories/openssl-encrypt-before-1.4.9-shell-injection-via-info-command'info' reconstructed-CLI block interpolates untrusted metadata unquoted (shell injection when pasted) · Advisory · jahlives/openssl_encrypt · GitHub
https://github.com/jahlives/openssl_encrypt/security/advisories/GHSA-gw2m-mj6q-59hcVendor Advisories for CVE-2026-81698(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 14× in last 7d / 14× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
- 2026-08-30 01:22 UTCEPSS rescore
- 2026-08-29 19:18 UTCGHSA enrichment
- 2026-08-29 07:10 UTCEG score recompute
- 2026-08-29 07:09 UTCGHSA enrichment
- 2026-08-28 21:42 UTCEPSS rescore
- 2026-08-28 19:03 UTCGHSA enrichment
- 2026-08-28 08:35 UTCGHSA enrichment
- 2026-08-27 20:27 UTCEG score recompute
- 2026-08-27 20:27 UTCGHSA enrichment
- 2026-08-27 20:17 UTCEG score recompute
- 2026-08-27 20:17 UTCGHSA enrichment
- 2026-08-27 17:25 UTCEG score recompute
- 2026-08-27 16:47 UTCEG score recompute
- 2026-08-27 16:43 UTCMITRE cvelistV5first tracked
Related CVEs(same CWE)
Same CWE
10 shownCWE-78
- CVE-2009-20011EG 10.0CRITICAL
- CVE-2011-10017EG 10.0CRITICAL
- CVE-2012-1166EG 10.0EPSS p91HIGH
- CVE-2012-2976EG 10.0EPSS p92HIGH
- CVE-2012-2953EG 10.0EPSS p99HIGH
- CVE-2011-4502EG 10.0EPSS p92HIGH
- CVE-2011-2148EG 10.0EPSS p92HIGH
- CVE-2011-0382EG 10.0EPSS p90HIGH
- CVE-2011-0381EG 10.0EPSS p92HIGH
- CVE-2011-0372EG 10.0HIGH
Frequently asked(5)
What is CVE-2026-81698?
When was CVE-2026-81698 disclosed?
Is CVE-2026-81698 actively exploited?
What is the CVSS score of CVE-2026-81698?
How do I remediate CVE-2026-81698?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-81698
Is Your Infrastructure Affected by CVE-2026-81698?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.