{"answers":{"affected":"3 open source packages ship an affected version, including jxl-grid.","exploited":"There is no known exploitation of CVE-2026-52834 in the wild and no public exploit code.","fix":"Upgrade jxl-grid to 0.6.2 or later.","what":"CVE-2026-52834 is a high-severity vulnerability in tirr-c jxl-grid, published on 19 Aug 2026. It can only be exploited from the same machine or local network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-52834 and fix it if it is affected.\n\nWhat it is: CVE-2026-52834 is a high-severity vulnerability in tirr-c jxl-grid, published on 19 Aug 2026. It can only be exploited from the same machine or local network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-52834 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- jxl-grid (crates.io): affected all versions; fixed in 0.6.2\n- jxl-grid (crates.io): affected all versions; fixed in 0.6.2\n- jxl-grid (crates.io): affected from 0.0.0-0; fixed in 0.6.2\n\nTask:\n1. 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.\n2. 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.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-52834/ (Markdown: https://insights.sbomify.com/CVE-2026-52834/index.md)","id":"CVE-2026-52834","markdown":"https://insights.sbomify.com/CVE-2026-52834/index.md","name":"CVE-2026-52834","record":{"aliases":["GHSA-5pmv-rx8r-wmv5","RUSTSEC-2026-0151"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["code_execution","denial_of_service"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Rust JPEG XL decoder","requires_auth":"none","summary":"Integer overflow in jxl-grid allows out-of-bounds writes during JPEG XL decoding on 32-bit platforms, leading to code execution or crashes.","user_interaction":"not_required","vuln_class":"integer_overflow"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":7.3,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:L/AC:H/PR:N/UI:N/S:C/C:L/I:L/A:H","version":"3.1"},"cwes":[{"id":"CWE-190","name":"Integer Overflow or Wraparound"},{"id":"CWE-131","name":"Incorrect Calculation of Buffer Size"},{"id":"CWE-122","name":"Heap-based Buffer Overflow"}],"description":"jxl-oxide is a pure Rust implementation of a JPEG XL decoder. Prior to jxl-grid 0.6.2, decoding a crafted JPEG XL image on a 32-bit platform can overflow length calculations in AlignedGrid::with_alloc_tracker and related grid and subgrid arithmetic. A 65536 x 65536 frame can pass the frame-area limit while overflowing the usize element count, causing modular, VarDCT, or filter rendering paths to allocate a backing buffer smaller than the logical grid. A tiny bitstream-controlled cropped frame combined with a huge canvas or requested region can also reach the vulnerable composition path in crates/jxl-render/src/blend.rs through ordinary render_frame(). Later mutable subgrid and raw-pointer operations can then perform attacker-controlled out-of-bounds writes, causing memory corruption, denial of service, or arbitrary code execution. This issue is fixed in jxl-grid version 0.6.2.","ecosystems":["crates.io"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"jxl-oxide: Out-of-bounds writes due to integer overflow in jxl-grid on 32-bit platforms","id":"CVE-2026-52834","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"crates.io","product":null,"products":[],"type":"integer_overflow","year":"2026"},"n_packages":3,"n_references":4,"next":{"headline":"Tautulli: Path traversal / arbitrary file write via unsanitized upload filename in import_config and import_database","id":"CVE-2026-52835"},"packages":[{"ecosystem":"crates.io","fixed":["0.6.2"],"introduced":["0"],"last_affected":[],"package":"jxl-grid","purl":null,"source":"GHSA-5pmv-rx8r-wmv5"},{"ecosystem":"crates.io","fixed":["0.6.2"],"introduced":["0"],"last_affected":[],"package":"jxl-grid","purl":"pkg:cargo/jxl-grid","source":"GHSA-5pmv-rx8r-wmv5"},{"ecosystem":"crates.io","fixed":["0.6.2"],"introduced":["0.0.0-0"],"last_affected":[],"package":"jxl-grid","purl":"pkg:cargo/jxl-grid","source":"RUSTSEC-2026-0151"}],"prev":{"headline":"Nuclio: Unsanitized runtimeAttributes.repositories injected into Groovy build.gradle leads to build-time RCE","id":"CVE-2026-52833"},"products":["jxl-grid","jxl-oxide"],"published":"2026-08-19","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"class":"open","licence":"CC0 1.0","name":"RustSec","prefix":"RUSTSEC"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-08-19","vendors":["tirr-c"]},"summary":"Integer overflow in jxl-grid allows out-of-bounds writes during JPEG XL decoding on 32-bit platforms, leading to code execution or crashes.","url":"https://insights.sbomify.com/CVE-2026-52834/"}