Summary
Logic bug in decode_simple_table_slow may cause integer arithmetic overflow when decoding Modular image with certain kind of MA tree, which may panic with overflow-checks enabled.
Impact
Denial of service: any application passing untrusted JXL data to JxlImage::render_frame (or equivalent) can be
crashed. Affects all builds with overflow checks enabled, which includes debug builds and any release build
that sets overflow-checks = true in Cargo.toml or [profile.*].
No memory corruption is possible, the panic fires before any unsafe code is reached.
An arithmetic operation produces a value that exceeds the integer type's maximum, causing it to wrap to an unexpected small value. Typical impact: incorrect size calculations leading to heap overflows or logic errors.
GHSA-2V8P-FQPX-2Q3W has a CVSS score of 6.2 (Medium). The vector is requires local access, no privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (0.11.3); upgrading removes the vulnerable code path.
Affected versions
Security releases
Kodem intelligence
Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.
Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.
Remediation advice
Kodem Kai can prioritize this vulnerability in your dependency tree and generate a fix recommendation.
Frequently Asked Questions
- What is GHSA-2V8P-FQPX-2Q3W? GHSA-2V8P-FQPX-2Q3W is a medium-severity integer overflow or wraparound vulnerability in jxl-modular (rust), affecting versions <= 0.11.2. It is fixed in 0.11.3. An arithmetic operation produces a value that exceeds the integer type's maximum, causing it to wrap to an unexpected small value.
- How severe is GHSA-2V8P-FQPX-2Q3W? GHSA-2V8P-FQPX-2Q3W has a CVSS score of 6.2 (Medium). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
- Which versions of jxl-modular are affected by GHSA-2V8P-FQPX-2Q3W? jxl-modular (rust) versions <= 0.11.2 is affected.
- Is there a fix for GHSA-2V8P-FQPX-2Q3W? Yes. GHSA-2V8P-FQPX-2Q3W is fixed in 0.11.3. Upgrade to this version or later.
- Is GHSA-2V8P-FQPX-2Q3W exploitable, and should I be worried? Whether GHSA-2V8P-FQPX-2Q3W is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
- What actually determines whether GHSA-2V8P-FQPX-2Q3W is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
- How do I fix GHSA-2V8P-FQPX-2Q3W? Upgrade
jxl-modularto 0.11.3 or later.