CVE-2026-80430

MEDIUMPre-NVD 4.64.6
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to the CVSS score beside it.

This medium-severity CVE scores 4.6 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.2% (4th percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.

Triggered by: Headline CVSS from a secondary CVSS source
Sources: EPSS, a secondary CVSS source

Also known asEUVD-2026-87063 (ENISA EUVD) · GHSA-phg7-mgrc-j9pj (GitHub Security Advisories)Source: ENISA EUVD

4.6EG
EchelonGraph verdictMonitorRemediate within your standard update timelines (the SSVC decision on this page).
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0.2%CVSS: 4.6Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

Fixed versions, as the CVE record's CNA (Secur0) states them: "Upgrade to kitty 0.49.0 or later."

Improper Link Resolution Before File Access in the drag source staging path of the drag and drop protocol in kitty from 0.47.0 before 0.49.0 allows a program writing to the terminal to create files and directories at paths outside the staging directory, because subdir_data_for_drag() in kitty/dnd.c resolves a descendant of the staged item tree by constructing a path string and opening it with safe_open(path, O_DIRECTORY | O_RDONLY, 0) rather than by walking the tree one component at a time, so a client that declares two entries with the same name, the first a symlink whose target is an arbitrary absolute path and the second a directory, causes mkdirat() to fail with EEXIST, which the code ignores, and causes the subsequent path resolution to follow the symlink and return a directory descriptor outside the staging directory, which is then passed as the dirfd argument to add_payload() and used for every further create operation on that item and its descendants. Entry names are sanitised against path separators and dot components, but symlink targets are not validated. Files are created with O_CREAT | O_WRONLY | O_EXCL at mode 0644, so existing files cannot be overwritten, and directories are created with mkdirat() at mode 0755, so the attacker can create intermediate directories that did not previously exist. This results in the creation of files and directories at any path writable by the user running kitty, provided the symlink target is an existing directory.

CVSS v3
4.6
EG Score
4.6MEDIUMmedium confidence
EG Risk
21
EG Risk 21/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity46% × 45%
Impact severity (EG Severity): CVSS 4.6 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.2% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at every mission impact level.
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines.
EPSS PROB
0.2%
EPSS %ILE
4th
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (4.6): severity, escalated by confirmed exploitation. This CVE's 4.6 is its impact severity (EG Severity), not escalated.

EG Severity
4.6 MEDIUMCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.a secondary CVSS source · CVSS v3.0 or v3.1
EG Likelihood
0.2% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-24). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at every mission impact level.CISA BOD 26-04: 60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at every mission impact level.

A fix is available. Apply it within your standard update timelines.

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

September 25, 2026

Last Modified

September 29, 2026

Advisory Details (4)

Auto-updated Sep 25, 2026
Patch available. Sources: github_commit, github_release.
Web page

CVE-2026-80430 · Improper link resolution in the kitty drag and drop protocol allows a client to create files outside the staging directory | Vulnerabilities published by Secur0

https://secur0.com/en/cna/cve-list/cve-2026-80430-kitty-dnd-symlink-traversal
GitHub release Patch Available

version 0.49.0

Patch available: kovidgoyal/kitty v0.49.0

https://github.com/kovidgoyal/kitty/releases/tag/v0.49.0
GitHub commit

commit 3c3133d33992 (kovidgoyal/kitty)

Fix landed in kovidgoyal/kitty commit 3c3133d33992 — awaiting tagged release

https://github.com/kovidgoyal/kitty/commit/3c3133d3399257492347f535d8d191680803b25d
GitHub commit

commit 554908ed0b4d (kovidgoyal/kitty)

Fix landed in kovidgoyal/kitty commit 554908ed0b4d — awaiting tagged release

https://github.com/kovidgoyal/kitty/commit/554908ed0b4d010cf9821c75449c7f7c79a6170a

