CVE-2026-95834

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.1% (2nd 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-87233 (ENISA EUVD) · GHSA-3v4f-mq3r-g3gv (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.1%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."

Use After Free in the drag source 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 cause the terminal to read from and write to freed heap memory, because drag_remote_file_data() in kitty/dnd.c holds a DragRemoteItem pointer into an array it does not own, calls toplevel_data_for_drag() or subdir_data_for_drag(), and then continues to use that pointer. Those helpers, and add_payload() and populate_dir_entries() which they call, report errors through the abrt() macro, which expands to cancel_drag() followed by a plain return, and cancel_drag() calls drag_free_offer(), which frees the array the pointer refers to. The helpers return void, so the caller receives no indication that the teardown happened, and proceeds to call all_children_complete() on the freed pointer, which dereferences it, and then to write through it. That dereference is guarded by a local flag that is set when the request carries no payload and announces no further data, which is the same condition that selects the finalisation block of add_payload(), so the error paths in that block reach it: a create that fails because an entry of the same name already exists, because the client may declare two entries with one name and the create operations use O_CREAT with O_EXCL and symlinkat(), a mkdirat() failure other than EEXIST, and the directory entry allocation paths. Both branches reach it. In the top level branch the caller's pointer is never cleared, so clearing the owning structure's own pointers during teardown does not help. In the sub directory branch subdir_data_for_drag() sets the caller's pointer to NULL on entry and assigns it only after its own last error path, so its own aborts leave the caller with NULL and are stopped by a null check, but it then calls add_payload() with that pointer set, and an abort there leaves the caller holding a freed child node inside the item tree, which drag_free_offer() frees by recursion. This results in undefined behaviour in the terminal process, reachable from the byte stream of any program running in the window.

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.1% × 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.1%
EPSS %ILE
2nd
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.1% 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 (3)

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

cve-2026-95834 · Use after free in the kitty drag and drop protocol when a drag source item is aborted mid-transfer | Vulnerabilities published by Secur0

https://secur0.com/en/cna/cve-list/cve-2026-95834-kitty-dnd-use-after-free
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 b54bfbb4f85f (kovidgoyal/kitty)

Fix landed in kovidgoyal/kitty commit b54bfbb4f85f — awaiting tagged release

https://github.com/kovidgoyal/kitty/commit/b54bfbb4f85f992edca9b04f5c0c2612454eec23

Vendor Advisories for CVE-2026-95834(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 / 53× 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.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. 1 repeat row among the latest 78 is merged into the row it repeats.

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

Related CVEs(same product + same CWE)

Frequently asked(5)

What is CVE-2026-95834?
CVE-2026-95834 is a medium-severity vulnerability; its CVE record was published on September 25, 2026. Use After Free in the drag source 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 cause the terminal to read from and write to freed heap memory, because drag_remote_file_data() in kitty/dnd.c holds a DragRemoteItem pointer into an…
When was the CVE record for CVE-2026-95834 published?
The CVE record for CVE-2026-95834 was published on September 25, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. 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-95834 actively exploited?
CVE-2026-95834 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.1% probability of exploitation in the next 30 days (2nd percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-95834?
CVE-2026-95834 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-95834?
A fix for CVE-2026-95834 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-95834 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-95834

Explore →

Is Your Infrastructure Affected by CVE-2026-95834?

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

Book a Demo →Browse All CVEs