Skip to main content
Vulnerability Database/CVE-2026-80432

CVE-2026-80432: Kitty Terminal Information Disclosure Flaw

CVE-2026-80432 is an information disclosure vulnerability in Kitty terminal emulator that exposes dragged file contents without user consent. This article covers technical details, affected versions, and mitigation.

Published:

Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.

Sources: National Vulnerability Database, CISA KEV, Exploit-DB

CVE-2026-80432 Overview

CVE-2026-80432 is a missing authorization vulnerability [CWE-862] in the drag-and-drop (DnD) protocol of the kitty terminal emulator. Versions from 0.47.0 up to 0.49.0 fail to verify the drop state of the terminal window before serving drag data to a client program writing escape codes to the terminal. A program running inside the terminal can request the contents of files the user merely hovers over the window, without the user ever completing a drop. The flaw was fixed in kitty 0.49.0 by requiring that a drop event actually occurs before data requests are served.

Critical Impact

A local program with terminal write access can read arbitrary files that the user drags over the kitty window, resulting in disclosure of file contents the user never intended to transfer.

Affected Products

  • kitty terminal emulator version 0.47.0
  • kitty terminal emulator versions after 0.47.0 and before 0.49.0
  • kitty 0.48.2 (last vulnerable release before the fix)

Discovery Timeline

  • 2026-09-25 - CVE-2026-80432 published to NVD
  • 2026-09-29 - Last updated in NVD database

Technical Details for CVE-2026-80432

Vulnerability Analysis

The kitty drag-and-drop protocol lets client programs request MIME-typed data for items dragged onto the terminal window. The protocol expects data to be served only after the user releases the drag inside the window. In vulnerable versions, drop_enqueue_request() in kitty/dnd.c processes a client data request without checking whether a drop event has occurred. A client that issues the request while a drag is only hovering receives the data offered by the drag source.

The second half of the flaw lives in drop_left_child(). This function runs when a drag leaves the window without a drop. It releases the offered MIME list but keeps the pending request state, the open file descriptor, the main loop transfer timer, directory handles, the URI list, and the pending MIME name. The client can continue reading through a retained directory handle, and an in-flight file transfer keeps streaming after the drag ends.

The kitty process reads the file contents from the filesystem using paths supplied by the drag source. The result is disclosure of files the user moved over the window without releasing them.

Root Cause

The root cause is a missing authorization check [CWE-862]. The drop handling path treats a drag-in-progress as sufficient authorization to serve file data. It should require a completed drop event. Resource cleanup on drag-leave is also incomplete, leaving session state live after the authorization context has ended.

Attack Vector

Exploitation requires local terminal access and user interaction. An attacker-controlled program running inside a kitty session, such as a shell command, a text editor plugin, or a program viewed through less, sends the DnD data request escape sequence (OSC _dnd_code ; t=r:x=idx ST). When the user drags a file or folder over the kitty window without dropping it, the program silently receives the file contents or enumerates directory entries.

text
// Patch excerpt — docs/dnd-protocol.rst
Data may only be requested after a drop has actually occurred, receiving
movement events is not sufficient. Terminals must reject any data request
received before the drop event with an ``EPERM`` error. Since no drop is in
progress, this particular error does not terminate anything. Additionally,
when a drag leaves the window without a drop having occurred, terminals must
discard all data and resources associated with the drag session, such as
previously fetched URI lists, in-progress file transfers and directory
handles. Requests referring to them must fail.

Source: GitHub commit 026d11f

Detection Methods for CVE-2026-80432

Indicators of Compromise

  • Terminal escape sequences matching the kitty DnD data request format (OSC _dnd_... ; t=r:x=...) emitted by processes other than legitimate interactive clients.
  • Unexpected file read activity from the kitty process targeting paths outside its normal working set, correlated with user drag activity.
  • Long-lived file descriptors held by kitty for files or directories that the user did not open through the terminal.

Detection Strategies

  • Audit process execution inside terminal sessions for shell commands or TUI programs that write raw OSC sequences to standard output.
  • Monitor kitty process file access with Linux audit rules (auditctl -a always,exit -F arch=b64 -S openat -F exe=/usr/bin/kitty) to flag reads of sensitive directories such as /home/*/.ssh/ or /etc/.
  • Correlate kitty version strings reported by endpoint inventory with the vulnerable range 0.47.0 through 0.48.2.

Monitoring Recommendations

  • Collect terminal process telemetry and file access events into a central data lake for retroactive hunting across the vulnerable version range.
  • Alert on kitty child processes that write high volumes of OSC escape sequences, which is uncommon for benign interactive use.
  • Track installed kitty package versions through configuration management or EDR software inventory feeds.

How to Mitigate CVE-2026-80432

Immediate Actions Required

  • Upgrade kitty to version 0.49.0 or later on all workstations and multi-user hosts.
  • Avoid dragging sensitive files or directories over any kitty window running a vulnerable version, even without releasing the drop.
  • Inventory endpoints for kitty installations sourced from distribution packages, Homebrew, or manual builds, since package maintainers may lag upstream.

Patch Information

The fix is included in kitty 0.49.0, released by the upstream maintainer. The commit 026d11f517da17bfd3c35ea502057babdfbe5828 updates drop_enqueue_request() to reject data requests received before a drop event with an EPERM error. It also updates drop_left_child() to discard all pending drag resources, including URI lists, in-progress file transfers, and directory handles. See the kitty v0.49.0 release notes and the Secur0 advisory for additional context.

Workarounds

  • Switch to a different terminal emulator until the upgrade can be deployed on systems that cannot be patched immediately.
  • Restrict execution of untrusted binaries and scripts inside kitty sessions to reduce the chance of a hostile OSC emitter.
  • Train users to drop drags outside the kitty window, or press Escape to cancel, when transferring sensitive files between applications.
bash
# Verify installed kitty version and upgrade
kitty --version

# Debian/Ubuntu
sudo apt update && sudo apt install --only-upgrade kitty

# Arch Linux
sudo pacman -Syu kitty

# macOS (Homebrew)
brew upgrade kitty

# Confirm the fixed version is installed
kitty --version | awk '{print $2}'  # expect 0.49.0 or later

Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.

Sources: National Vulnerability Database, CISA KEV, Exploit-DB

Experience the Most Advanced Cybersecurity Platform

See how the world’s most intelligent, autonomous cybersecurity platform can protect your organization today and into the future.