Kitty is a cross-platform GPU based terminal. In versions prior to 0.47.2, a local privilege escalation vulnerability exists in kitty's file transmission protocol where a child process running in the terminal can write to arbitrary files on the filesystem by exploiting a TOCTOU (Time-of-Check-Time-of-Use) race condition between symlink validation and file creation. The os.open() call used to create files does not use O_NOFOLLOW, allowing an attacker to create a symlink between the initial stat check and the actual file open, causing the write to follow the symlink to an arbitrary destination. Version 0.47.2 fixes the issue.
CVE-2026-54055
This medium-severity CVE scores 5.0 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.1%, top 100% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).
- Lower severity and no public exploit yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 5.0
- EG Score
- 5.0(medium)
- EG Risk
- 27(Track)EG Risk 27/100SSVC: Track
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computedSeverity50% × 45%Exploitation0% × 40%Automatability30% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- 0%
- EPSS %ILE
- 0%
- KEV
- Not listed
Published
June 12, 2026
Last Modified
June 16, 2026
Advisory Details (1)
Auto-updated Jun 15, 2026Arbitrary File Write via Symlink Race Condition in File Transmission Protocol · Advisory · kovidgoyal/kitty · GitHub
https://github.com/kovidgoyal/kitty/security/advisories/GHSA-q446-x7q6-vcxhAffected Packages
(4 across 4 ecosystems)
Debian:11(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| kitty | 0.19.3-1 ... 0.48.2-1 (47 versions) | — | — |
Debian:12(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| kitty | 0.26.5-5 ... 0.48.2-1 (39 versions) | — | — |
Debian:13(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| kitty | 0.41.1-2 ... 0.48.2-1 (16 versions) | — | — |
Debian:14(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| kitty | 0.41.1-2 ... 0.47.0-3 (12 versions) | 0.47.3-1 | — |
Weakness Classification(3)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 6× in last 7d / 19× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
- 2026-08-25 13:49 UTCEPSS rescore
- 2026-08-24 23:44 UTCEG score recompute
- 2026-08-23 09:59 UTCEG score recompute
- 2026-08-23 00:19 UTCEPSS rescore
- 2026-08-20 12:31 UTCEG score recompute
- 2026-08-19 17:04 UTCEPSS rescore
- 2026-08-15 23:36 UTCEG score recompute
- 2026-08-09 12:01 UTCEG score recompute
- 2026-08-08 16:37 UTCEPSS rescore
- 2026-08-06 17:56 UTCEG score recompute
- 2026-08-06 13:47 UTCEPSS rescore
- 2026-08-05 19:55 UTCEG score recompute
- 2026-08-05 19:17 UTCEPSS rescore
- 2026-08-02 07:16 UTCEG score recompute
- 2026-08-02 02:27 UTCEPSS rescore
- 2026-08-01 09:14 UTCEG score recompute
- 2026-08-01 04:16 UTCEPSS rescore
- 2026-07-31 04:38 UTCEG score recompute
- 2026-07-30 16:28 UTCEPSS rescore
- 2026-07-26 20:31 UTCEG score recompute
- 2026-07-26 14:54 UTCEPSS rescore
- 2026-07-24 14:18 UTCEPSS rescore
- 2026-07-23 03:19 UTCEG score recompute
- 2026-07-22 14:08 UTCEPSS rescore
- 2026-07-21 15:25 UTCEPSS rescore
Show 23 moreShow fewer
- 2026-07-18 10:04 UTCEPSS rescore
- 2026-07-11 08:27 UTCEPSS rescore
- 2026-07-11 08:27 UTCEPSS rescore
- 2026-07-08 15:16 UTCEPSS rescore
- 2026-07-08 15:16 UTCEPSS rescore
- 2026-07-07 13:46 UTCEPSS rescore
- 2026-07-07 13:46 UTCEPSS rescore
- 2026-07-06 02:23 UTCEPSS rescore
- 2026-07-06 02:23 UTCEPSS rescore
- 2026-07-01 15:07 UTCEPSS rescore
- 2026-06-28 04:56 UTCEPSS rescore
- 2026-06-28 04:56 UTCEPSS rescore
- 2026-06-27 03:08 UTCEPSS rescore
- 2026-06-25 13:49 UTCEPSS rescore
- 2026-06-17 17:53 UTCEPSS rescore
- 2026-06-16 17:53 UTCEPSS rescore
- 2026-06-15 17:49 UTCEPSS rescore
- 2026-06-15 17:49 UTCEPSS rescore
- 2026-06-14 23:18 UTCEPSS rescore
- 2026-06-13 23:00 UTCEPSS rescore
- 2026-06-12 23:12 UTCEPSS rescore
- 2026-06-12 22:15 UTCEG score recompute
- 2026-06-12 22:13 UTCNVD updatefirst tracked
Related CVEs(same CWE)
Frequently asked(5)
What is CVE-2026-54055?
When was CVE-2026-54055 disclosed?
Is CVE-2026-54055 actively exploited?
What is the CVSS score of CVE-2026-54055?
How do I remediate CVE-2026-54055?
Dependency Blast Radius
See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-54055
Is Your Infrastructure Affected by CVE-2026-54055?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.