openssl_encrypt versions before 1.4.0 contain a sandbox bypass vulnerability where the plugin sandbox fails to restrict alternative file access methods like pathlib.Path and io.open. Attackers can import pathlib or io modules to read and write arbitrary files, completely bypassing the restricted_open file access controls.
CVE-2026-74883
Score 8.8 from GitHub Security Advisory (severity: HIGH) published 2026-08-17. a secondary CVSS source baseline 8.8; 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
- 8.8
- EG Score
- 8.8(high)
- EG Risk
- 71(Attend)EG Risk 71/100SSVC: Attend
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 computedSeverity88% × 45%Exploitation40% × 40%Automatability100% × 15%Action: Remediate soon — notable exploitation risk. - EPSS PROB
- 0%
- EPSS %ILE
- 18%
- 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 Sandbox Bypass via pathlib and io | Advisories | VulnCheck
https://www.vulncheck.com/advisories/openssl-encrypt-before-sandbox-bypass-via-pathlib-and-iopathlib.Path and io.open bypass sandbox builtins.open restriction · Advisory · jahlives/openssl_encrypt · GitHub
https://github.com/jahlives/openssl_encrypt/security/advisories/GHSA-mcjj-qw7m-j3cpVendor Advisories for CVE-2026-74883(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 22× in last 7d / 22× 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-21 05:35 UTCEG score recompute
- 2026-08-21 05:35 UTCGHSA enrichment
- 2026-08-20 22:56 UTCEPSS rescore
- 2026-08-20 18:35 UTCGHSA enrichment
- 2026-08-20 07:36 UTCGHSA enrichment
- 2026-08-19 20:36 UTCEG score recompute
- 2026-08-19 20:36 UTCGHSA enrichment
- 2026-08-19 17:04 UTCEPSS rescore
- 2026-08-19 09:35 UTCGHSA enrichment
- 2026-08-18 22:33 UTCEG score recompute
- 2026-08-18 22:33 UTCGHSA enrichment
- 2026-08-18 13:49 UTCEPSS rescore
- 2026-08-18 13:49 UTCEPSS rescore
- 2026-08-18 11:34 UTCGHSA enrichment
- 2026-08-18 00:34 UTCGHSA enrichment
- 2026-08-17 13:30 UTCEG score recompute
- 2026-08-17 13:30 UTCGHSA enrichment
- 2026-08-17 12:56 UTCEG score recompute
- 2026-08-17 12:56 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-74883?
When was CVE-2026-74883 disclosed?
Is CVE-2026-74883 actively exploited?
What is the CVSS score of CVE-2026-74883?
How do I remediate CVE-2026-74883?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-74883
Is Your Infrastructure Affected by CVE-2026-74883?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.