{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2026-2703 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-2703 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-2703 is a medium-severity vulnerability in xlnt-community xlnt, published on 19 Feb 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-2703 and fix it if it is affected.\n\nWhat it is: CVE-2026-2703 is a medium-severity vulnerability in xlnt-community xlnt, published on 19 Feb 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-2703 in the wild and no public exploit code.\n\nAffected product: xlnt-community xlnt. 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-2703/ (Markdown: https://insights.sbomify.com/CVE-2026-2703/index.md)","id":"CVE-2026-2703","markdown":"https://insights.sbomify.com/CVE-2026-2703/index.md","name":"CVE-2026-2703","record":{"aliases":["GHSA-pf2p-f275-6cmx"],"analysis":{"component_type":"library","fix_type":"patch","impacts":["code_execution","denial_of_service"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Excel file library","requires_auth":"low_privilege","summary":"An off-by-one error in the base64 decoder of the xlnt library allows attackers to cause memory corruption via crafted encrypted XLSX files.","user_interaction":"not_required","vuln_class":"integer_overflow"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"VulDB","cpe":[{"product":"xlnt","vendor":"xlnt-community"}],"cvss":{"score":4.8,"severity":"medium","source":"cna","vector":"CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:N/VC:N/VI:N/VA:L/SC:N/SI:N/SA:N/E:P","version":"4.0"},"cwes":[{"id":"CWE-193","name":"Off-by-one Error"},{"id":"CWE-189","name":null}],"description":"A weakness has been identified in xlnt-community xlnt up to 1.6.1. Impacted is the function xlnt::detail::decode_base64 of the file source/detail/cryptography/base64.cpp of the component Encrypted XLSX File Parser. Executing a manipulation can lead to off-by-one. The attack requires local access. The exploit has been made available to the public and could be used for attacks. This patch is called f2d7bf494e5c52706843cf7eb9892821bffb0734. Applying a patch is advised to resolve this issue.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":false,"headline":"xlnt-community xlnt Encrypted XLSX File base64.cpp decode_base64 off-by-one","id":"CVE-2026-2703","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"integer_overflow","year":"2026"},"n_packages":0,"n_references":7,"next":{"headline":"Open Babel CIF File transform3d.cpp DescribeAsString out-of-bounds","id":"CVE-2026-2704"},"packages":[],"prev":{"headline":"Beetel 777VR1 WPA2 PSK hard-coded credentials","id":"CVE-2026-2702"},"products":["xlnt"],"published":"2026-02-19","related":[{"cvss_score":4.8,"headline":"xlnt-community xlnt XLSX File compound_document.cpp xsgetn out-of-bounds","id":"CVE-2026-3663","kev_date_added":null,"published":"2026-03-07"},{"cvss_score":4.8,"headline":"xlnt-community xlnt Encrypted XLSX File compound_document.cpp read_directory out-of-bounds","id":"CVE-2026-3664","kev_date_added":null,"published":"2026-03-07"},{"cvss_score":4.8,"headline":"xlnt-community xlnt XLSX File xlsx_consumer.cpp read_office_document null pointer dereference","id":"CVE-2026-3665","kev_date_added":null,"published":"2026-03-07"},{"cvss_score":4.8,"headline":"xlnt-community xlnt Compound Document binary.hpp append heap-based overflow","id":"CVE-2026-3463","kev_date_added":null,"published":"2026-03-03"}],"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-24","vendors":["xlnt-community"]},"summary":"An off-by-one error in the base64 decoder of the xlnt library allows attackers to cause memory corruption via crafted encrypted XLSX files.","url":"https://insights.sbomify.com/CVE-2026-2703/"}