Vendor Advisories for CVE-2026-80430(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Affected Packages

(3 across 3 ecosystems)
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
kitty0.26.5-5 ... 0.48.2-1.1 (40 versions)
  • every version on: no fix on record
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
kitty0.41.1-2 ... 0.48.2-1.1 (18 versions)
  • every version on: no fix on record
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
kitty0.41.1-2 ... 0.48.2-1.1 (16 versions)
  • every version on: no fix on record
—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 8× in last 7d / 57× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. 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. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

  1. 2026-11-01 16:35 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  2. 2026-10-31 16:33 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  3. 2026-10-30 16:35 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  4. 2026-10-30 02:25 UTCOSV refresh
  5. 2026-10-29 16:34 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  6. 2026-10-28 16:33 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  7. 2026-10-27 16:32 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  8. 2026-10-26 16:32 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  9. 2026-10-25 16:34 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  10. 2026-10-25 13:59 UTCEG score recompute
  11. 2026-10-24 16:33 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  12. 2026-10-23 16:32 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  13. 2026-10-22 16:35 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  14. 2026-10-22 13:54 UTCEG score recompute
  15. 2026-10-22 13:54 UTCGHSA enrichmentGHSA-phg7-mgrc-j9pj
  16. 2026-10-21 16:33 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  17. 2026-10-20 16:33 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  18. 2026-10-18 16:33 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  19. 2026-10-18 03:10 UTCEG score recompute
  20. 2026-10-17 16:35 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  21. 2026-10-16 16:44 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  22. 2026-10-15 16:33 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  23. 2026-10-14 16:33 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  24. 2026-10-13 16:35 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  25. 2026-10-12 16:35 UTCEPSS rescoreEPSS 0.2% · 4th percentile
Show 59 more
  1. 2026-10-12 14:57 UTCEG score recompute
  2. 2026-10-11 19:21 UTCEG score recompute
  3. 2026-10-11 18:28 UTCGHSA enrichmentGHSA-phg7-mgrc-j9pj
  4. 2026-10-11 16:37 UTCEG score recompute
  5. 2026-10-11 13:55 UTCEG score recompute
  6. 2026-10-11 13:49 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  7. 2026-10-10 20:36 UTCEG score recompute
  8. 2026-10-10 20:36 UTCGHSA enrichmentGHSA-phg7-mgrc-j9pj
  9. 2026-10-10 20:00 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  10. 2026-10-09 22:44 UTCEG score recompute
  11. 2026-10-09 22:44 UTCGHSA enrichmentGHSA-phg7-mgrc-j9pj
  12. 2026-10-09 20:07 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  13. 2026-10-09 00:54 UTCEG score recompute
  14. 2026-10-09 00:54 UTCGHSA enrichmentGHSA-phg7-mgrc-j9pj
  15. 2026-10-08 17:13 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  16. 2026-10-08 03:04 UTCEG score recompute
  17. 2026-10-08 03:04 UTCGHSA enrichmentGHSA-phg7-mgrc-j9pj
  18. 2026-10-07 23:48 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  19. 2026-10-07 05:14 UTCEG score recompute
  20. 2026-10-07 05:14 UTCGHSA enrichmentGHSA-phg7-mgrc-j9pj
  21. 2026-10-06 15:18 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  22. 2026-10-06 07:24 UTCEG score recompute
  23. 2026-10-06 07:24 UTCGHSA enrichmentGHSA-phg7-mgrc-j9pj
  24. 2026-10-05 17:43 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  25. 2026-10-05 09:34 UTCEG score recompute
  26. 2026-10-05 09:34 UTCGHSA enrichmentGHSA-phg7-mgrc-j9pj
  27. 2026-10-04 23:22 UTCEPSS rescoreEPSS 0.2% · 3rd percentile
  28. 2026-10-04 11:44 UTCEG score recompute
  29. 2026-10-04 11:44 UTCGHSA enrichmentGHSA-phg7-mgrc-j9pj
  30. 2026-10-03 14:26 UTCEPSS rescoreEPSS 0.2% · 3rd percentile
  31. 2026-10-03 13:54 UTCEG score recompute
  32. 2026-10-03 13:54 UTCGHSA enrichmentGHSA-phg7-mgrc-j9pj
  33. 2026-10-02 17:57 UTCEPSS rescoreEPSS 0.2% · 3rd percentile
  34. 2026-10-02 16:03 UTCEG score recompute
  35. 2026-10-02 16:02 UTCGHSA enrichmentGHSA-phg7-mgrc-j9pj
  36. 2026-10-01 19:50 UTCEPSS rescoreEPSS 0.2% · 3rd percentile
  37. 2026-10-01 18:10 UTCGHSA enrichmentGHSA-phg7-mgrc-j9pj
  38. 2026-09-30 20:10 UTCEG score recompute
  39. 2026-09-30 20:10 UTCGHSA enrichmentGHSA-phg7-mgrc-j9pj
  40. 2026-09-30 15:04 UTCEPSS rescoreEPSS 0.2% · 3rd percentile
  41. 2026-09-29 22:21 UTCEG score recompute
  42. 2026-09-29 22:20 UTCGHSA enrichmentGHSA-phg7-mgrc-j9pj
  43. 2026-09-29 08:08 UTCEG score recompute
  44. 2026-09-29 08:08 UTCGHSA enrichmentGHSA-phg7-mgrc-j9pj
  45. 2026-09-28 13:52 UTCEPSS rescoreEPSS 0.2% · 3rd percentile
  46. 2026-09-28 10:15 UTCEG score recompute
  47. 2026-09-28 10:15 UTCGHSA enrichmentGHSA-phg7-mgrc-j9pj
  48. 2026-09-27 13:48 UTCEPSS rescoreEPSS 0.2% · 3rd percentile
  49. 2026-09-27 12:25 UTCEG score recompute
  50. 2026-09-27 12:25 UTCGHSA enrichmentGHSA-phg7-mgrc-j9pj
  51. 2026-09-26 15:59 UTCEPSS rescoreEPSS 0.2% · 3rd percentile
  52. 2026-09-26 14:35 UTCGHSA enrichmentGHSA-phg7-mgrc-j9pj
  53. 2026-09-25 16:27 UTCEG score recompute
  54. 2026-09-25 16:27 UTCGHSA enrichmentGHSA-phg7-mgrc-j9pj
  55. 2026-09-25 15:36 UTCEG score recompute
  56. 2026-09-25 15:36 UTCGHSA enrichmentGHSA-phg7-mgrc-j9pj
  57. 2026-09-25 14:23 UTCEG score recompute
  58. 2026-09-25 13:19 UTCEG score recomputeFirst assessed: 4.6 MEDIUM
  59. 2026-09-25 13:19 UTCMITRE cvelistV5first tracked

Related CVEs(same product + same CWE)

Frequently asked(5)

What is CVE-2026-80430?
CVE-2026-80430 is a medium-severity vulnerability; its CVE record was published on September 25, 2026. Improper Link Resolution Before File Access in the drag source staging path of the drag and drop protocol in kitty from 0.47.0 before 0.49.0 allows a program writing to the terminal to create files and directories at paths outside the staging directory, because subdir_data_for_drag() in kitty/dnd.c…
When was CVE-2026-80430 made public?
CVE-2026-80430 was made public on September 21, 2026: that is the date its CVE record's CNA, Secur0, gives for when the vulnerability was made public. The CVE record itself was published on September 25, 2026. EchelonGraph's copy of the record carries a last-modified date of September 29, 2026; the record at its source may have been updated since.
Is CVE-2026-80430 actively exploited?
CVE-2026-80430 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.2% probability of exploitation in the next 30 days (4th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-80430?
CVE-2026-80430 has a CVSS base score of 4.6 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-80430?
A fix for CVE-2026-80430 is available: update to the fixed version the vendor names in its advisory. Fixed versions, as the CVE record's CNA (Secur0) states them: "Upgrade to kitty 0.49.0 or later." The vendor advisories EchelonGraph has for CVE-2026-80430 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-80430

Explore →

Is Your Infrastructure Affected by CVE-2026-80430?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Book a Demo →Browse All CVEs