{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-26824 exists.","fix":"Upgrade to a fixed version.","what":"CVE-2026-26824 is a medium-severity vulnerability in n/a, published on 3 Jun 2026. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-26824 and fix it if it is affected.\n\nWhat it is: CVE-2026-26824 is a medium-severity vulnerability in n/a, published on 3 Jun 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-26824 exists.\n\nAffected product: n/a. 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-26824/ (Markdown: https://insights.sbomify.com/CVE-2026-26824/index.md)","id":"CVE-2026-26824","markdown":"https://insights.sbomify.com/CVE-2026-26824/index.md","name":"CVE-2026-26824","record":{"aliases":["DEBIAN-CVE-2026-26824","GHSA-hwmf-9wj8-35pw","JLSEC-2026-1301","UBUNTU-CVE-2026-26824"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["data_read","denial_of_service"],"network_reachable":"yes","non_default_config":false,"product_category":"libxls library","requires_auth":"none","summary":"Attackers can cause crashes or disclose information by processing crafted XLS files due to uninitialized memory in the libxls library.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"libxls","vendor":"libxls_project"}],"cvss":{"score":6.5,"severity":"medium","source":"cisa-adp","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:L","version":"3.1"},"cwes":[{"id":"CWE-457","name":"Use of Uninitialized Variable"}],"description":"libxls through version 1.6.3 contains a use of uninitialized memory vulnerability in the OLE container parser. Memory allocated for the Master Sector Allocation Table (MSAT) in read_MSAT() is not fully initialized before being consumed by ole2_validate_sector_chain(), which may result in application crashes or potential information disclosure when processing a crafted XLS file","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":"Information disclosure in n/a","id":"CVE-2026-26824","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"information_disclosure","year":"2026"},"n_packages":0,"n_references":3,"next":{"headline":"Information disclosure in n/a","id":"CVE-2026-26825"},"packages":[],"prev":{"headline":"DO NOT USE THIS CVE RECORD.","id":"CVE-2026-26809"},"products":["n/a"],"published":"2026-06-03","related":[{"cvss_score":8.8,"headline":"Memory corruption in libxls","id":"CVE-2017-2910","kev_date_added":null,"published":"2020-12-02"},{"cvss_score":8.8,"headline":"Use after free in n/a","id":"CVE-2018-20452","kev_date_added":null,"published":"2018-12-25"},{"cvss_score":8.8,"headline":"Integer overflow in libxls","id":"CVE-2017-12108","kev_date_added":null,"published":"2018-04-24"},{"cvss_score":8.8,"headline":"Integer overflow in libxls","id":"CVE-2017-12109","kev_date_added":null,"published":"2018-04-24"},{"cvss_score":8.8,"headline":"Integer overflow in libxls","id":"CVE-2017-12110","kev_date_added":null,"published":"2017-11-20"},{"cvss_score":8.8,"headline":"Memory corruption in libxls","id":"CVE-2017-12111","kev_date_added":null,"published":"2017-11-20"},{"cvss_score":8.8,"headline":"Memory corruption in libxls","id":"CVE-2017-2897","kev_date_added":null,"published":"2017-11-20"}],"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":"yes","exploitation":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-09-23","vendors":["n/a"]},"summary":"Attackers can cause crashes or disclose information by processing crafted XLS files due to uninitialized memory in the libxls library.","url":"https://insights.sbomify.com/CVE-2026-26824/"}