CVE-2026-28386

CRITICALNVD 7.59.1
EchelonGraph scoreMEDIUM confidence

Score 9.1 from GitHub Security Advisory (severity: CRITICAL) published 2026-04-08. NVD baseline CVSS 7.5; sources differ by 1.6.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
9.1EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 7.5Exploit: None knownExposed: 0

A fix is available — apply it.

Issue summary: Applications using AES-CFB128 encryption or decryption on systems with AVX-512 and VAES support can trigger an out-of-bounds read of up to 15 bytes when processing partial cipher blocks.

Impact summary: This out-of-bounds read may trigger a crash which leads to Denial of Service for an application if the input buffer ends at a memory page boundary and the following page is unmapped. There is no information disclosure as the over-read bytes are not written to output.

The vulnerable code path is only reached when processing partial blocks (when a previous call left an incomplete block and the current call provides fewer bytes than needed to complete it). Additionally, the input buffer must be positioned at a page boundary with the following page unmapped. CFB mode is not used in TLS/DTLS protocols, which use CBC, GCM, CCM, or ChaCha20-Poly1305 instead. For these reasons the issue was assessed as Low severity according to our Security Policy.

Only x86-64 systems with AVX-512 and VAES instruction support are affected. Other architectures and systems without VAES support use different code paths that are not affected.

OpenSSL FIPS module in 3.6 version is affected by this issue.

CVSS v3
7.5
EG Score
9.1(medium)
EG Risk
56(Track)
EG Risk 56/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
Severity91% × 45%
Exploitation0% × 40%
Automatability100% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
24%
KEV
Not listed

Published

April 7, 2026

Last Modified

July 24, 2026

Advisory Details (2)

Auto-updated Jun 10, 2026
Upstream fix merged — awaiting tagged release. Sources: github_commit.
github_commit

commit 61f428a2fc66 (openssl/openssl)

Fix landed in openssl/openssl commit 61f428a2fc66 — awaiting tagged release

https://github.com/openssl/openssl/commit/61f428a2fc6671ede184a19f71e6e495f0689621

