UBUNTU-CVE-2026-54056 (CVE-2026-54056)
Vulnerability from osv_ubuntu – Published: 2026-06-12 21:16 – Updated: 2026-10-17 09:45 – Source websiteKitty is a cross-platform GPU based terminal. In versions 0.47.0 and 0.47.1, kitten dnd can allow a malicious remote drag-and-drop source to overwrite or truncate arbitrary files writable by the local kitty user. Remote text/uri-list drops are staged in a temporary directory, but on case-sensitive filesystems duplicate remote basenames are not de-duplicated. An attacker can first create a staged symlink and then send a same-name regular-file entry. The regular-file write uses utils.CreateAt() / openat(O_RDWR|O_CREAT|O_TRUNC) without O_NOFOLLOW, so it follows the attacker-created symlink and writes outside the staging directory before final overwrite confirmation runs. This appears related in class to the file-transfer symlink advisory, but it is a different bug: it affects kitten dnd remote drag-and-drop staging, uses different vulnerable code (kittens/dnd/drop.go and tools/utils/file_at_fd.go), and reproduces on commit 4aa4a5c0567a92553a8c20a88a4352da637fca5d, after the file-transfer O_NOFOLLOW fix. Version 0.47.2 patches the issue.
{
"affected": [
{
"ecosystem_specific": {
"binaries": [
{
"binary_name": "kitty",
"binary_version": "0.15.0-1ubuntu0.2+esm1"
},
{
"binary_name": "kitty-terminfo",
"binary_version": "0.15.0-1ubuntu0.2+esm1"
}
]
},
"package": {
"ecosystem": "Ubuntu:Pro:20.04:LTS",
"name": "kitty",
"purl": "pkg:deb/ubuntu/kitty@0.15.0-1ubuntu0.2+esm1?arch=source\u0026distro=esm-apps/focal"
},
"ranges": [
{
"events": [
{
"introduced": "0"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"0.14.3-1",
"0.14.4-1",
"0.14.6-1",
"0.15.0-1",
"0.15.0-1build1",
"0.15.0-1ubuntu0.2",
"0.15.0-1ubuntu0.2+esm1"
]
},
{
"ecosystem_specific": {
"binaries": [
{
"binary_name": "kitty",
"binary_version": "0.21.2-1ubuntu0.22.04.1+esm1"
}
]
},
"package": {
"ecosystem": "Ubuntu:Pro:22.04:LTS",
"name": "kitty",
"purl": "pkg:deb/ubuntu/kitty@0.21.2-1ubuntu0.22.04.1+esm1?arch=source\u0026distro=esm-apps/jammy"
},
"ranges": [
{
"events": [
{
"introduced": "0"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"0.19.3-1",
"0.21.2-1",
"0.21.2-1build1",
"0.21.2-1ubuntu0.22.04.1",
"0.21.2-1ubuntu0.22.04.1+esm1"
]
},
{
"ecosystem_specific": {
"binaries": [
{
"binary_name": "kitty",
"binary_version": "0.32.2-1ubuntu0.4+esm2"
},
{
"binary_name": "kitty-shell-integration",
"binary_version": "0.32.2-1ubuntu0.4+esm2"
},
{
"binary_name": "kitty-terminfo",
"binary_version": "0.32.2-1ubuntu0.4+esm2"
}
]
},
"package": {
"ecosystem": "Ubuntu:Pro:24.04:LTS",
"name": "kitty",
"purl": "pkg:deb/ubuntu/kitty@0.32.2-1ubuntu0.4+esm2?arch=source\u0026distro=esm-apps/noble"
},
"ranges": [
{
"events": [
{
"introduced": "0"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"0.26.5-3ubuntu2",
"0.26.5-5ubuntu1",
"0.31.0-3",
"0.31.0-4",
"0.32.2-1",
"0.32.2-1build2",
"0.32.2-1build3",
"0.32.2-1ubuntu0.1",
"0.32.2-1ubuntu0.2",
"0.32.2-1ubuntu0.3",
"0.32.2-1ubuntu0.4",
"0.32.2-1ubuntu0.4+esm1",
"0.32.2-1ubuntu0.4+esm2"
]
},
{
"ecosystem_specific": {
"binaries": [
{
"binary_name": "kitty",
"binary_version": "0.41.1-2+deb13u1build0.25.10.1"
},
{
"binary_name": "kitty-shell-integration",
"binary_version": "0.41.1-2+deb13u1build0.25.10.1"
},
{
"binary_name": "kitty-terminfo",
"binary_version": "0.41.1-2+deb13u1build0.25.10.1"
}
]
},
"package": {
"ecosystem": "Ubuntu:25.10",
"name": "kitty",
"purl": "pkg:deb/ubuntu/kitty@0.41.1-2+deb13u1build0.25.10.1?arch=source\u0026distro=questing"
},
"ranges": [
{
"events": [
{
"introduced": "0"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"0.39.1-1",
"0.41.1-2",
"0.41.1-2+deb13u1build0.25.10.1"
]
},
{
"ecosystem_specific": {
"binaries": [
{
"binary_name": "kitty",
"binary_version": "0.48.2-1.1ubuntu1"
},
{
"binary_name": "kitty-shell-integration",
"binary_version": "0.48.2-1.1ubuntu1"
},
{
"binary_name": "kitty-terminfo",
"binary_version": "0.48.2-1.1ubuntu1"
}
]
},
"package": {
"ecosystem": "Ubuntu:26.10",
"name": "kitty",
"purl": "pkg:deb/ubuntu/kitty@0.48.2-1.1ubuntu1?arch=source\u0026distro=stonking"
},
"ranges": [
{
"events": [
{
"introduced": "0"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"0.45.0-1build1",
"0.47.0-3",
"0.47.4-1",
"0.48.2-1.1ubuntu1"
]
},
{
"ecosystem_specific": {
"binaries": [
{
"binary_name": "kitty",
"binary_version": "0.45.0-1ubuntu0.1~esm2"
},
{
"binary_name": "kitty-shell-integration",
"binary_version": "0.45.0-1ubuntu0.1~esm2"
},
{
"binary_name": "kitty-terminfo",
"binary_version": "0.45.0-1ubuntu0.1~esm2"
}
]
},
"package": {
"ecosystem": "Ubuntu:Pro:26.04:LTS",
"name": "kitty",
"purl": "pkg:deb/ubuntu/kitty@0.45.0-1ubuntu0.1~esm2?arch=source\u0026distro=esm-apps/resolute"
},
"ranges": [
{
"events": [
{
"introduced": "0"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"0.41.1-2",
"0.43.1-1",
"0.44.0-1",
"0.45.0-1",
"0.45.0-1build1",
"0.45.0-1ubuntu0.1~esm1",
"0.45.0-1ubuntu0.1~esm2"
]
}
],
"aliases": [],
"details": "Kitty is a cross-platform GPU based terminal. In versions 0.47.0 and 0.47.1, `kitten dnd` can allow a malicious remote drag-and-drop source to overwrite or truncate arbitrary files writable by the local kitty user. Remote `text/uri-list` drops are staged in a temporary directory, but on case-sensitive filesystems duplicate remote basenames are not de-duplicated. An attacker can first create a staged symlink and then send a same-name regular-file entry. The regular-file write uses `utils.CreateAt()` / `openat(O_RDWR|O_CREAT|O_TRUNC)` without `O_NOFOLLOW`, so it follows the attacker-created symlink and writes outside the staging directory before final overwrite confirmation runs. This appears related in class to the file-transfer symlink advisory, but it is a different bug: it affects `kitten dnd` remote drag-and-drop staging, uses different vulnerable code (`kittens/dnd/drop.go` and `tools/utils/file_at_fd.go`), and reproduces on commit `4aa4a5c0567a92553a8c20a88a4352da637fca5d`, after the file-transfer `O_NOFOLLOW` fix. Version 0.47.2 patches the issue.",
"id": "UBUNTU-CVE-2026-54056",
"modified": "2026-10-17T09:45:54Z",
"published": "2026-06-12T21:16:00Z",
"references": [
{
"type": "REPORT",
"url": "https://ubuntu.com/security/CVE-2026-54056"
},
{
"type": "REPORT",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-54056"
},
{
"type": "REPORT",
"url": "https://github.com/kovidgoyal/kitty/security/advisories/GHSA-r892-cv7q-fw8x"
}
],
"related": [],
"schema_version": "1.7.0",
"severity": [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:N/I:H/A:L",
"type": "CVSS_V3"
},
{
"score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:L",
"type": "CVSS_V3"
},
{
"score": "medium",
"type": "Ubuntu"
}
],
"upstream": [
"CVE-2026-54056"
]
}
Drag nodes to arrange them. Double-click a related vulnerability to open it, or a source to visit its link. The Physics button on the left tunes the layout and the simulation; the legend at the bottom left hides or shows nodes by kind and by sighting type.
Sightings
| Author | Source | Type | Date | Other |
|---|
Nomenclature
- Seen: The vulnerability was mentioned, discussed, or observed by the user.
- Confirmed: The vulnerability has been validated from an analyst's perspective.
- Published Proof of Concept: A public proof of concept is available for this vulnerability.
- Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
- Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
- Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
- Not confirmed: The user expressed doubt about the validity of the vulnerability.
- Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.
Vulnerability timeline
Sightings and recorded dates, grouped by day · UTC
How durations are calculated
Following the VTEM framework (Black Hat USA 2015), time to patch starts when the vendor or a coordinator was informed, total time to patch at discovery, and disclosure to patch at public disclosure; vendor response time runs from the report to its acknowledgement. Time to exploit and time unpatched start at the earliest discovery or report, falling back to public disclosure. Unpatched time ends at the first recorded patch, or the calculation time when no patch is recorded. Exploitation to patch shows the interval between those two events; a published proof of concept is a public exploit, not exploitation.
Each result shows its source dates. A negative interval means the end event came first; when date-only inputs leave the order open, the result says so. Date-only inputs are approximate. The earliest evidence wins: KEV report dates and sightings are labelled as such. Records describing another vulnerability are listed but never calculated from, and a PoC alone does not establish exploitation. Missing patch evidence does not prove that no patch exists. Filters below change the event list only.
Loading timeline…
The approach is described in our paper Mapping CVEs to MITRE ATT&CK Techniques: A Curated Gold-Set Classifier and the Limits of LLM-Assisted Label Expansion.
Browse all ATT&CK techniques and the vulnerabilities related to each.
Related by attack behaviour
Vulnerabilities whose description is nearest to this one in the vector space of the CIRCL/vulnerability-attack-technique-biencoder model. This is a similarity search over the bi-encoder space (plain cosine), not a classification, and it has no measured accuracy.