CVE-2026-51807

CRITICALPre-NVD 9.89.8—
EchelonGraph scoreHIGH confidence

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, epss, ghsa
Trending — 3 sources updated this week
9.8EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 9.8Exploit: None knownExposed: 0

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

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.8(high)
EG Risk
59(Track)
EG Risk 59/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
Severity98% × 45%
Exploitation0% × 40%
Automatability100% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
30%
KEV
Not listed

Published

July 14, 2026

Last Modified

July 17, 2026

Advisory Details (4)

Auto-updated Jul 25, 2026
Patch available. Sources: github_commit.
generic

Releases · osamu620/OpenHTJ2K · GitHub

https://github.com/osamu620/OpenHTJ2K/releases
generic

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
generic

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 20× in last 7d / 60× 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.

  1. 2026-07-28 01:25 UTCGHSA enrichment
  2. 2026-07-27 21:18 UTCGHSA enrichment
  3. 2026-07-27 17:10 UTCEG score recompute
  4. 2026-07-27 17:10 UTCGHSA enrichment
  5. 2026-07-27 13:04 UTCGHSA enrichment
  6. 2026-07-27 08:44 UTCGHSA enrichment
  7. 2026-07-27 04:36 UTCGHSA enrichment
  8. 2026-07-27 00:16 UTCGHSA enrichment
  9. 2026-07-26 20:06 UTCGHSA enrichment
  10. 2026-07-26 15:57 UTCEG score recompute
  11. 2026-07-26 15:57 UTCGHSA enrichment
  12. 2026-07-26 14:54 UTCEPSS rescore
  13. 2026-07-26 11:50 UTCEG score recompute
  14. 2026-07-26 11:50 UTCGHSA enrichment
  15. 2026-07-25 14:18 UTCEPSS rescore
  16. 2026-07-24 14:18 UTCEPSS rescore
  17. 2026-07-23 14:18 UTCEPSS rescore
  18. 2026-07-23 03:19 UTCEG score recompute
  19. 2026-07-22 14:08 UTCEPSS rescore
  20. 2026-07-21 15:25 UTCEPSS rescore
  21. 2026-07-20 17:08 UTCEPSS rescore
  22. 2026-07-19 14:31 UTCEPSS rescore
  23. 2026-07-19 14:31 UTCEPSS rescore
  24. 2026-07-19 03:42 UTCEG score recompute
  25. 2026-07-19 03:42 UTCGHSA enrichment
Show 35 more
  1. 2026-07-19 02:29 UTCEPSS rescore
  2. 2026-07-18 10:04 UTCEPSS rescore
  3. 2026-07-17 15:59 UTCGHSA enrichment
  4. 2026-07-17 15:58 UTCGHSA enrichment
  5. 2026-07-17 15:57 UTCGHSA enrichment
  6. 2026-07-17 15:56 UTCGHSA enrichment
  7. 2026-07-17 15:55 UTCGHSA enrichment
  8. 2026-07-17 15:54 UTCGHSA enrichment
  9. 2026-07-17 15:53 UTCGHSA enrichment
  10. 2026-07-17 15:52 UTCGHSA enrichment
  11. 2026-07-17 15:49 UTCGHSA enrichment
  12. 2026-07-17 15:48 UTCGHSA enrichment
  13. 2026-07-17 15:47 UTCGHSA enrichment
  14. 2026-07-17 15:46 UTCGHSA enrichment
  15. 2026-07-17 15:45 UTCGHSA enrichment
  16. 2026-07-17 15:44 UTCGHSA enrichment
  17. 2026-07-17 15:43 UTCGHSA enrichment
  18. 2026-07-17 15:42 UTCGHSA enrichment
  19. 2026-07-17 15:41 UTCGHSA enrichment
  20. 2026-07-17 15:40 UTCGHSA enrichment
  21. 2026-07-17 15:39 UTCGHSA enrichment
  22. 2026-07-17 15:38 UTCGHSA enrichment
  23. 2026-07-17 15:37 UTCGHSA enrichment
  24. 2026-07-17 15:36 UTCGHSA enrichment
  25. 2026-07-17 15:35 UTCGHSA enrichment
  26. 2026-07-17 15:35 UTCGHSA enrichment
  27. 2026-07-17 06:50 UTCEG score recompute▲ 9.80
  28. 2026-07-17 06:50 UTCGHSA enrichment
  29. 2026-07-16 17:03 UTCEPSS rescore
  30. 2026-07-15 16:57 UTCEPSS rescore
  31. 2026-07-15 16:57 UTCEPSS rescore
  32. 2026-07-15 14:49 UTCMITRE cvelistV5CVSS v3 → 9.8 · severity → CRITICAL
  33. 2026-07-14 23:23 UTCNVD update
  34. 2026-07-14 22:46 UTCEG score recompute
  35. 2026-07-14 22:45 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-51807?
CVE-2026-51807 is a critical vulnerability 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 CVE-2026-51807 disclosed?
CVE-2026-51807 was first published in the National Vulnerability Database on July 14, 2026, with the most recent update on July 17, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-51807 actively exploited?
CVE-2026-51807 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 70.3% of all 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?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-51807, 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

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.

Start Free Scan →Browse All CVEs