{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2026-55693 in the wild and no public exploit code.","fix":"Upgrade to a fixed version.","what":"CVE-2026-55693 is a medium-severity memory corruption vulnerability in Vim Vim, published on 25 Jun 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2026-55693 and fix it if it is affected.\n\nWhat it is: CVE-2026-55693 is a medium-severity memory corruption vulnerability in Vim Vim, published on 25 Jun 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2026-55693 in the wild and no public exploit code.\n\nAffected product: Vim Vim. 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-55693/ (Markdown: https://insights.sbomify.com/CVE-2026-55693/index.md)","id":"CVE-2026-55693","markdown":"https://insights.sbomify.com/CVE-2026-55693/index.md","name":"CVE-2026-55693","record":{"aliases":["AZL-91107","BELL-CVE-2026-55693","DEBIAN-CVE-2026-55693","ECHO-31d3-7c0e-c6d2","GHSA-wgh4-64f7-q3jq","MINI-83vm-2w88-v66c","ROOT-OS-DEBIAN-11-CVE-2026-55693","ROOT-OS-DEBIAN-12-CVE-2026-55693","UBUNTU-CVE-2026-55693"],"analysis":{"component_type":"desktop_application","fix_type":"upgrade","impacts":["denial_of_service","code_execution"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Vim text editor","requires_auth":"none","summary":"A crafted spell file can cause an out-of-bounds write in Vim, leading to a crash or potential code execution when spell suggestions are used.","user_interaction":"required","vuln_class":"memory_corruption"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"vim","vendor":"vim"}],"cvss":{"score":5.7,"severity":"medium","source":"cna","vector":"CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:A/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N/E:U","version":"4.0"},"cwes":[{"id":"CWE-787","name":"Out-of-bounds Write"}],"description":"Vim is an open source, command line text editor. Prior to 9.2.0653, the tree_count_words() function in src/spellfile.c fills in the word-count fields of a spell-file word trie by walking it iteratively with a depth counter. The counter is bounded only by the trie structure itself; it is never checked against the size of the fixed MAXWLEN-element stack arrays it indexes (arridx[], curi[], wordcount[]). A crafted .spl/.sug file pair, loaded when the user invokes spell suggestion, can drive the descent arbitrarily deep, so the function writes past the end of those arrays. This is a stack out-of-bounds write that corrupts the call frame and crashes the editor. This vulnerability is fixed in 9.2.0653.","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":"Vim: Out-of-bounds Write in Spell File Word Count","id":"CVE-2026-55693","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"vim:vim","products":["vim:vim"],"type":"memory_corruption","year":"2026"},"n_packages":0,"n_references":3,"next":{"headline":"Snipe-IT: Chained Information Disclosure and IDOR Leads to Full EULA File Takeover","id":"CVE-2026-55694"},"packages":[],"prev":{"headline":"EmbedVideo Extension: Stored XSS via malformed src url with $wgEmbedVideoRequireConsent enabled","id":"CVE-2026-55692"},"products":["vim"],"published":"2026-06-25","related":[{"cvss_score":9.8,"headline":"Memory corruption in n/a","id":"CVE-2020-20703","kev_date_added":null,"published":"2023-06-20"},{"cvss_score":9.8,"headline":"Integer overflow in n/a","id":"CVE-2017-6349","kev_date_added":null,"published":"2017-02-27"},{"cvss_score":9.8,"headline":"Integer overflow in n/a","id":"CVE-2017-6350","kev_date_added":null,"published":"2017-02-27"},{"cvss_score":9.8,"headline":"Integer overflow in n/a","id":"CVE-2017-5953","kev_date_added":null,"published":"2017-02-10"},{"cvss_score":9.3,"headline":"Command injection in n/a","id":"CVE-2008-3075","kev_date_added":null,"published":"2009-02-21"},{"cvss_score":9.3,"headline":"Command injection in n/a","id":"CVE-2008-3076","kev_date_added":null,"published":"2009-02-21"},{"cvss_score":9.3,"headline":"Command injection in n/a","id":"CVE-2008-6235","kev_date_added":null,"published":"2009-02-21"}],"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":"total"},"state":"PUBLISHED","updated":"2026-06-26","vendors":["vim"]},"summary":"A crafted spell file can cause an out-of-bounds write in Vim, leading to a crash or potential code execution when spell suggestions are used.","url":"https://insights.sbomify.com/CVE-2026-55693/"}