{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-80431 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-80431 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-80431 is a medium-severity memory corruption vulnerability in Kovid Goyal kitty, published on 25 Sep 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-80431 and fix it if it is affected.\n\nWhat it is: CVE-2026-80431 is a medium-severity memory corruption vulnerability in Kovid Goyal kitty, published on 25 Sep 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-80431 in the wild and no public exploit code.\n\nAffected product: Kovid Goyal kitty. 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-80431/ (Markdown: https://insights.sbomify.com/CVE-2026-80431/index.md)","id":"CVE-2026-80431","markdown":"https://insights.sbomify.com/CVE-2026-80431/index.md","name":"CVE-2026-80431","record":{"aliases":["DEBIAN-CVE-2026-80431","GHSA-fx7r-q727-j825","UBUNTU-CVE-2026-80431"],"analysis":{"component_type":"desktop_application","fix_type":"upgrade","impacts":["denial_of_service"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"kitty terminal emulator","requires_auth":"none","summary":"A malicious program can crash the kitty terminal by sending a long grapheme cluster in an OSC 66 escape code, causing an out-of-bounds write.","user_interaction":"required","vuln_class":"memory_corruption"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Secur0","cpe":[],"cvss":{"score":6.8,"severity":"medium","source":"cna","vector":"CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:P/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N","version":"4.0"},"cwes":[{"id":"CWE-787","name":"Out-of-bounds Write"}],"description":"Out-of-bounds Write in the natural width branch of the text sizing protocol in kitty from 0.40.0 before 0.49.0 allows a program writing to the terminal to write past the end of a fixed-size buffer, because screen_handle_multicell_command() in kitty/screen.c appends each codepoint of a grapheme cluster with lc.chars[lc.count++] = ch without any capacity check, while lc is declared by the RAII_ListOfChars macro as a four-element char_type array in the function's stack frame, so an OSC 66 escape code whose payload carries a grapheme cluster longer than four codepoints writes beyond that buffer, one 32-bit value per additional codepoint, in the order the codepoints appear. Where the cluster is preceded in the same payload by a sequence that causes an intermediate flush, the buffer is first migrated to the heap by ensure_space_for_chars() and the write occurs past the heap allocation instead. This results in termination of the kitty process and therefore of all its windows, tabs and child processes.","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":"Out-of-bounds write in the kitty text sizing protocol allows termination of the terminal process","id":"CVE-2026-80431","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"memory_corruption","year":"2026"},"n_packages":0,"n_references":3,"next":{"headline":"Missing authorization in kitty","id":"CVE-2026-80432"},"packages":[],"prev":{"headline":"Path traversal in kitty","id":"CVE-2026-80430"},"products":["kitty"],"published":"2026-09-25","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"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-09-25","vendors":["Kovid Goyal"]},"summary":"A malicious program can crash the kitty terminal by sending a long grapheme cluster in an OSC 66 escape code, causing an out-of-bounds write.","url":"https://insights.sbomify.com/CVE-2026-80431/"}