# CVE-2021-22563: Memory Overread in libjxl

> An out-of-bounds read in libjxl when rendering splines can cause crashes or leak memory, requiring an upgrade to fix.

- **Severity:** Medium 4.5 (`CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:L/I:L/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 1 Nov 2021
- **Updated:** 17 Sep 2024
- **Also known as:** GHSA-q2wp-4p9r-fg6g

## What is CVE-2021-22563?

CVE-2021-22563 is a medium-severity memory corruption vulnerability in Google LLC libjxl, published on 1 Nov 2021. It can only be exploited from the same machine or local network, with no action from the victim.

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

Weakness: CWE-125 (Out-of-bounds Read), CWE-126 (Buffer Over-read)

## Which versions are affected by CVE-2021-22563?

It affects 1 product.


Products: Libjxl Project Libjxl.

## How do I fix CVE-2021-22563?

No fix has been published for CVE-2021-22563 yet. Limit exposure of the affected software until one is available.

## Is CVE-2021-22563 being exploited?

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

## Other vulnerabilities in Google LLC 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-2021-22563 and fix it if it is affected.

What it is: CVE-2021-22563 is a medium-severity memory corruption vulnerability in Google LLC libjxl, published on 1 Nov 2021. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2021-22563 in the wild and no public exploit code.

Affected product: Google LLC 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-2021-22563/ (Markdown: https://insights.sbomify.com/CVE-2021-22563/index.md)
```

## Sources

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

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