Vendor Advisories for CVE-2026-28386(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(1)

Vendor / EcosystemFixed in / PatchReleasedSource
redhatopenssl-main-3.5.6-0.1.hum12026-04-09redhat

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(1 across 1 ecosystem)
Debian:14(1)
PackageVulnerable rangeFixed inDependents
openssl3.5.1-1 ... 3.6.1-3 (20 versions)3.6.2-1

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 7× in last 7d / 29× 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.

Showing the most recent 100 of 313 total refreshes for this CVE.

  1. 2026-09-18 19:28 UTCEPSS rescore
  2. 2026-09-18 19:27 UTCEPSS rescore
  3. 2026-09-17 19:30 UTCEPSS rescore
  4. 2026-09-16 14:08 UTCEPSS rescore
  5. 2026-09-16 05:15 UTCEPSS rescore
  6. 2026-09-13 16:47 UTCEPSS rescore
  7. 2026-09-12 15:01 UTCEPSS rescore
  8. 2026-09-11 14:52 UTCEPSS rescore
  9. 2026-09-10 09:34 UTCEPSS rescore
  10. 2026-09-08 22:00 UTCEPSS rescore
  11. 2026-09-06 13:47 UTCEPSS rescore
  12. 2026-09-06 13:47 UTCEPSS rescore
  13. 2026-09-04 05:06 UTCEPSS rescore
  14. 2026-09-02 19:40 UTCOSV refresh
  15. 2026-09-02 14:11 UTCEPSS rescore
  16. 2026-09-01 13:53 UTCEPSS rescore
  17. 2026-09-01 04:39 UTCEPSS rescore
  18. 2026-09-01 04:39 UTCEPSS rescore
  19. 2026-08-30 19:17 UTCEPSS rescore
  20. 2026-08-30 01:22 UTCEPSS rescore
  21. 2026-08-28 21:41 UTCEPSS rescore
  22. 2026-08-27 14:25 UTCEPSS rescore
  23. 2026-08-26 14:46 UTCEPSS rescore
  24. 2026-08-25 13:49 UTCEPSS rescore
  25. 2026-08-24 14:17 UTCEPSS rescore
Show 75 more
  1. 2026-08-23 00:19 UTCEPSS rescore
  2. 2026-08-21 23:49 UTCEPSS rescore
  3. 2026-08-20 22:55 UTCEPSS rescore
  4. 2026-08-20 22:55 UTCEPSS rescore
  5. 2026-08-19 17:03 UTCEPSS rescore
  6. 2026-08-18 13:48 UTCEPSS rescore
  7. 2026-08-17 13:47 UTCEPSS rescore
  8. 2026-08-16 14:56 UTCEPSS rescore
  9. 2026-08-16 11:45 UTCVendor advisory
  10. 2026-08-16 11:45 UTCGHSA enrichment
  11. 2026-08-16 07:54 UTCEG score recompute
  12. 2026-08-16 07:54 UTCVendor advisory
  13. 2026-08-16 07:54 UTCGHSA enrichment
  14. 2026-08-16 02:14 UTCEPSS rescore
  15. 2026-08-15 02:15 UTCEG score recompute
  16. 2026-08-15 02:15 UTCVendor advisory
  17. 2026-08-15 02:15 UTCGHSA enrichment
  18. 2026-08-15 01:30 UTCEPSS rescore
  19. 2026-08-14 22:23 UTCVendor advisory
  20. 2026-08-14 22:23 UTCGHSA enrichment
  21. 2026-08-14 18:31 UTCVendor advisory
  22. 2026-08-14 18:31 UTCGHSA enrichment
  23. 2026-08-14 13:06 UTCVendor advisory
  24. 2026-08-14 13:06 UTCGHSA enrichment
  25. 2026-08-14 09:14 UTCVendor advisory
  26. 2026-08-14 09:14 UTCGHSA enrichment
  27. 2026-08-14 05:22 UTCEG score recompute
  28. 2026-08-14 05:22 UTCVendor advisory
  29. 2026-08-14 05:22 UTCGHSA enrichment
  30. 2026-08-13 22:00 UTCEPSS rescore
  31. 2026-08-13 09:38 UTCVendor advisory
  32. 2026-08-13 09:38 UTCGHSA enrichment
  33. 2026-08-13 03:21 UTCVendor advisory
  34. 2026-08-13 03:21 UTCGHSA enrichment
  35. 2026-08-12 23:29 UTCVendor advisory
  36. 2026-08-12 23:29 UTCGHSA enrichment
  37. 2026-08-12 19:37 UTCEG score recompute
  38. 2026-08-12 19:37 UTCVendor advisory
  39. 2026-08-12 19:37 UTCGHSA enrichment
  40. 2026-08-12 13:50 UTCEPSS rescore
  41. 2026-08-11 23:47 UTCVendor advisory
  42. 2026-08-11 23:47 UTCGHSA enrichment
  43. 2026-08-11 19:49 UTCEG score recompute
  44. 2026-08-11 19:49 UTCVendor advisory
  45. 2026-08-11 19:49 UTCGHSA enrichment
  46. 2026-08-11 13:42 UTCEPSS rescore
  47. 2026-08-11 07:05 UTCVendor advisory
  48. 2026-08-11 07:05 UTCGHSA enrichment
  49. 2026-08-11 03:12 UTCEG score recompute
  50. 2026-08-11 03:12 UTCVendor advisory
  51. 2026-08-11 03:11 UTCGHSA enrichment
  52. 2026-08-11 00:00 UTCEPSS rescore
  53. 2026-08-10 12:11 UTCVendor advisory
  54. 2026-08-10 12:11 UTCGHSA enrichment
  55. 2026-08-10 08:11 UTCVendor advisory
  56. 2026-08-10 08:11 UTCGHSA enrichment
  57. 2026-08-10 04:19 UTCVendor advisory
  58. 2026-08-10 04:19 UTCGHSA enrichment
  59. 2026-08-10 00:27 UTCVendor advisory
  60. 2026-08-10 00:27 UTCGHSA enrichment
  61. 2026-08-09 20:35 UTCVendor advisory
  62. 2026-08-09 20:35 UTCGHSA enrichment
  63. 2026-08-09 16:43 UTCEG score recompute
  64. 2026-08-09 16:43 UTCVendor advisory
  65. 2026-08-09 16:43 UTCGHSA enrichment
  66. 2026-08-09 13:46 UTCEPSS rescore
  67. 2026-08-09 12:50 UTCVendor advisory
  68. 2026-08-09 12:50 UTCGHSA enrichment
  69. 2026-08-09 08:45 UTCVendor advisory
  70. 2026-08-09 08:45 UTCGHSA enrichment
  71. 2026-08-09 04:53 UTCEG score recompute
  72. 2026-08-09 04:53 UTCVendor advisory
  73. 2026-08-09 04:53 UTCGHSA enrichment
  74. 2026-08-08 16:37 UTCEPSS rescore
  75. 2026-08-08 10:24 UTCVendor advisory

Frequently asked(5)

What is CVE-2026-28386?
CVE-2026-28386 is a critical vulnerability published on April 7, 2026. Issue summary: Applications using AES-CFB128 encryption or decryption on systems with AVX-512 and VAES support can trigger an out-of-bounds read of up to 15 bytes when processing partial cipher blocks. Impact summary: This out-of-bounds read may trigger a crash which leads to Denial of Service for…
When was CVE-2026-28386 disclosed?
CVE-2026-28386 was first published in the National Vulnerability Database on April 7, 2026, with the most recent update on July 24, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-28386 actively exploited?
CVE-2026-28386 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 75.6% of all scored CVEs.
What is the CVSS score of CVE-2026-28386?
CVE-2026-28386 has a CVSS v3 base score of 7.5 (NVD). EchelonGraph synthesises NVD + CISA KEV + FIRST EPSS + GHSA into a combined EG score of 9.1.
How do I remediate CVE-2026-28386?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-28386, 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-28386

Explore →

Is Your Infrastructure Affected by CVE-2026-28386?

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