openssl_encrypt versions before 1.4.0 expose passwords passed via the --password CLI argument in process listings accessible to all system users. Attackers can read process arguments through ps aux or /proc/[pid]/cmdline to retrieve plaintext passwords and keystore passwords.
CVE-2026-74873
Score 5.5 from GitHub Security Advisory (severity: HIGH) published 2026-08-17. a secondary CVSS source baseline 5.5; 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
- 5.5
- EG Score
- 5.5(high)
- EG Risk
- 40(Track)EG Risk 40/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 computedSeverity55% × 45%Exploitation0% × 40%Automatability100% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- 0%
- EPSS %ILE
- 14%
- KEV
- Not listed
Published
August 17, 2026
Last Modified
August 17, 2026
Advisory Details (2)
Auto-updated Aug 17, 2026openssl_encrypt before 1.4.0 Password Exposure via CLI Argument | Advisories | VulnCheck
https://www.vulncheck.com/advisories/openssl-encrypt-before-password-exposure-via-cli-argumentPassword visible in process list via --password CLI argument · Advisory · jahlives/openssl_encrypt · GitHub
https://github.com/jahlives/openssl_encrypt/security/advisories/GHSA-h3m5-p59h-x88pVendor Advisories for CVE-2026-74873(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Affected Packages
(1 across 1 ecosystem)
PyPI(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| openssl-encrypt | 0.2.2 ... 1.4.0b8 (44 versions) | 1.4.0 | — |
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 16× in last 7d / 16× 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-20 22:56 UTCEPSS rescore
- 2026-08-20 14:15 UTCEG score recompute
- 2026-08-20 14:15 UTCGHSA enrichment
- 2026-08-19 17:04 UTCEPSS rescore
- 2026-08-19 14:34 UTCGHSA enrichment
- 2026-08-18 14:56 UTCEG score recompute
- 2026-08-18 14:56 UTCGHSA enrichment
- 2026-08-18 13:49 UTCEPSS rescore
- 2026-08-18 13:49 UTCEPSS rescore
- 2026-08-17 15:21 UTCEG score recompute
- 2026-08-17 15:21 UTCGHSA enrichment
- 2026-08-17 14:44 UTCEG score recompute
- 2026-08-17 14:44 UTCGHSA enrichment
- 2026-08-17 11:39 UTCEG score recompute
- 2026-08-17 11:13 UTCEG score recompute
- 2026-08-17 11:12 UTCMITRE cvelistV5first tracked
Frequently asked(5)
What is CVE-2026-74873?
When was CVE-2026-74873 disclosed?
Is CVE-2026-74873 actively exploited?
What is the CVSS score of CVE-2026-74873?
How do I remediate CVE-2026-74873?
Dependency Blast Radius
See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-74873
Is Your Infrastructure Affected by CVE-2026-74873?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.