{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2025-12474 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2025-12474 is a low-severity vulnerability in Google libjxl, published on 11 Feb 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2025-12474 and fix it if it is affected.\n\nWhat it is: CVE-2025-12474 is a low-severity vulnerability in Google libjxl, published on 11 Feb 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2025-12474 in the wild and no public exploit code.\n\nAffected product: Google libjxl. No package-level version data is available, so check the vendor advisory linked from the reference page.\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-2025-12474/ (Markdown: https://insights.sbomify.com/CVE-2025-12474/index.md)","id":"CVE-2025-12474","markdown":"https://insights.sbomify.com/CVE-2025-12474/index.md","name":"CVE-2025-12474","record":{"aliases":["DEBIAN-CVE-2025-12474","GHSA-9gvg-fw8p-72fv","UBUNTU-CVE-2025-12474"],"analysis":{"component_type":"library","fix_type":"patch","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"JPEG XL library","requires_auth":"none","summary":"A crafted file triggers uninitialized memory reads in libjxl, potentially exposing sensitive data to attackers.","user_interaction":"required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Google","cpe":[{"product":"libjxl","vendor":"libjxl_project"}],"cvss":{"score":2.3,"severity":"low","source":"cna","vector":"CVSS:4.0/AV:N/AC:H/AT:N/PR:N/UI:P/VC:L/VI:L/VA:N/SC:N/SI:N/SA:N","version":"4.0"},"cwes":[{"id":"CWE-908","name":"Use of Uninitialized Resource"}],"description":"A specially-crafted file can cause libjxl's decoder to read pixel data from uninitialized (but allocated) memory.\n\nThis can be done by causing the decoder to reference an outside-image-bound area in a subsequent patches. An incorrect optimization causes the decoder to omit populating those areas.","ecosystems":[],"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":"libjxl: Uninitialized memory read in decoder due to incorrect optimization in patch handling","id":"CVE-2025-12474","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"information_disclosure","year":"2025"},"n_packages":0,"n_references":1,"next":{"headline":"Blocksy Companion \u003c= 2.1.14 - Authenticated (Contributor+) Stored Cross-Site Scripting","id":"CVE-2025-12475"},"packages":[],"prev":{"headline":"RTMKit \u003c= 1.6.8 - Reflected Cross-Site Scripting via 'themebuilder' Parameter","id":"CVE-2025-12473"},"products":["libjxl"],"published":"2026-02-11","related":[{"cvss_score":9.8,"headline":"Memory corruption in n/a","id":"CVE-2021-27804","kev_date_added":null,"published":"2021-03-02"},{"cvss_score":8.7,"headline":"libjxl: Out-of-bounds write in grayscale color transformation when using LCMS2","id":"CVE-2026-1837","kev_date_added":null,"published":"2026-02-11"},{"cvss_score":7.5,"headline":"Integer overflow in n/a","id":"CVE-2023-35790","kev_date_added":null,"published":"2023-06-16"},{"cvss_score":7.5,"headline":"Denial of service in n/a","id":"CVE-2021-36691","kev_date_added":null,"published":"2021-08-30"},{"cvss_score":6.9,"headline":"Out of Bounds Memory Read/Write in libjxl","id":"CVE-2024-11403","kev_date_added":null,"published":"2024-11-25"},{"cvss_score":6.9,"headline":"Resource exhaustion via Stack overflow in libjxl","id":"CVE-2024-11498","kev_date_added":null,"published":"2024-11-25"},{"cvss_score":6.5,"headline":"Denial of service in n/a","id":"CVE-2022-34000","kev_date_added":null,"published":"2022-06-19"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"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-02-11","vendors":["Google"]},"summary":"A crafted file triggers uninitialized memory reads in libjxl, potentially exposing sensitive data to attackers.","url":"https://insights.sbomify.com/CVE-2025-12474/"}