CVE-2026-81715

LOWPre-NVD 3.33.3—
EchelonGraph scoreHIGH confidence

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

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

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

openssl_encrypt (pip package openssl-encrypt) versions <= 1.4.8 do not redact the keyserver bearer token passed as the positional argument to 'keyserver set-token' in the --debug argv dump, because sanitize_argv_for_debug fails to sanitize it. As a result the token is printed in cleartext to stderr under --debug (even without --unsafe-show-secrets), persisting the credential in logs and terminal history. Fixed in 1.4.9.

CVSS v3
3.3
EG Score
3.3(high)
EG Risk
30(Track)
EG Risk 30/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
Severity33% × 45%
Exploitation0% × 40%
Automatability100% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
9%
KEV
Not listed

Published

August 27, 2026

Last Modified

September 3, 2026

References (2)

Vendor Advisories for CVE-2026-81715(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)
PackageVulnerable rangeFixed inDependents
openssl-encrypt0.2.2 ... 1.4.8 (53 versions)1.4.9—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 11× in last 7d / 40× 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-09-18 19:46 UTCEG score recompute
  2. 2026-09-18 19:46 UTCGHSA enrichment
  3. 2026-09-18 19:28 UTCEPSS rescore
  4. 2026-09-16 14:08 UTCEPSS rescore
  5. 2026-09-16 05:15 UTCEPSS rescore
  6. 2026-09-15 18:52 UTCEG score recompute
  7. 2026-09-15 18:52 UTCGHSA enrichment
  8. 2026-09-15 03:12 UTCEPSS rescore
  9. 2026-09-15 03:12 UTCEPSS rescore
  10. 2026-09-12 17:59 UTCEG score recompute
  11. 2026-09-12 17:59 UTCGHSA enrichment
  12. 2026-09-11 14:53 UTCEPSS rescore
  13. 2026-09-11 14:53 UTCEPSS rescore
  14. 2026-09-09 17:05 UTCEG score recompute
  15. 2026-09-09 17:05 UTCGHSA enrichment
  16. 2026-09-08 22:01 UTCEPSS rescore
  17. 2026-09-06 16:12 UTCEG score recompute
  18. 2026-09-06 16:12 UTCGHSA enrichment
  19. 2026-09-06 13:48 UTCEPSS rescore
  20. 2026-09-05 15:31 UTCEPSS rescore
  21. 2026-09-04 05:07 UTCEPSS rescore
  22. 2026-09-03 15:18 UTCEG score recompute
  23. 2026-09-03 15:18 UTCGHSA enrichment
  24. 2026-09-02 14:12 UTCEPSS rescore
  25. 2026-09-01 13:54 UTCEPSS rescore
Show 15 more
  1. 2026-09-01 04:40 UTCEPSS rescore
  2. 2026-09-01 04:40 UTCEPSS rescore
  3. 2026-08-31 20:54 UTCEG score recompute
  4. 2026-08-31 20:54 UTCGHSA enrichment
  5. 2026-08-30 19:18 UTCEPSS rescore
  6. 2026-08-30 19:17 UTCEPSS rescore
  7. 2026-08-30 01:22 UTCEPSS rescore
  8. 2026-08-28 21:42 UTCEPSS rescore
  9. 2026-08-28 20:43 UTCEG score recompute
  10. 2026-08-28 20:43 UTCGHSA enrichment
  11. 2026-08-28 19:48 UTCEG score recompute
  12. 2026-08-28 19:47 UTCGHSA enrichment
  13. 2026-08-27 17:25 UTCEG score recompute
  14. 2026-08-27 16:47 UTCEG score recompute
  15. 2026-08-27 16:43 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-81715?
CVE-2026-81715 is a low vulnerability published on August 27, 2026. opensslencrypt (pip package openssl-encrypt) versions <= 1.4.8 do not redact the keyserver bearer token passed as the positional argument to 'keyserver set-token' in the --debug argv dump, because sanitizeargvfordebug fails to sanitize it. As a result the token is printed in cleartext to stderr…
When was CVE-2026-81715 disclosed?
CVE-2026-81715 was first published in the National Vulnerability Database on August 27, 2026, with the most recent update on September 3, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-81715 actively exploited?
CVE-2026-81715 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.3% of all scored CVEs.
What is the CVSS score of CVE-2026-81715?
CVE-2026-81715 has a CVSS v3 base score of 3.3 (NVD).
How do I remediate CVE-2026-81715?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-81715, 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

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-81715

Explore →

Is Your Infrastructure Affected by CVE-2026-81715?

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

Start Free Scan →Browse All CVEs