GHSA-66m8-c62j-h6v5: jxl-oxide `FrameBuffer::new` Creates Out-of-bounds Slices On Vulnerability

MODERATE
Share
CVSS 6.2
CWE-190 CWE-131
Published
Advisory Summary

GHSA-66m8-c62j-h6v5 is a MODERATE (CVSS 6.2) `framebuffer::new` creates out-of-bounds slices on vulnerability (CWE-190: Integer Overflow or Wraparound) affecting jxl-oxide libraries in the crates.io ecosystem. The issue involves `framebuffer::new` creates out-of-bounds slices on overflow. Remediation is available by upgrading affected packages to version 0.12.6.

GHSA-66m8-c62j-h6v5 at a Glance

CVE Identifier N/A
GHSA Identifier GHSA-66m8-c62j-h6v5
Severity MODERATE
CVSS v3.1 Base Score 6.2
CWE Classification CWE-190: Integer Overflow or Wraparound
Affected Product jxl-oxide
Package Ecosystem crates.io
Published Date
Last Updated

Security Impact

CVSS: 6.2

The security impact metrics below are parsed directly from the CVSS v3.1 vector string (CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H).

Attack Vector Local (AV:L)
Attack Complexity Low (AC:L)
Privileges Required None (PR:N)
User Interaction None (UI:N)
Scope Unchanged (S:U)
Confidentiality None (C:N)
Integrity None (I:N)
Availability High (A:H)

How to Fix GHSA-66m8-c62j-h6v5

To remediate this vulnerability, upgrade all affected jxl-oxide dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.

jxl-oxide fixed: 0.12.6 
Upgrade jxl-oxide to 0.12.6
Verify Direct and Transitive Dependencies

Run the following command in your project directory to verify that all resolved dependencies use the patched release: 

inspect dependencies for jxl-oxide

How to Check if You Are Affected

To determine whether your application is affected by GHSA-66m8-c62j-h6v5, inspect your project dependencies for jxl-oxide:

inspect dependencies for jxl-oxide

Analyze the terminal output to locate any version of jxl-oxide in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 0.12.6), your application is affected.

Note: Verify declared build manifests and deployed runtime container environments.

Technical Details

Vulnerability Mechanism & Technical Analysis

This vulnerability is classified under CWE-190: Integer Overflow or Wraparound, where the product performs a calculation that can produce an integer overflow or wraparound when the logic assumes that the resulting value will always be larger than the original value. this occurs when an integer value is incremented to a value that is too large to store in the associated representation. when this occurs, the value may become a very small or negative number. In jxl-oxide, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.

Source Advisory Statement

### Summary `jxl-oxide` exposes a public safe API that can construct an undersized `FrameBuffer` due to unchecked `usize` multiplication, which immediately trigger panic while initializing the buffer in normal decoding path. Additionally, calling the safe grouped buffer accessors afterward can create invalid oversized slices from a much smaller allocation, causing undefined behavior; however normal decoding path never reaches UB, because these methods are never used within `jxl-oxide`. ### Impact On 32-bit platforms this can cause panic by accessing out-of-range indices, making it a DoS vulnerability.

GHSA-66m8-c62j-h6v5 Affected jxl-oxide Versions

1 component(s)
Fixed Versions:
0.12.6
Product / Package Ecosystem Affected Versions Fixed Version
jxl-oxide
 crates.io
< 0.12.6
0.12.6

References

GitHub Advisory / Wiki ADVISORY
https://github.com/tirr-c/jxl-oxide/security/advisories/GHSA-66m8-c62j-h6v5
jxl-oxide Source Repository REPOSITORY
https://github.com/tirr-c/jxl-oxide

Frequently Asked Questions

What is GHSA-66m8-c62j-h6v5?
GHSA-66m8-c62j-h6v5 is a security vulnerability in jxl-oxide involving `FrameBuffer::new` creates out-of-bounds slices on overflow under CWE-190: Integer Overflow or Wraparound.
Which jxl-oxide versions are affected?
Affected versions include releases prior to 0.12.6 across affected packages: jxl-oxide.
What version fixes GHSA-66m8-c62j-h6v5?
Upgrading to 0.12.6 (or the latest patched release for your respective branch) resolves the vulnerability.
Is jxl-oxide affected?
Yes, jxl-oxide is affected in releases prior to 0.12.6. Upgrade your dependency to 0.12.6 or later.
What is the CVSS score of GHSA-66m8-c62j-h6v5?
GHSA-66m8-c62j-h6v5 has a CVSS v3.1 base score of 6.2 (MODERATE) with vector string CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H.
What CWE is associated with GHSA-66m8-c62j-h6v5?
GHSA-66m8-c62j-h6v5 is classified under CWE-190: Integer Overflow or Wraparound (The product performs a calculation that can produce an integer overflow or wraparound when the logic assumes that the resulting value will always be larger than the original value. This occurs when an integer value is incremented to a value that is too large to store in the associated representation. When this occurs, the value may become a very small or negative number.).
How can I check crates.io dependencies for GHSA-66m8-c62j-h6v5?
Run the dependency tree command: 'inspect dependencies for jxl-oxide'. This command lists direct and transitive dependencies in your build configuration so you can verify if a vulnerable version is resolved.
Machine-readable OSV JSON OSV v1.5 Schema
Normalized schema output
View Raw JSON 
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-66m8-c62j-h6v5",
  "modified" : "2026-07-02T20:45:10Z",
  "published" : "2026-07-02T20:45:10Z",
  "aliases" : [ ],
  "summary" : "jxl-oxide: `FrameBuffer::new` creates out-of-bounds slices on overflow",
  "details" : "### Summary\n`jxl-oxide` exposes a public safe API that can construct an undersized `FrameBuffer` due to unchecked `usize` multiplication, which immediately trigger panic while initializing the buffer in normal decoding path.\n\nAdditionally, calling the safe grouped buffer accessors afterward can create invalid oversized slices from a much smaller allocation, causing undefined behavior; however normal decoding path never reaches UB, because these methods are never used within `jxl-oxide`.\n\n### Impact\nOn 32-bit platforms this can cause panic by accessing out-of-range indices, making it a DoS vulnerability.",
  "severity" : [ {
    "type" : "CVSS_V3",
    "score" : "CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H"
  } ],
  "affected" : [ {
    "package" : {
      "ecosystem" : "crates.io",
      "name" : "jxl-oxide"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "0"
      }, {
        "fixed" : "0.12.6"
      } ]
    } ],
    "database_specific" : {
      "last_known_affected_version_range" : "<= 0.12.5"
    }
  } ],
  "references" : [ {
    "type" : "WEB",
    "url" : "https://github.com/tirr-c/jxl-oxide/security/advisories/GHSA-66m8-c62j-h6v5"
  }, {
    "type" : "PACKAGE",
    "url" : "https://github.com/tirr-c/jxl-oxide"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-131", "CWE-190" ],
    "severity" : "MODERATE",
    "github_reviewed" : true,
    "github_reviewed_at" : "2026-07-02T20:45:10Z",
    "nvd_published_at" : null
  }
}