{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-26197 exists.","fix":"Apply the vendor's patch.","what":"CVE-2026-26197 is a medium-severity memory corruption vulnerability in Hdfgroup Hdf5, published on 20 Jul 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-2026-26197 and fix it if it is affected.\n\nWhat it is: CVE-2026-26197 is a medium-severity memory corruption vulnerability in Hdfgroup Hdf5, published on 20 Jul 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: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-26197 exists.\n\nAffected product: Hdfgroup Hdf5. 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-2026-26197/ (Markdown: https://insights.sbomify.com/CVE-2026-26197/index.md)","id":"CVE-2026-26197","markdown":"https://insights.sbomify.com/CVE-2026-26197/index.md","name":"CVE-2026-26197","record":{"aliases":["AZL-92847","DEBIAN-CVE-2026-26197","ECHO-e487-ec41-9a0c","GHSA-gh44-7wpq-622f","JLSEC-2026-1162","UBUNTU-CVE-2026-26197"],"analysis":{"component_type":"library","fix_type":"patch","impacts":["data_read","denial_of_service"],"network_reachable":"yes","non_default_config":false,"product_category":"HDF5 data library","requires_auth":"none","summary":"A maliciously crafted HDF5 file can trigger an out-of-bounds read due to inconsistent array metadata, potentially exposing memory or causing crashes.","user_interaction":"required","vuln_class":"memory_corruption"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"hdf5","vendor":"hdfgroup"}],"cvss":{"score":5.9,"severity":"medium","source":"cna","vector":"CVSS:4.0/AV:N/AC:H/AT:P/PR:N/UI:A/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N","version":"4.0"},"cwes":[{"id":"CWE-125","name":"Out-of-bounds Read"}],"description":"HDF5 is a high-performance library and a file format specification that implements the HDF5 data model. If a file is corrupted such that an array datatype's size, the number of elements, and the element size  are not in agreement it can trigger an out of bounds read. The array datatype stores the full size of the datatype (`dt-\u003eshared-\u003esize`) separately from the number of elements (`dt-\u003eshared-\u003eu.array.nelem`) and the element size (`dt-\u003eshared-\u003eparent-\u003eshared-\u003esize`). If any one of these are corrupted so that they don't align with the others (element size * nelem = full size), it can lead to an out of bounds read. Depending on what is corrupted, it can alter the type of out of bounds read triggered. The vulnerability is present only in files that have been maliciously altered, as its generally not possible to independently alter the full size of the datatype, the element count and the element size. As such, this is only present if a malicious actor is altering files, and won't appear in regular usage.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":true,"headline":"Array full size, element count, and element size are not checked to make sure they match in H5Odtype.c","id":"CVE-2026-26197","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"hdfgroup:hdf5","products":["hdfgroup:hdf5"],"type":"memory_corruption","year":"2026"},"n_packages":0,"n_references":1,"next":{"headline":"ormar is vulnerable to SQL Injection through aggregate functions min() and max()","id":"CVE-2026-26198"},"packages":[],"prev":{"headline":"Gogs: Access tokens get exposed through URL params in API requests","id":"CVE-2026-26196"},"products":["hdf5"],"published":"2026-07-20","related":[{"cvss_score":9.8,"headline":"Memory corruption in n/a","id":"CVE-2024-32608","kev_date_added":null,"published":"2024-10-09"},{"cvss_score":9.8,"headline":"Memory corruption in n/a","id":"CVE-2024-29157","kev_date_added":null,"published":"2024-05-09"},{"cvss_score":9.8,"headline":"Memory corruption in n/a","id":"CVE-2024-29159","kev_date_added":null,"published":"2024-05-09"},{"cvss_score":9.8,"headline":"Memory corruption in n/a","id":"CVE-2024-29164","kev_date_added":null,"published":"2024-05-09"},{"cvss_score":9.8,"headline":"Other in n/a","id":"CVE-2024-32611","kev_date_added":null,"published":"2024-05-09"},{"cvss_score":9.8,"headline":"Memory corruption in n/a","id":"CVE-2024-32615","kev_date_added":null,"published":"2024-05-09"},{"cvss_score":9.8,"headline":"Memory corruption in n/a","id":"CVE-2024-32621","kev_date_added":null,"published":"2024-05-09"}],"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":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-07-20","vendors":["HDFGroup"]},"summary":"A maliciously crafted HDF5 file can trigger an out-of-bounds read due to inconsistent array metadata, potentially exposing memory or causing crashes.","url":"https://insights.sbomify.com/CVE-2026-26197/"}