# CVE-2023-0645: Out of Bounds read in libjxl

> An attacker can cause an out-of-bounds read in libjxl via a crafted file, potentially leading to crashes or information disclosure.

- **Severity:** Medium 5.3 (`CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 11 Apr 2023
- **Updated:** 29 Jun 2026
- **Also known as:** DEBIAN-CVE-2023-0645, GHSA-378h-jm2h-7wrm, UBUNTU-CVE-2023-0645

## What is CVE-2023-0645?

CVE-2023-0645 is a medium-severity memory corruption vulnerability in Libjxl, published on 11 Apr 2023. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

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

Weakness: CWE-125 (Out-of-bounds Read)

## Which versions are affected by CVE-2023-0645?

It affects 1 product.


Products: Libjxl Project Libjxl.

## How do I fix CVE-2023-0645?

Upgrade to a fixed version.

## Is CVE-2023-0645 being exploited?

There is no known exploitation of CVE-2023-0645 in the wild and no public exploit code.

## Other vulnerabilities in Libjxl

- [CVE-2021-27804](https://insights.sbomify.com/CVE-2021-27804/): Memory corruption in n/a (critical 9.8)
- [CVE-2026-1837](https://insights.sbomify.com/CVE-2026-1837/): libjxl: Out-of-bounds write in grayscale color transformation when using LCMS2 (high 8.7)
- [CVE-2023-35790](https://insights.sbomify.com/CVE-2023-35790/): Integer overflow in n/a (high 7.5)
- [CVE-2021-36691](https://insights.sbomify.com/CVE-2021-36691/): Denial of service in n/a (high 7.5)
- [CVE-2024-11403](https://insights.sbomify.com/CVE-2024-11403/): Out of Bounds Memory Read/Write in libjxl (medium 6.9)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2023-0645 and fix it if it is affected.

What it is: CVE-2023-0645 is a medium-severity memory corruption vulnerability in Libjxl, published on 11 Apr 2023. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2023-0645 in the wild and no public exploit code.

Affected product: Libjxl. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2023-0645/ (Markdown: https://insights.sbomify.com/CVE-2023-0645/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2023-0645
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2023-0645
- OSV: https://osv.dev/vulnerability/CVE-2023-0645

---
From sbomify Insights: https://insights.sbomify.com/CVE-2023-0645/
Summaries are generated and may contain mistakes; the official description above is the record.