CVE-2026-81716

MEDIUMPre-NVD 5.25.2—
EchelonGraph scoreHIGH confidence

Score 5.2 from GitHub Security Advisory (severity: HIGH) published 2026-08-27. a secondary CVSS source baseline 5.2; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 4 sources updated this week
5.2EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 5.2Exploit: None knownExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

openssl_encrypt (pip: openssl-encrypt) versions before 1.4.9 contain a path traversal flaw in PluginSandbox._is_safe_path, which authorized file access using a bare string-prefix match. A sandboxed plugin without the READ_FILES permission could read or write another plugin's directory that merely shares a name prefix (e.g., .../plugins/foobar matching allowed .../plugins/foo), breaking per-plugin isolation within the same user. Fixed by matching each allowed directory exactly or with a trailing path separator.

CVSS v3
5.2
EG Score
5.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 computed
Severity52% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
9%
KEV
Not listed

Published

August 27, 2026

Last Modified

August 28, 2026

Advisory Details (2)

Auto-updated Aug 27, 2026
Patch available. Sources: github.
generic

openssl_encrypt before 1.4.9 Plugin Sandbox Path Traversal | Advisories | VulnCheck

https://www.vulncheck.com/advisories/openssl-encrypt-before-1.4.9-plugin-sandbox-path-traversal
github Patch Available

Plugin sandbox authorizes sibling directories via a bare path prefix (cross-plugin access) · Advisory · jahlives/openssl_encrypt · GitHub

https://github.com/jahlives/openssl_encrypt/security/advisories/GHSA-vr4h-5xqv-xxxf

Vendor Advisories for CVE-2026-81716(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 10× in last 7d / 10× 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.

  1. 2026-08-30 01:22 UTCEPSS rescore
  2. 2026-08-29 18:11 UTCEG score recompute
  3. 2026-08-29 18:10 UTCGHSA enrichment
  4. 2026-08-28 21:42 UTCEPSS rescore
  5. 2026-08-28 19:03 UTCGHSA enrichment
  6. 2026-08-27 20:27 UTCEG score recompute
  7. 2026-08-27 20:27 UTCGHSA enrichment
  8. 2026-08-27 17:24 UTCEG score recompute
  9. 2026-08-27 16:47 UTCEG score recompute
  10. 2026-08-27 16:43 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-81716?
CVE-2026-81716 is a medium vulnerability published on August 27, 2026. opensslencrypt (pip: openssl-encrypt) versions before 1.4.9 contain a path traversal flaw in PluginSandbox.issafepath, which authorized file access using a bare string-prefix match. A sandboxed plugin without the READ_FILES permission could read or write another plugin's directory that merely…
When was CVE-2026-81716 disclosed?
CVE-2026-81716 was first published in the National Vulnerability Database on August 27, 2026, with the most recent update on August 28, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-81716 actively exploited?
CVE-2026-81716 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 91.1% of all scored CVEs.
What is the CVSS score of CVE-2026-81716?
CVE-2026-81716 has a CVSS v3 base score of 5.2 (NVD).
How do I remediate CVE-2026-81716?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-81716, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-81716

Explore →

Is Your Infrastructure Affected by CVE-2026-81716?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs