In openssl_encrypt (pip package openssl-encrypt) versions <= 1.4.8, the desktop GUI passes the steganography password to the CLI child process on the command line via the --stego-password argument (on both encrypt and decrypt paths) instead of via an environment variable as done for the main password. Any local user can read the steganography password from /proc//cmdline for the lifetime of the subprocess. Fixed in 1.4.9.
CVE-2026-81684
Score 6.2 from GitHub Security Advisory published 2026-08-27. a secondary CVSS source baseline 6.2; sources differ by 0.0.
- Lower severity and no public exploit yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 6.2
- EG Score
- 6.2(high)
- EG Risk
- 28(Track)EG Risk 28/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 computedSeverity62% × 45%Exploitation0% × 40%Automatability0% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- 0%
- EPSS %ILE
- 2%
- 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 Information Disclosure via Command Line | Advisories | VulnCheck
https://www.vulncheck.com/advisories/openssl-encrypt-before-1.4.9-information-disclosure-via-command-lineDesktop GUI passes the steganography password on the child process command line, exposing it to other local users · Advisory · jahlives/openssl_encrypt · GitHub
https://github.com/jahlives/openssl_encrypt/security/advisories/GHSA-rx2c-m92f-qv6pVendor Advisories for CVE-2026-81684(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 11× in last 7d / 11× 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:53 UTCEG score recompute
- 2026-08-29 19:53 UTCGHSA enrichment
- 2026-08-28 21:42 UTCEPSS rescore
- 2026-08-28 20:43 UTCEG score recompute
- 2026-08-28 20:43 UTCGHSA enrichment
- 2026-08-28 16:49 UTCEG score recompute
- 2026-08-28 16:48 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
Frequently asked(5)
What is CVE-2026-81684?
When was CVE-2026-81684 disclosed?
Is CVE-2026-81684 actively exploited?
What is the CVSS score of CVE-2026-81684?
How do I remediate CVE-2026-81684?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-81684
Is Your Infrastructure Affected by CVE-2026-81684?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.