CVE-2026-81714

HIGHPre-NVD 7.07.0
EchelonGraph scoreMEDIUM confidence

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

Score 7.0 from GitHub Security Advisory (severity: CRITICAL) published 2026-08-27. The CNA's CVSS baseline 7.0; 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
7.0EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.2%CVSS: 7.0Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

openssl_encrypt (pip: openssl-encrypt) versions <= 1.4.8 use suffix-tolerant fingerprint matching in enroll_trust_key when binding a plugin-signing trust anchor. An operator who confirms a short (forgeable, ~32-bit) GPG key id could unknowingly enroll an attacker's colliding key as a trusted anchor, which then vouches for malicious plugins under the ENFORCE signature policy. Version 1.4.9 fixes this by requiring the confirmed value to exactly match the full primary-key fingerprint (case-insensitive, whitespace-stripped).

CVSS v3
7.0
EG Score
7.0HIGHmedium confidence
EG Risk
32
EG Risk 32/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)
Severity70% × 45%
The EG Score, 7.0 of 10.
Exploitation0.2% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track* at high (mission-essential systems).
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (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.
EPSS PROB
0.2%
EPSS %ILE
8th
KEV
Not listed

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

A fix is available. Apply it within your standard update timelines.

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (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; Fix on system upgrade if it is not.

In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact total (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

Advisory Details (2)

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

openssl_encrypt before 1.4.9 Plugin Signing Trust Anchor Enrollment Bypass | Advisories | VulnCheck

https://www.vulncheck.com/advisories/openssl-encrypt-before-1.4.9-plugin-signing-trust-anchor-enrollment-bypass
GitHub advisoryMentions a patch (unverified)

Plugin-signing trust-anchor enrollment accepts a partial/suffix fingerprint match · Advisory · jahlives/openssl_encrypt · GitHub

https://github.com/jahlives/openssl_encrypt/security/advisories/GHSA-xg52-638v-jc5m

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

Showing the most recent 99 of 165 refreshes on record for this CVE.

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. 1 repeat row among the latest 100 is merged into the row it repeats. The 66 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-10-13 16:35 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  2. 2026-10-13 06:16 UTCEG score recompute
  3. 2026-10-13 06:16 UTCGHSA enrichmentGHSA-xrf2-fg77-9588 · GitHub severity CRITICAL · GitHub CVSS 7.0
  4. 2026-10-12 16:35 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  5. 2026-10-12 14:56 UTCEG score recompute
  6. 2026-10-11 19:20 UTCEG score recompute
  7. 2026-10-11 16:36 UTCEG score recompute
  8. 2026-10-11 13:54 UTCEG score recompute
  9. 2026-10-11 13:49 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  10. 2026-10-10 20:00 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  11. 2026-10-10 15:12 UTCGHSA enrichmentGHSA-xrf2-fg77-9588 · GitHub severity CRITICAL · GitHub CVSS 7.0
  12. 2026-10-10 01:54 UTCEG score recompute
  13. 2026-10-10 01:54 UTCGHSA enrichmentGHSA-xrf2-fg77-9588 · GitHub severity CRITICAL · GitHub CVSS 7.0
  14. 2026-10-09 20:07 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  15. 2026-10-09 03:05 UTCEG score recompute
  16. 2026-10-09 03:05 UTCGHSA enrichmentGHSA-xrf2-fg77-9588 · GitHub severity CRITICAL · GitHub CVSS 7.0
  17. 2026-10-08 17:13 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  18. 2026-10-08 01:19 UTCEG score recompute
  19. 2026-10-08 01:19 UTCGHSA enrichmentGHSA-xrf2-fg77-9588 · GitHub severity CRITICAL · GitHub CVSS 7.0
  20. 2026-10-07 23:48 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  21. 2026-10-07 03:10 UTCEG score recompute
  22. 2026-10-07 03:10 UTCGHSA enrichmentGHSA-xrf2-fg77-9588 · GitHub severity CRITICAL · GitHub CVSS 7.0
  23. 2026-10-06 15:18 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  24. 2026-10-06 14:03 UTCGHSA enrichmentGHSA-xrf2-fg77-9588 · GitHub severity CRITICAL · GitHub CVSS 7.0
  25. 2026-10-06 00:54 UTCEG score recompute
Show 74 more
  1. 2026-10-06 00:53 UTCGHSA enrichmentGHSA-xrf2-fg77-9588 · GitHub severity CRITICAL · GitHub CVSS 7.0
  2. 2026-10-05 17:43 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  3. 2026-10-05 08:47 UTCEG score recompute
  4. 2026-10-05 08:47 UTCGHSA enrichmentGHSA-xrf2-fg77-9588 · GitHub severity CRITICAL · GitHub CVSS 7.0
  5. 2026-10-04 23:22 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  6. 2026-10-04 19:38 UTCGHSA enrichmentGHSA-xrf2-fg77-9588 · GitHub severity CRITICAL · GitHub CVSS 7.0
  7. 2026-10-04 04:22 UTCGHSA enrichmentGHSA-xrf2-fg77-9588 · GitHub severity CRITICAL · GitHub CVSS 7.0
  8. 2026-10-03 15:13 UTCEG score recompute
  9. 2026-10-03 15:13 UTCGHSA enrichmentGHSA-xrf2-fg77-9588 · GitHub severity CRITICAL · GitHub CVSS 7.0
  10. 2026-10-03 14:26 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  11. 2026-10-02 19:26 UTCEG score recompute
  12. 2026-10-02 19:26 UTCGHSA enrichmentGHSA-xrf2-fg77-9588 · GitHub severity CRITICAL · GitHub CVSS 7.0
  13. 2026-10-02 17:57 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  14. 2026-10-02 06:19 UTCEG score recompute
  15. 2026-10-02 06:18 UTCGHSA enrichmentGHSA-xrf2-fg77-9588 · GitHub severity CRITICAL · GitHub CVSS 7.0
  16. 2026-10-01 19:50 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  17. 2026-10-01 15:27 UTCEG score recompute
  18. 2026-10-01 15:27 UTCGHSA enrichmentGHSA-xrf2-fg77-9588 · GitHub severity CRITICAL · GitHub CVSS 7.0
  19. 2026-10-01 09:01 UTCGHSA enrichmentGHSA-xrf2-fg77-9588 · GitHub severity CRITICAL · GitHub CVSS 7.0
  20. 2026-09-30 19:54 UTCEG score recompute
  21. 2026-09-30 19:54 UTCGHSA enrichmentGHSA-xrf2-fg77-9588 · GitHub severity CRITICAL · GitHub CVSS 7.0
  22. 2026-09-30 15:04 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  23. 2026-09-30 05:00 UTCEG score recompute
  24. 2026-09-30 05:00 UTCGHSA enrichmentGHSA-xrf2-fg77-9588 · GitHub severity CRITICAL · GitHub CVSS 7.0
  25. 2026-09-29 12:26 UTCGHSA enrichmentGHSA-xrf2-fg77-9588 · GitHub severity CRITICAL · GitHub CVSS 7.0
  26. 2026-09-28 23:19 UTCEG score recompute
  27. 2026-09-28 23:19 UTCGHSA enrichmentGHSA-xrf2-fg77-9588 · GitHub severity CRITICAL · GitHub CVSS 7.0
  28. 2026-09-28 13:52 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  29. 2026-09-28 10:08 UTCGHSA enrichmentGHSA-xrf2-fg77-9588 · GitHub severity CRITICAL · GitHub CVSS 7.0
  30. 2026-09-27 20:57 UTCEG score recompute
  31. 2026-09-27 20:57 UTCGHSA enrichmentGHSA-xrf2-fg77-9588 · GitHub severity CRITICAL · GitHub CVSS 7.0
  32. 2026-09-27 13:48 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  33. 2026-09-27 07:50 UTCGHSA enrichmentGHSA-xrf2-fg77-9588 · GitHub severity CRITICAL · GitHub CVSS 7.0
  34. 2026-09-26 18:43 UTCEG score recompute
  35. 2026-09-26 18:43 UTCGHSA enrichmentGHSA-xrf2-fg77-9588 · GitHub severity CRITICAL · GitHub CVSS 7.0
  36. 2026-09-26 15:59 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  37. 2026-09-25 13:43 UTCGHSA enrichmentGHSA-xrf2-fg77-9588 · GitHub severity CRITICAL · GitHub CVSS 7.0
  38. 2026-09-25 00:13 UTCEG score recompute
  39. 2026-09-25 00:13 UTCGHSA enrichmentGHSA-xrf2-fg77-9588 · GitHub severity CRITICAL · GitHub CVSS 7.0
  40. 2026-09-24 14:04 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  41. 2026-09-24 10:57 UTCGHSA enrichmentGHSA-xrf2-fg77-9588 · GitHub severity CRITICAL · GitHub CVSS 7.0
  42. 2026-09-23 21:50 UTCEG score recompute
  43. 2026-09-23 21:50 UTCGHSA enrichmentGHSA-xrf2-fg77-9588 · GitHub severity CRITICAL · GitHub CVSS 7.0
  44. 2026-09-23 17:54 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  45. 2026-09-23 08:43 UTCGHSA enrichmentGHSA-xrf2-fg77-9588 · GitHub severity CRITICAL · GitHub CVSS 7.0
  46. 2026-09-22 19:35 UTCEG score recompute
  47. 2026-09-22 19:35 UTCGHSA enrichmentGHSA-xrf2-fg77-9588 · GitHub severity CRITICAL · GitHub CVSS 7.0
  48. 2026-09-22 16:01 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  49. 2026-09-22 06:28 UTCEG score recompute
  50. 2026-09-22 06:28 UTCGHSA enrichmentGHSA-xrf2-fg77-9588 · GitHub severity CRITICAL · GitHub CVSS 7.0
  51. 2026-09-21 21:09 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  52. 2026-09-21 17:20 UTCGHSA enrichmentGHSA-xrf2-fg77-9588 · GitHub severity CRITICAL · GitHub CVSS 7.0
  53. 2026-09-21 04:06 UTCEG score recompute
  54. 2026-09-21 04:06 UTCGHSA enrichmentGHSA-xrf2-fg77-9588 · GitHub severity CRITICAL · GitHub CVSS 7.0
  55. 2026-09-20 20:16 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  56. 2026-09-20 14:59 UTCGHSA enrichmentGHSA-xrf2-fg77-9588 · GitHub severity CRITICAL · GitHub CVSS 7.0
  57. 2026-09-20 01:52 UTCEG score recompute
  58. 2026-09-20 01:52 UTCGHSA enrichmentGHSA-xrf2-fg77-9588 · GitHub severity CRITICAL · GitHub CVSS 7.0
  59. 2026-09-19 12:45 UTCGHSA enrichmentGHSA-xrf2-fg77-9588 · GitHub severity CRITICAL · GitHub CVSS 7.0
  60. 2026-09-18 23:37 UTCEG score recompute
  61. 2026-09-18 23:37 UTCGHSA enrichmentGHSA-xrf2-fg77-9588 · GitHub severity CRITICAL · GitHub CVSS 7.0
  62. 2026-09-18 19:28 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  63. 2026-09-18 10:30 UTCGHSA enrichmentGHSA-xrf2-fg77-9588 · GitHub severity CRITICAL · GitHub CVSS 7.0
  64. 2026-09-17 21:23 UTCEG score recompute
  65. 2026-09-17 21:23 UTCGHSA enrichmentGHSA-xrf2-fg77-9588 · GitHub severity CRITICAL · GitHub CVSS 7.0
  66. 2026-09-17 08:13 UTCGHSA enrichmentGHSA-xrf2-fg77-9588 · GitHub severity CRITICAL · GitHub CVSS 7.0
  67. 2026-09-16 19:04 UTCEG score recompute
  68. 2026-09-16 19:04 UTCGHSA enrichmentGHSA-xrf2-fg77-9588 · GitHub severity CRITICAL · GitHub CVSS 7.0
  69. 2026-09-16 14:08 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  70. 2026-09-16 05:15 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  71. 2026-09-16 03:34 UTCGHSA enrichmentGHSA-xrf2-fg77-9588 · GitHub severity CRITICAL · GitHub CVSS 7.0
  72. 2026-09-15 14:27 UTCEG score recompute
  73. 2026-09-15 14:27 UTCGHSA enrichmentGHSA-xrf2-fg77-9588 · GitHub severity CRITICAL · GitHub CVSS 7.0
  74. 2026-09-15 03:12 UTCEPSS rescoreEPSS 0.1% · 3rd percentile

Related CVEs(same product + same CWE)

Frequently asked(5)

What is CVE-2026-81714?
CVE-2026-81714 is a high-severity vulnerability; its CVE record was published on August 27, 2026. opensslencrypt (pip: openssl-encrypt) versions <= 1.4.8 use suffix-tolerant fingerprint matching in enrolltrust_key when binding a plugin-signing trust anchor. An operator who confirms a short (forgeable, ~32-bit) GPG key id could unknowingly enroll an attacker's colliding key as a trusted anchor,…
When was CVE-2026-81714 made public?
CVE-2026-81714 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-81714 actively exploited?
CVE-2026-81714 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.2% probability of exploitation in the next 30 days (8th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-81714?
CVE-2026-81714 has a CVSS base score of 7.0 (the CNA's own assessment, by vulncheck; NVD's own analysis pending).
How do I remediate CVE-2026-81714?
A fix for CVE-2026-81714 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-81714 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-81714

Explore →

Is Your Infrastructure Affected by CVE-2026-81714?

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

Book a Demo →Browse All CVEs