CVE-2026-81715

LOWPre-NVD 3.33.3
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to the CVSS score beside it.

Score 3.3 from GitHub Security Advisory (severity: HIGH) published 2026-08-27. The CNA's CVSS baseline 3.3; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: the CNA's CVSS, EPSS, GitHub Security Advisory
Trending — 3 sources updated this week
3.3EG
EchelonGraph verdictMonitorRemediate within your standard update timelines at low or medium mission impact and sooner than that at high (the SSVC decision on this page).
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0.3%CVSS: 3.3Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

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.3LOWmedium confidence
EG Risk
30
EG Risk 30/100

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 (value × EchelonGraph’s weight)
Severity33% × 45%
The EG Score, 3.3 of 10.
Exploitation0.3% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability100% × 15%
CISA's SSVC Automatable value: yes (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Attend at high (mission-essential systems).
Exploitation none (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
EPSS PROB
0.3%
EPSS %ILE
16th
KEV
Not listed

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Attend at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.

Exploitation none (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; 60 days if it is not.

In CISA KEV no (CISA's KEV catalog) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

August 27, 2026

Last Modified

October 1, 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 rangeFix by version rangeDependents
openssl-encrypt0.2.2 ... 1.4.8 (53 versions)
  • every version up to 1.4.9: fixed in 1.4.9
—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 12× in last 7d / 47× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. 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. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. 4 repeat rows among the latest 77 are merged into the row they repeat.

  1. 2026-10-11 19:20 UTCEG score recompute
  2. 2026-10-11 16:36 UTCEG score recompute
  3. 2026-10-11 13:54 UTCEG score recompute
  4. 2026-10-11 13:49 UTCEPSS rescoreEPSS 0.3% · 16th percentile
  5. 2026-10-10 20:00 UTCEPSS rescoreEPSS 0.3% · 16th percentile
  6. 2026-10-09 20:07 UTCEPSS rescoreEPSS 0.3% · 16th percentile
  7. 2026-10-08 17:13 UTCEPSS rescoreEPSS 0.3% · 16th percentile
  8. 2026-10-08 01:19 UTCEG score recompute
  9. 2026-10-08 01:19 UTCGHSA enrichmentGHSA-h5x2-vmqf-9934 · GitHub severity HIGH · GitHub CVSS 3.3
  10. 2026-10-07 23:48 UTCEPSS rescoreEPSS 0.3% · 16th percentile
  11. 2026-10-06 15:18 UTCEPSS rescoreEPSS 0.3% · 16th percentile
  12. 2026-10-05 17:43 UTCEPSS rescoreEPSS 0.3% · 16th percentile
  13. 2026-10-04 23:22 UTCEPSS rescoreEPSS 0.3% · 16th percentile
  14. 2026-10-04 16:21 UTCEG score recompute
  15. 2026-10-04 16:21 UTCGHSA enrichmentGHSA-h5x2-vmqf-9934 · GitHub severity HIGH · GitHub CVSS 3.3
  16. 2026-10-03 14:26 UTCEPSS rescoreEPSS 0.3% · 16th percentile
  17. 2026-10-02 17:57 UTCEPSS rescoreEPSS 0.3% · 16th percentile
  18. 2026-10-01 19:50 UTCEPSS rescoreEPSS 0.3% · 16th percentile
  19. 2026-10-01 15:27 UTCEG score recompute
  20. 2026-10-01 15:27 UTCGHSA enrichmentGHSA-h5x2-vmqf-9934 · GitHub severity HIGH · GitHub CVSS 3.3
  21. 2026-10-01 01:00 UTCEG score recompute
  22. 2026-10-01 01:00 UTCGHSA enrichmentGHSA-h5x2-vmqf-9934 · GitHub severity HIGH · GitHub CVSS 3.3
  23. 2026-09-30 15:04 UTCEPSS rescoreEPSS 0.3% · 16th percentile
  24. 2026-09-28 13:52 UTCEPSS rescoreEPSS 0.3% · 16th percentile
  25. 2026-09-27 23:03 UTCEG score recompute
Show 48 more
  1. 2026-09-27 23:03 UTCGHSA enrichmentGHSA-h5x2-vmqf-9934 · GitHub severity HIGH · GitHub CVSS 3.3
  2. 2026-09-27 13:48 UTCEPSS rescoreEPSS 0.3% · 16th percentile
  3. 2026-09-26 15:59 UTCEPSS rescoreEPSS 0.3% · 16th percentile
  4. 2026-09-24 22:09 UTCEG score recompute
  5. 2026-09-24 22:09 UTCGHSA enrichmentGHSA-h5x2-vmqf-9934 · GitHub severity HIGH · GitHub CVSS 3.3
  6. 2026-09-24 14:04 UTCEPSS rescoreEPSS 0.3% · 15th percentile
  7. 2026-09-23 17:54 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  8. 2026-09-22 16:01 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  9. 2026-09-21 21:09 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  10. 2026-09-21 20:40 UTCEG score recompute
  11. 2026-09-21 20:40 UTCGHSA enrichmentGHSA-h5x2-vmqf-9934 · GitHub severity HIGH · GitHub CVSS 3.3
  12. 2026-09-20 20:16 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  13. 2026-09-18 19:46 UTCEG score recompute
  14. 2026-09-18 19:46 UTCGHSA enrichmentGHSA-h5x2-vmqf-9934 · GitHub severity HIGH · GitHub CVSS 3.3
  15. 2026-09-18 19:28 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  16. 2026-09-16 14:08 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  17. 2026-09-16 05:15 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  18. 2026-09-15 18:52 UTCEG score recompute
  19. 2026-09-15 18:52 UTCGHSA enrichmentGHSA-h5x2-vmqf-9934 · GitHub severity HIGH · GitHub CVSS 3.3
  20. 2026-09-15 03:12 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  21. 2026-09-12 17:59 UTCEG score recompute
  22. 2026-09-12 17:59 UTCGHSA enrichmentGHSA-h5x2-vmqf-9934 · GitHub severity HIGH · GitHub CVSS 3.3
  23. 2026-09-11 14:53 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  24. 2026-09-09 17:05 UTCEG score recompute
  25. 2026-09-09 17:05 UTCGHSA enrichmentGHSA-h5x2-vmqf-9934 · GitHub severity HIGH · GitHub CVSS 3.3
  26. 2026-09-08 22:01 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  27. 2026-09-06 16:12 UTCEG score recompute
  28. 2026-09-06 16:12 UTCGHSA enrichmentGHSA-h5x2-vmqf-9934 · GitHub severity HIGH · GitHub CVSS 3.3
  29. 2026-09-06 13:48 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  30. 2026-09-05 15:31 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  31. 2026-09-04 05:07 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  32. 2026-09-03 15:18 UTCEG score recompute
  33. 2026-09-03 15:18 UTCGHSA enrichmentGHSA-h5x2-vmqf-9934 · GitHub severity HIGH · GitHub CVSS 3.3
  34. 2026-09-02 14:12 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  35. 2026-09-01 13:54 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  36. 2026-09-01 04:40 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  37. 2026-08-31 20:54 UTCEG score recompute
  38. 2026-08-31 20:54 UTCGHSA enrichmentGHSA-h5x2-vmqf-9934 · GitHub severity HIGH · GitHub CVSS 3.3
  39. 2026-08-30 19:17 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  40. 2026-08-30 01:22 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  41. 2026-08-28 21:42 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  42. 2026-08-28 20:43 UTCEG score recompute
  43. 2026-08-28 20:43 UTCGHSA enrichmentGHSA-h5x2-vmqf-9934 · GitHub severity HIGH · GitHub CVSS 3.3
  44. 2026-08-28 19:48 UTCEG score recompute
  45. 2026-08-28 19:47 UTCGHSA enrichmentGHSA-h5x2-vmqf-9934 · GitHub severity HIGH · GitHub CVSS 3.3
  46. 2026-08-27 17:25 UTCEG score recompute
  47. 2026-08-27 16:47 UTCEG score recomputeFirst assessed: 3.3 LOW
  48. 2026-08-27 16:43 UTCMITRE cvelistV5first tracked

Related CVEs(same product + same CWE)

Frequently asked(5)

What is CVE-2026-81715?
CVE-2026-81715 is a low-severity vulnerability; its CVE record was 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 made public?
CVE-2026-81715 was made public on August 12, 2026: that is the date its CVE record's CNA, VulnCheck, gives for when the vulnerability was made public. The CVE record itself was published on August 27, 2026. EchelonGraph's copy of the record carries a last-modified date of October 1, 2026; the record at its source may have been updated since.
Is CVE-2026-81715 actively exploited?
CVE-2026-81715 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.3% probability of exploitation in the next 30 days (16th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-81715?
CVE-2026-81715 has a CVSS base score of 3.3 (the CNA's own assessment, by vulncheck; NVD's own analysis pending).
How do I remediate CVE-2026-81715?
A fix for CVE-2026-81715 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-81715 are linked in the Vendor Advisories panel on this page.

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.

Book a Demo →Browse All CVEs