CVE-2026-51807

CRITICALPre-NVD 9.89.8
EchelonGraph scoreMEDIUM confidence

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

Score 9.8 from GitHub Security Advisory (severity: CRITICAL) published 2026-07-15. CISA-ADP (Vulnrichment) CVSS v3.1 baseline 9.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: CISA-ADP (Vulnrichment) CVSS v3.1, EPSS, GitHub Security Advisory
Trending — 3 sources updated this week
9.8EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines at low or medium mission impact and sooner than that at high (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.7%CVSS: 9.8Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

Heap-based out-of-bounds write in j2k_precinct_subband::parse_packet_header() in OpenHTJ2K versions 0.18.3 and earlier (fixed in v0.18.4) caused by missing bounds validation before coding-pass lengths are written to j2k_codeblock::pass_length[128]. A crafted JPEG 2000 codestream containing malformed PPM packet headers can trigger a heap-based out-of-bounds write in j2k_precinct_subband::parse_packet_header() in source/core/coding/coding_units.cpp due to missing bounds validation for the j2k_codeblock::pass_length[128] array which can lead to heap corruption and process termination.

CVSS v3
9.8
EG Score
9.8CRITICALmedium confidence
EG Risk
59
EG Risk 59/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)
Severity98% × 45%
The EG Score, 9.8 of 10.
Exploitation0.7% × 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 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 at low or medium mission impact and sooner than that at high.
EPSS PROB
0.7%
EPSS %ILE
50th
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 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)3 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 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

July 14, 2026

Last Modified

July 17, 2026

Advisory Details (4)

Auto-updated Oct 10, 2026
Patch available. Sources: github_commit.
Web page

Releases · osamu620/OpenHTJ2K · GitHub

https://github.com/osamu620/OpenHTJ2K/releases
Web page

Comparing 0778b93...v0.18.4 · osamu620/OpenHTJ2K · GitHub

https://github.com/osamu620/OpenHTJ2K/compare/0778b93...v0.18.4
GitHub commit Patch Available

commit 0778b93 (osamu620/OpenHTJ2K)

Patch available: osamu620/OpenHTJ2K v0.18.4 (contains commit 0778b93)

https://github.com/osamu620/OpenHTJ2K/commit/0778b93
Web page

OpenHTJ2K/CHANGELOG at main · osamu620/OpenHTJ2K · GitHub

https://github.com/osamu620/OpenHTJ2K/blob/main/CHANGELOG

Vendor Advisories for CVE-2026-51807(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 16× in last 7d / 45× 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 100 of 371 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. None are among the latest 100 rows. The 271 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-51807?
CVE-2026-51807 is a critical-severity vulnerability; its CVE record was published on July 14, 2026. Heap-based out-of-bounds write in j2kprecinctsubband::parsepacketheader() in OpenHTJ2K versions 0.18.3 and earlier (fixed in v0.18.4) caused by missing bounds validation before coding-pass lengths are written to j2kcodeblock::passlength[128]. A crafted JPEG 2000 codestream containing malformed PPM…
When was the CVE record for CVE-2026-51807 published?
The CVE record for CVE-2026-51807 was published on July 14, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of July 17, 2026; the record at its source may have been updated since.
Is CVE-2026-51807 actively exploited?
CVE-2026-51807 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.7% probability of exploitation in the next 30 days (50th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-51807?
CVE-2026-51807 has a CVSS v3.1 base score of 9.8 (CISA-ADP / Vulnrichment enrichment; NVD's own analysis pending).
How do I remediate CVE-2026-51807?
A fix for CVE-2026-51807 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-51807 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-51807?

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

Book a Demo →Browse All CVEs