vulntracker.iovulntracker.io
© 2026 vulntracker.io

CVE-2021-22563

Memory Overread in libjxl

MEDIUM
4.4
CVSS Score
Published: November 1, 2021 at 01:10 PM UTC
Updated: June 17, 2026 at 03:37 AM UTC
1 product affected across 1 vendorLibjxl

Using libjxl by Google LLC?

Get instant alerts when new vulnerabilities affect libjxl - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Start FreeSign In
Severity
MEDIUM4.4
Exploit prediction
EPSS 0.3%

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

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

Libjxl· Libjxl Project
95%
v ≤ 0.6.0v < 0.6.0
Affected range stops below 0.6.0, so it looks safe — our inference, not a vendor statement

Remediation

No guide yet

No remediation guidance has been written for this CVE yet. What the record does show:

Patch and advisory references

References (2)

x_refsource_MISCExploitIssue TrackingPatchThird Party Advisory
Source: [email protected]
https://github.com/libjxl/libjxl/issues/735
x_refsource_MISCPatchThird Party Advisory
Source: [email protected]
https://github.com/libjxl/libjxl/pull/757

CVSS

4.4MEDIUM[email protected]
Attack Vector
LOCAL
Complexity
LOW
Privileges
LOW
User Interaction
NONE
Scope
UNCHANGED
Confidentiality
NONE
Integrity
LOW
Availability
LOW
Vector?

Quick Info

StatusMODIFIED
CWE
CWE-126CWE-125

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Create accountSign in
Free plan, no card