{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2026-26825 in the wild and no public exploit code.","fix":"Upgrade to a fixed version.","what":"CVE-2026-26825 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-26825 and fix it if it is affected.\n\nWhat it is: CVE-2026-26825 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: There is no known exploitation of CVE-2026-26825 in the wild and no public exploit code.\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-26825/ (Markdown: https://insights.sbomify.com/CVE-2026-26825/index.md)","id":"CVE-2026-26825","markdown":"https://insights.sbomify.com/CVE-2026-26825/index.md","name":"CVE-2026-26825","record":{"aliases":["DEBIAN-CVE-2026-26825","GHSA-48jr-3rh3-95w6","UBUNTU-CVE-2026-26825"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"libxls library","requires_auth":"none","summary":"Attackers can exploit uninitialized memory in libxls to potentially disclose sensitive information when parsing malformed XLS files.","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":5.3,"severity":"medium","source":"cisa-adp","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-908","name":"Use of Uninitialized Resource"}],"description":"A use-of-uninitialized memory vulnerability exists in libxls 1.6.3 when parsing malformed XLS files. The issue is reachable via xls_parseWorkBook() and is triggered by uninitialized heap memory originating from the OLE layer (ole2_read). The flaw is detectable with MemorySanitizer (MSAN) and can lead to undefined behavior, incorrect parsing logic, or potential information disclosure.","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":"Information disclosure in n/a","id":"CVE-2026-26825","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":"Null dereference in n/a","id":"CVE-2026-26828"},"packages":[],"prev":{"headline":"Information disclosure in n/a","id":"CVE-2026-26824"},"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":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-09-23","vendors":["n/a"]},"summary":"Attackers can exploit uninitialized memory in libxls to potentially disclose sensitive information when parsing malformed XLS files.","url":"https://insights.sbomify.com/CVE-2026-26825/"}