CVE-2023-0645

CRITICALNVD 9.19.1
EchelonGraph scoreMEDIUM confidence

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

Score 9.1 from GitHub Security Advisory (severity: CRITICAL) published 2023-07-06. NVD baseline CVSS 9.1; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, NVD CVSS v3

Also known asEUVD-2023-12679 (ENISA EUVD) · GHSA-378h-jm2h-7wrm (GitHub Security Advisories)Source: ENISA EUVD

9.1EG
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.9%CVSS: 9.1Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

An out of bounds read exists in libjxl. An attacker using a specifically crafted file could cause an out of bounds read in the exif handler. We recommend upgrading to version 0.8.1 or past commit  https://github.com/libjxl/libjxl/pull/2101/commits/d95b050c1822a5b1ede9e0dc937e43fca1b10159 https://github.com/libjxl/libjxl/pull/2101/commits/d95b050c1822a5b1ede9e0dc937e43fca1b10159

CVSS v3
9.1
EG Score
9.1CRITICALmedium confidence
EG Risk
41
EG Risk 41/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity91% × 45%
Impact severity (EG Severity): CVSS 9.1 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.9% × 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: A fix is available. Apply it within your standard update timelines.
EPSS PROB
0.9%
EPSS %ILE
58th
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (9.1): severity, escalated by confirmed exploitation. This CVE's 9.1 is its impact severity (EG Severity), not escalated.

EG Severity
9.1 CRITICALCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
0.9% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-11-12). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at every mission impact level.CISA BOD 26-04: 60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

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

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

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.

The score's inputs: 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

April 11, 2023

Last Modified

June 29, 2026

Advisory Details (3)

Auto-updated Sep 16, 2026
Patch available. Sources: github_pr.
GitHub pull request

Update exif.h

Fix merged in libjxl/libjxl PR #2101 on 2023-02-01 — awaiting tagged release

https://github.com/libjxl/libjxl/pull/2101/commits/d95b050c1822a5b1ede9e0dc937e43fca1b10159
GitHub pull request

Update exif.h

Fix merged in libjxl/libjxl PR #2101 on 2023-02-01 — awaiting tagged release

https://github.com/libjxl/libjxl/pull/2101
Web page

oss-security - CVE-2023-0645: libjxl/cjxl out-of-bounds read in EXIF metadata parsing

http://www.openwall.com/lists/oss-security/2026/06/29/3

Vendor Advisories for CVE-2023-0645(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 / EcosystemFix (by version range) / PatchReleasedSource
ubuntulibjxl0.7 (0.7.0-10.2ubuntu6.1) @ noble2026-11-12ubuntu

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

(3 across 3 ecosystems)
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
jpeg-xl0.7.0-10
  • every version up to 0.7.0-10+deb12u1: fixed in 0.7.0-10+deb12u1
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
jpeg-xl—
  • every version up to 0.8.2-4: fixed in 0.8.2-4
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
jpeg-xl—
  • every version up to 0.8.2-4: fixed in 0.8.2-4
—

Weakness Classification(1)

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

All Vendor Advisories

(1)

Every vendor that published an advisory referencing this CVE — pulled from our cve_vendor_advisories aggregation. Click any row for the vendor's original advisory page.

Data Freshness Timeline

(refreshed 15× in last 7d / 76× 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 its CVE.org record (CNA or CISA ADP). 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). "EchelonGraph re-scored" is our own recompute of this CVE's score, not an update from a source, and is not counted in the refreshes above. Most recent first.

Showing the most recent 100 of 292 rows 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 192 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Related CVEs(same product + same vendor + same CWE)

Frequently asked(5)

What is CVE-2023-0645?
CVE-2023-0645 is a critical-severity vulnerability; its CVE record was published on April 11, 2023. An out of bounds read exists in libjxl. An attacker using a specifically crafted file could cause an out of bounds read in the exif handler. We recommend upgrading to version 0.8.1 or past commit https://github.com/libjxl/libjxl/pull/2101/commits/d95b050c1822a5b1ede9e0dc937e43fca1b10159…
When was CVE-2023-0645 made public?
CVE-2023-0645 was made public on January 31, 2023: that is the date its CVE record's CNA, Google LLC, gives for when the vulnerability was made public. The CVE record itself was published on April 11, 2023. EchelonGraph's copy of the record carries a last-modified date of June 29, 2026; the record at its source may have been updated since.
Is CVE-2023-0645 actively exploited?
CVE-2023-0645 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.9% probability of exploitation in the next 30 days (58th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2023-0645?
CVE-2023-0645 has a CVSS v3 base score of 9.1 (NVD).
How do I remediate CVE-2023-0645?
A fix for CVE-2023-0645 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2023-0645 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-2023-0645

Explore →

Is Your Infrastructure Affected by CVE-2023-0645?

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

Book a Demo →Browse All CVEs