CVE-2026-81687

MEDIUMPre-NVD 5.55.5
EchelonGraph scoreMEDIUM confidence

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

Score 5.5 from GitHub Security Advisory (severity: HIGH) published 2026-08-27. The CNA's CVSS baseline 5.5; 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
5.5EG
EchelonGraph verdictMonitorRemediate within your standard update timelines (the SSVC decision on this page).
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0.3%CVSS: 5.5Exploit: None knownExposed services: Not assessed

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

The CVE record's CNA (VulnCheck) lists jahlives openssl_encrypt versions before 1.4.9 as affected, and jahlives openssl_encrypt versions 1.4.9 as unaffected. No release containing a fix is confirmed on record.

openssl_encrypt versions before 1.4.9 fail to enforce a time ceiling on key derivation function iteration counts specified in file metadata. Attackers can craft files with extremely high KDF iteration counts to consume CPU resources for unbounded periods before password verification occurs.

CVSS v3
5.5
EG Score
5.5MEDIUMmedium confidence
EG Risk
25
EG Risk 25/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)
Severity55% × 45%
The EG Score, 5.5 of 10.
Exploitation0.3% × 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 every mission impact level.
Exploitation none (CISA Vulnrichment) · Automatable no (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: No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines, and watch the vendor's advisory for the fix.
EPSS PROB
0.3%
EPSS %ILE
20th
KEV
Not listed

SSVC (CISA's decision table, applied by EchelonGraph)Track at every mission impact level.

No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines, and watch the vendor's advisory for the fix.

Exploitation none (CISA Vulnrichment) · Automatable no (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)60 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 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

Advisory Details (2)

Auto-updated Aug 27, 2026
No fix on record yet. Sources: github.
Web page

openssl_encrypt before 1.4.9 Denial of Service via KDF | Advisories | VulnCheck

https://www.vulncheck.com/advisories/openssl-encrypt-before-1.4.9-denial-of-service-via-kdf
GitHub advisoryMentions a patch (unverified)

Decrypt gates KDF memory but not time, so crafted iteration counts wedge the CPU before authentication · Advisory · jahlives/openssl_encrypt · GitHub

https://github.com/jahlives/openssl_encrypt/security/advisories/GHSA-rv6w-7hq9-pr74

Vendor Advisories for CVE-2026-81687(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 17× in last 7d / 81× 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 98 of 135 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. 2 repeat rows among the latest 100 are merged into the row they repeat. The 37 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.3% · 20th percentile
  2. 2026-10-12 16:35 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  3. 2026-10-12 14:56 UTCEG score recompute
  4. 2026-10-11 19:20 UTCEG score recompute
  5. 2026-10-11 16:36 UTCEG score recompute
  6. 2026-10-11 13:54 UTCEG score recompute
  7. 2026-10-11 13:49 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  8. 2026-10-10 20:00 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  9. 2026-10-10 05:58 UTCEG score recompute
  10. 2026-10-10 05:58 UTCGHSA enrichmentGHSA-fj6q-w4r8-75h7 · GitHub severity HIGH · GitHub CVSS 5.5
  11. 2026-10-09 20:07 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  12. 2026-10-09 07:16 UTCEG score recompute
  13. 2026-10-09 07:16 UTCGHSA enrichmentGHSA-fj6q-w4r8-75h7 · GitHub severity HIGH · GitHub CVSS 5.5
  14. 2026-10-08 17:13 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  15. 2026-10-08 08:28 UTCEG score recompute
  16. 2026-10-08 08:28 UTCGHSA enrichmentGHSA-fj6q-w4r8-75h7 · GitHub severity HIGH · GitHub CVSS 5.5
  17. 2026-10-07 23:48 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  18. 2026-10-07 09:53 UTCEG score recompute
  19. 2026-10-07 09:53 UTCGHSA enrichmentGHSA-fj6q-w4r8-75h7 · GitHub severity HIGH · GitHub CVSS 5.5
  20. 2026-10-06 15:18 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  21. 2026-10-06 11:10 UTCEG score recompute
  22. 2026-10-06 11:10 UTCGHSA enrichmentGHSA-fj6q-w4r8-75h7 · GitHub severity HIGH · GitHub CVSS 5.5
  23. 2026-10-05 17:43 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  24. 2026-10-05 12:25 UTCEG score recompute
  25. 2026-10-05 12:25 UTCGHSA enrichmentGHSA-fj6q-w4r8-75h7 · GitHub severity HIGH · GitHub CVSS 5.5
Show 73 more
  1. 2026-10-04 23:22 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  2. 2026-10-04 13:49 UTCGHSA enrichmentGHSA-fj6q-w4r8-75h7 · GitHub severity HIGH · GitHub CVSS 5.5
  3. 2026-10-03 15:13 UTCEG score recompute
  4. 2026-10-03 15:13 UTCGHSA enrichmentGHSA-fj6q-w4r8-75h7 · GitHub severity HIGH · GitHub CVSS 5.5
  5. 2026-10-03 14:26 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  6. 2026-10-02 17:57 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  7. 2026-10-02 14:03 UTCEG score recompute
  8. 2026-10-02 14:03 UTCGHSA enrichmentGHSA-fj6q-w4r8-75h7 · GitHub severity HIGH · GitHub CVSS 5.5
  9. 2026-10-01 19:50 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  10. 2026-10-01 15:28 UTCEG score recompute
  11. 2026-10-01 15:28 UTCGHSA enrichmentGHSA-fj6q-w4r8-75h7 · GitHub severity HIGH · GitHub CVSS 5.5
  12. 2026-09-30 19:55 UTCEG score recompute
  13. 2026-09-30 19:55 UTCGHSA enrichmentGHSA-fj6q-w4r8-75h7 · GitHub severity HIGH · GitHub CVSS 5.5
  14. 2026-09-30 15:04 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  15. 2026-09-29 14:34 UTCEG score recompute
  16. 2026-09-29 14:34 UTCGHSA enrichmentGHSA-fj6q-w4r8-75h7 · GitHub severity HIGH · GitHub CVSS 5.5
  17. 2026-09-28 15:59 UTCEG score recompute
  18. 2026-09-28 15:59 UTCGHSA enrichmentGHSA-fj6q-w4r8-75h7 · GitHub severity HIGH · GitHub CVSS 5.5
  19. 2026-09-28 13:52 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  20. 2026-09-27 17:23 UTCEG score recompute
  21. 2026-09-27 17:23 UTCGHSA enrichmentGHSA-fj6q-w4r8-75h7 · GitHub severity HIGH · GitHub CVSS 5.5
  22. 2026-09-27 13:48 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  23. 2026-09-26 18:44 UTCEG score recompute
  24. 2026-09-26 18:44 UTCGHSA enrichmentGHSA-fj6q-w4r8-75h7 · GitHub severity HIGH · GitHub CVSS 5.5
  25. 2026-09-26 15:59 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  26. 2026-09-25 14:39 UTCGHSA enrichmentGHSA-fj6q-w4r8-75h7 · GitHub severity HIGH · GitHub CVSS 5.5
  27. 2026-09-24 16:01 UTCEG score recompute
  28. 2026-09-24 16:01 UTCGHSA enrichmentGHSA-fj6q-w4r8-75h7 · GitHub severity HIGH · GitHub CVSS 5.5
  29. 2026-09-24 14:04 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  30. 2026-09-23 17:54 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  31. 2026-09-23 17:25 UTCGHSA enrichmentGHSA-fj6q-w4r8-75h7 · GitHub severity HIGH · GitHub CVSS 5.5
  32. 2026-09-23 12:38 UTCEG score recompute
  33. 2026-09-23 12:38 UTCGHSA enrichmentGHSA-fj6q-w4r8-75h7 · GitHub severity HIGH · GitHub CVSS 5.5
  34. 2026-09-22 16:01 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  35. 2026-09-22 14:03 UTCEG score recompute
  36. 2026-09-22 14:02 UTCGHSA enrichmentGHSA-fj6q-w4r8-75h7 · GitHub severity HIGH · GitHub CVSS 5.5
  37. 2026-09-21 21:09 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  38. 2026-09-21 15:27 UTCEG score recompute
  39. 2026-09-21 15:27 UTCGHSA enrichmentGHSA-fj6q-w4r8-75h7 · GitHub severity HIGH · GitHub CVSS 5.5
  40. 2026-09-20 20:16 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  41. 2026-09-20 16:51 UTCGHSA enrichmentGHSA-fj6q-w4r8-75h7 · GitHub severity HIGH · GitHub CVSS 5.5
  42. 2026-09-19 18:13 UTCEG score recompute
  43. 2026-09-19 18:13 UTCGHSA enrichmentGHSA-fj6q-w4r8-75h7 · GitHub severity HIGH · GitHub CVSS 5.5
  44. 2026-09-18 19:31 UTCEG score recompute
  45. 2026-09-18 19:31 UTCGHSA enrichmentGHSA-fj6q-w4r8-75h7 · GitHub severity HIGH · GitHub CVSS 5.5
  46. 2026-09-18 19:28 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  47. 2026-09-17 20:55 UTCEG score recompute
  48. 2026-09-17 20:55 UTCGHSA enrichmentGHSA-fj6q-w4r8-75h7 · GitHub severity HIGH · GitHub CVSS 5.5
  49. 2026-09-16 19:04 UTCEG score recompute
  50. 2026-09-16 19:04 UTCGHSA enrichmentGHSA-fj6q-w4r8-75h7 · GitHub severity HIGH · GitHub CVSS 5.5
  51. 2026-09-16 14:08 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  52. 2026-09-16 05:15 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  53. 2026-09-15 18:29 UTCEG score recompute
  54. 2026-09-15 18:29 UTCGHSA enrichmentGHSA-fj6q-w4r8-75h7 · GitHub severity HIGH · GitHub CVSS 5.5
  55. 2026-09-15 03:12 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  56. 2026-09-14 19:48 UTCGHSA enrichmentGHSA-fj6q-w4r8-75h7 · GitHub severity HIGH · GitHub CVSS 5.5
  57. 2026-09-13 21:13 UTCEG score recompute
  58. 2026-09-13 21:13 UTCGHSA enrichmentGHSA-fj6q-w4r8-75h7 · GitHub severity HIGH · GitHub CVSS 5.5
  59. 2026-09-12 22:38 UTCEG score recompute
  60. 2026-09-12 22:38 UTCGHSA enrichmentGHSA-fj6q-w4r8-75h7 · GitHub severity HIGH · GitHub CVSS 5.5
  61. 2026-09-12 00:02 UTCEG score recompute
  62. 2026-09-12 00:02 UTCGHSA enrichmentGHSA-fj6q-w4r8-75h7 · GitHub severity HIGH · GitHub CVSS 5.5
  63. 2026-09-11 14:53 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  64. 2026-09-11 01:26 UTCEG score recompute
  65. 2026-09-11 01:26 UTCGHSA enrichmentGHSA-fj6q-w4r8-75h7 · GitHub severity HIGH · GitHub CVSS 5.5
  66. 2026-09-10 02:50 UTCGHSA enrichmentGHSA-fj6q-w4r8-75h7 · GitHub severity HIGH · GitHub CVSS 5.5
  67. 2026-09-09 04:14 UTCEG score recompute
  68. 2026-09-09 04:14 UTCGHSA enrichmentGHSA-fj6q-w4r8-75h7 · GitHub severity HIGH · GitHub CVSS 5.5
  69. 2026-09-08 22:01 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  70. 2026-09-08 05:38 UTCEG score recompute
  71. 2026-09-08 05:37 UTCGHSA enrichmentGHSA-fj6q-w4r8-75h7 · GitHub severity HIGH · GitHub CVSS 5.5
  72. 2026-09-07 06:57 UTCEG score recompute
  73. 2026-09-07 06:57 UTCGHSA enrichmentGHSA-fj6q-w4r8-75h7 · GitHub severity HIGH · GitHub CVSS 5.5

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-81687?
CVE-2026-81687 is a medium-severity vulnerability; its CVE record was published on August 27, 2026. openssl_encrypt versions before 1.4.9 fail to enforce a time ceiling on key derivation function iteration counts specified in file metadata. Attackers can craft files with extremely high KDF iteration counts to consume CPU resources for unbounded periods before password verification occurs.
When was CVE-2026-81687 made public?
CVE-2026-81687 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-81687 actively exploited?
CVE-2026-81687 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.3% probability of exploitation in the next 30 days (20th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-81687?
CVE-2026-81687 has a CVSS base score of 5.5 (the CNA's own assessment, by vulncheck; NVD's own analysis pending).
How do I remediate CVE-2026-81687?
No fix for CVE-2026-81687 is confirmed yet. Until one is published, restrict network exposure of the affected system or apply the vendor's mitigation — for example, keep it off the internet or limit it to trusted networks — and watch the vendor's advisory for the fix. The CVE record's CNA (VulnCheck) lists jahlives openssl_encrypt versions before 1.4.9 as affected, and jahlives openssl_encrypt versions 1.4.9 as unaffected. No release containing a fix is confirmed on record. The vendor advisories EchelonGraph has for CVE-2026-81687 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-81687?

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

Book a Demo →Browse All CVEs