CVE-2026-95832

CRITICALPre-NVD 9.39.3
EchelonGraph scoreMEDIUM confidence

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

This critical-severity CVE scores 9.3 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.2% (5th 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-87065 (ENISA EUVD) · GHSA-hvwf-v5fx-xvj6 (GitHub Security Advisories)Source: ENISA EUVD

9.3EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.2%CVSS: 9.3Exploit: 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 Neutralization of Special Elements in Output Used by a Downstream Component in the colour control escape code handler in kitty from 0.47.3 before 0.49.0 allows a program writing to the terminal to execute an arbitrary command in the user's shell, because color_control() in kitty/window.py answers a query for an unrecognised field name by placing that field name into the reply, and write_escape_code_to_child() in kitty/screen.c then writes the reply to the pseudoterminal master, where it is not distinguishable from input typed by the user, without neutralising it for the shell that reads it. The payload is reduced to printable ASCII before the field name is echoed, which is the restriction introduced in 0.47.3 as the fix for CVE-2026-54057, and the record and field separators ; and = are consumed as delimiters, but every other printable character survives, which is sufficient to compose a shell command. A newline is available from handle_remote_ssh() in kitty/window.py, which writes the bytes yielded by get_ssh_data() in kittens/ssh/utils.py, the first of which begin with a newline, to the pseudoterminal master before any credential carried in the request is checked. The reply is framed as an OSC sequence carrying the escape code number, the field name, and the literal value ?. This results in execution of an attacker-chosen command with the privileges of the user running the terminal.

CVSS
9.3
EG Score
9.3CRITICALmedium confidence
EG Risk
42
EG Risk 42/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)
Severity93% × 45%
Impact severity (EG Severity): CVSS 9.3 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 low or medium mission impact; Track* at high (mission-essential systems).
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (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
5th
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 (9.3): severity, escalated by confirmed exploitation. This CVE's 9.3 is its impact severity (EG Severity), not escalated.

EG Severity
9.3 CRITICALCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.a secondary CVSS source
EG Likelihood
0.2% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-11-20). 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 low or medium mission impact; Track* at high (mission-essential systems).CISA BOD 26-04: 14 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 low or medium mission impact; Track* at high (mission-essential systems).

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

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (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)14 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 total (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 (5)

Auto-updated Oct 3, 2026
Patch available. Sources: github_commit, github_release.
Web page

CVE-2026-95832 · Reflected unknown field names in the kitty colour control escape code allow command execution in the user's shell | Vulnerabilities published by Secur0

https://secur0.com/en/cna/cve-list/cve-2026-95832-kitty-color-control-command-execution
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 57bb144d96c0 (kovidgoyal/kitty)

Fix landed in kovidgoyal/kitty commit 57bb144d96c0 — awaiting tagged release

https://github.com/kovidgoyal/kitty/commit/57bb144d96c0f9d48a2b0a6d43c9a23d2a091cbf
GitHub commit

commit 03fbdad85549 (kovidgoyal/kitty)

Fix landed in kovidgoyal/kitty commit 03fbdad85549 — awaiting tagged release

https://github.com/kovidgoyal/kitty/commit/03fbdad855490470233954bc810e517027e5e640

Vendor Advisories for CVE-2026-95832(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 13× in last 7d / 59× 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 its CVE.org record (CNA or CISA ADP). An arrow marks a change the record states ("CVSS → 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). "EchelonGraph re-scored" is our own recompute of this CVE's score, not an update from a source, and is not counted in the refreshes above. Most recent first.

Showing the most recent 100 of 253 rows on record for this CVE.

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. None are among the latest 100 rows. The 153 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-11-21 16:42 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  2. 2026-11-21 15:17 UTCEchelonGraph re-scored
  3. 2026-11-21 15:17 UTCGHSA enrichmentGHSA-hvwf-v5fx-xvj6 · GitHub severity CRITICAL
  4. 2026-11-20 16:39 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  5. 2026-11-20 14:29 UTCEchelonGraph re-scored
  6. 2026-11-20 14:29 UTCGHSA enrichmentGHSA-hvwf-v5fx-xvj6 · GitHub severity CRITICAL
  7. 2026-11-19 16:36 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  8. 2026-11-19 13:41 UTCEchelonGraph re-scored
  9. 2026-11-19 13:41 UTCGHSA enrichmentGHSA-hvwf-v5fx-xvj6 · GitHub severity CRITICAL
  10. 2026-11-18 16:36 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  11. 2026-11-18 12:53 UTCEchelonGraph re-scored
  12. 2026-11-18 12:53 UTCGHSA enrichmentGHSA-hvwf-v5fx-xvj6 · GitHub severity CRITICAL
  13. 2026-11-17 16:36 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  14. 2026-11-17 12:06 UTCEchelonGraph re-scored
  15. 2026-11-17 12:06 UTCGHSA enrichmentGHSA-hvwf-v5fx-xvj6 · GitHub severity CRITICAL
  16. 2026-11-16 16:53 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  17. 2026-11-16 11:16 UTCEchelonGraph re-scored
  18. 2026-11-16 11:16 UTCGHSA enrichmentGHSA-hvwf-v5fx-xvj6 · GitHub severity CRITICAL
  19. 2026-11-15 17:04 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  20. 2026-11-15 10:27 UTCEchelonGraph re-scored
  21. 2026-11-15 10:27 UTCGHSA enrichmentGHSA-hvwf-v5fx-xvj6 · GitHub severity CRITICAL
  22. 2026-11-14 16:42 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  23. 2026-11-14 09:33 UTCEchelonGraph re-scored
  24. 2026-11-14 09:33 UTCGHSA enrichmentGHSA-hvwf-v5fx-xvj6 · GitHub severity CRITICAL
  25. 2026-11-13 16:58 UTCEPSS rescoreEPSS 0.2% · 5th percentile
Show 75 more
  1. 2026-11-13 08:44 UTCEchelonGraph re-scored
  2. 2026-11-13 08:44 UTCGHSA enrichmentGHSA-hvwf-v5fx-xvj6 · GitHub severity CRITICAL
  3. 2026-11-12 16:35 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  4. 2026-11-12 07:56 UTCEchelonGraph re-scored
  5. 2026-11-12 07:56 UTCGHSA enrichmentGHSA-hvwf-v5fx-xvj6 · GitHub severity CRITICAL
  6. 2026-11-11 16:41 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  7. 2026-11-11 07:08 UTCEchelonGraph re-scored
  8. 2026-11-11 07:08 UTCGHSA enrichmentGHSA-hvwf-v5fx-xvj6 · GitHub severity CRITICAL
  9. 2026-11-10 16:46 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  10. 2026-11-10 06:18 UTCEchelonGraph re-scored
  11. 2026-11-10 06:18 UTCGHSA enrichmentGHSA-hvwf-v5fx-xvj6 · GitHub severity CRITICAL
  12. 2026-11-09 16:36 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  13. 2026-11-09 05:30 UTCEchelonGraph re-scored
  14. 2026-11-09 05:30 UTCGHSA enrichmentGHSA-hvwf-v5fx-xvj6 · GitHub severity CRITICAL
  15. 2026-11-08 16:41 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  16. 2026-11-08 04:43 UTCEchelonGraph re-scored
  17. 2026-11-08 04:43 UTCGHSA enrichmentGHSA-hvwf-v5fx-xvj6 · GitHub severity CRITICAL
  18. 2026-11-07 16:40 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  19. 2026-11-07 03:55 UTCEchelonGraph re-scored
  20. 2026-11-07 03:55 UTCGHSA enrichmentGHSA-hvwf-v5fx-xvj6 · GitHub severity CRITICAL
  21. 2026-11-06 22:55 UTCOSV refresh
  22. 2026-11-06 16:40 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  23. 2026-11-06 03:08 UTCEchelonGraph re-scored
  24. 2026-11-06 03:08 UTCGHSA enrichmentGHSA-hvwf-v5fx-xvj6 · GitHub severity CRITICAL
  25. 2026-11-05 16:39 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  26. 2026-11-05 02:21 UTCEchelonGraph re-scored
  27. 2026-11-05 02:21 UTCGHSA enrichmentGHSA-hvwf-v5fx-xvj6 · GitHub severity CRITICAL
  28. 2026-11-04 16:37 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  29. 2026-11-04 01:33 UTCEchelonGraph re-scored
  30. 2026-11-04 01:33 UTCGHSA enrichmentGHSA-hvwf-v5fx-xvj6 · GitHub severity CRITICAL
  31. 2026-11-03 16:49 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  32. 2026-11-03 00:45 UTCEchelonGraph re-scored
  33. 2026-11-03 00:45 UTCGHSA enrichmentGHSA-hvwf-v5fx-xvj6 · GitHub severity CRITICAL
  34. 2026-11-02 16:46 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  35. 2026-11-01 23:57 UTCEchelonGraph re-scored
  36. 2026-11-01 23:57 UTCGHSA enrichmentGHSA-hvwf-v5fx-xvj6 · GitHub severity CRITICAL
  37. 2026-11-01 16:36 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  38. 2026-10-31 23:09 UTCEchelonGraph re-scored
  39. 2026-10-31 23:09 UTCGHSA enrichmentGHSA-hvwf-v5fx-xvj6 · GitHub severity CRITICAL
  40. 2026-10-31 16:33 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  41. 2026-10-30 22:22 UTCEchelonGraph re-scored
  42. 2026-10-30 22:22 UTCGHSA enrichmentGHSA-hvwf-v5fx-xvj6 · GitHub severity CRITICAL
  43. 2026-10-30 16:35 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  44. 2026-10-29 21:34 UTCEchelonGraph re-scored
  45. 2026-10-29 21:34 UTCGHSA enrichmentGHSA-hvwf-v5fx-xvj6 · GitHub severity CRITICAL
  46. 2026-10-29 16:34 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  47. 2026-10-28 20:47 UTCEchelonGraph re-scored
  48. 2026-10-28 20:46 UTCGHSA enrichmentGHSA-hvwf-v5fx-xvj6 · GitHub severity CRITICAL
  49. 2026-10-28 16:33 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  50. 2026-10-27 19:57 UTCEchelonGraph re-scored
  51. 2026-10-27 19:57 UTCGHSA enrichmentGHSA-hvwf-v5fx-xvj6 · GitHub severity CRITICAL
  52. 2026-10-27 16:33 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  53. 2026-10-26 19:09 UTCEchelonGraph re-scored
  54. 2026-10-26 19:08 UTCGHSA enrichmentGHSA-hvwf-v5fx-xvj6 · GitHub severity CRITICAL
  55. 2026-10-26 16:33 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  56. 2026-10-25 16:36 UTCEchelonGraph re-scored
  57. 2026-10-25 16:36 UTCGHSA enrichmentGHSA-hvwf-v5fx-xvj6 · GitHub severity CRITICAL
  58. 2026-10-25 16:34 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  59. 2026-10-25 13:48 UTCEchelonGraph re-scored
  60. 2026-10-24 16:34 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  61. 2026-10-24 15:48 UTCEchelonGraph re-scored
  62. 2026-10-24 15:47 UTCGHSA enrichmentGHSA-hvwf-v5fx-xvj6 · GitHub severity CRITICAL
  63. 2026-10-23 16:33 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  64. 2026-10-23 14:56 UTCEchelonGraph re-scored
  65. 2026-10-23 14:56 UTCGHSA enrichmentGHSA-hvwf-v5fx-xvj6 · GitHub severity CRITICAL
  66. 2026-10-22 16:35 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  67. 2026-10-22 14:06 UTCEchelonGraph re-scored
  68. 2026-10-22 14:06 UTCGHSA enrichmentGHSA-hvwf-v5fx-xvj6 · GitHub severity CRITICAL
  69. 2026-10-21 16:34 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  70. 2026-10-21 13:15 UTCEchelonGraph re-scored
  71. 2026-10-21 13:14 UTCGHSA enrichmentGHSA-hvwf-v5fx-xvj6 · GitHub severity CRITICAL
  72. 2026-10-20 16:34 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  73. 2026-10-20 12:07 UTCEchelonGraph re-scored
  74. 2026-10-20 12:07 UTCGHSA enrichmentGHSA-hvwf-v5fx-xvj6 · GitHub severity CRITICAL
  75. 2026-10-19 16:33 UTCEPSS rescoreEPSS 0.2% · 4th percentile

Frequently asked(5)

What is CVE-2026-95832?
CVE-2026-95832 is a critical-severity vulnerability; its CVE record was published on September 25, 2026. Improper Neutralization of Special Elements in Output Used by a Downstream Component in the colour control escape code handler in kitty from 0.47.3 before 0.49.0 allows a program writing to the terminal to execute an arbitrary command in the user's shell, because color_control() in kitty/window.py…
When was CVE-2026-95832 made public?
CVE-2026-95832 was made public on September 25, 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-95832 actively exploited?
CVE-2026-95832 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.2% probability of exploitation in the next 30 days (5th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-95832?
CVE-2026-95832 has a CVSS base score of 9.3 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-95832?
A fix for CVE-2026-95832 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-95832 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-95832

Explore →

Is Your Infrastructure Affected by CVE-2026-95832?

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