Memory Overread in libjxl

published 2021-11-01 5 y ago modified 2026-06-17 4 mo ago also EUVD-2021-9703

cvss: 4.5; version 3.1, CNA
cisa kev: Not listed; not in CISA's catalog
epss: 0.3%; EPSS 0.3% chance of exploitation in 30 days, percentile 24%
public exploits: 0; none known

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

Patch / fix

fixed in 1 distros 1 links 2

libjxl_project libjxl 0.6.0

libjxl Arch Linux 0.6.1-1

arch linux advisories AVG-2508

github.com/libjxl/libjxl#757 pull request
github.com/libjxl/libjxl/issues/735 advisory

Exploit prediction

0.31% chance of exploitation in the next 30 days, higher than 24% of all scored CVEs (FIRST EPSS, 2026-11-08).

Exploits and checks

github.com https://github.com/libjxl/libjxl/issues/735 referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

assigned by	version	score	vector
CNA	3.1	4.5	CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:L/I:L/A:L
NVD	3.1	4.4	CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:L
NVD	2.0	3.6	AV:L/AC:L/Au:N/C:N/I:P/A:P

Affected products

Google LLC libjxl

Classification

Weakness

CWE-126 Buffer Over-read
CWE-125 Out-of-bounds Read

References

github.com /libjxl/libjxl/pull/757
patch, third-party-advisory
github.com /libjxl/libjxl/issues/735
exploit, issue-tracking, patch, third-party-advisory

Sources

CVE List CVE-2021-22563
NVD CVE-2021-22563

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.

Summary