LiveActive security incident?Get immediate response
CVE Record

CVE-2022-41322: In Kitty before 0.26.2, insufficient validation in the desktop notification escape sequence can lead to arb...

In Kitty before 0.26.2, insufficient validation in the desktop notification escape sequence can lead to arbitrary code execution. The user must display attacker-controlled content in the terminal, then click on a notification popup.

HighCVSS 7.8Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

Kitty terminal versions before 0.26.2 can mishandle desktop notification data. If a user displays attacker-controlled terminal content and then clicks the resulting notification popup, arbitrary code execution may occur. This is most urgent for developer and administrator workstations using Kitty.

Executive priority

Treat as a high-priority workstation patch, especially for technical staff. The issue needs user interaction, but successful exploitation could execute code with serious business impact on developer or administrator machines.

Technical view

CVE-2022-41322 is an insufficient validation issue in Kitty's desktop notification escape sequence handling, categorized as CWE-116. The CVSS 3.1 score is 7.8 with local attack vector, no privileges required, user interaction required, and high confidentiality, integrity, and availability impact.

Likely exposure

Exposure is likely limited to systems running Kitty before 0.26.2 where users may display attacker-controlled content in the terminal. The source bundle does not identify broader affected products or CPEs.

Exploitation context

The provided sources do not show CISA KEV listing or cited active exploitation. Successful exploitation requires user interaction: attacker-controlled terminal content must be displayed, and the user must click a notification popup.

Researcher notes

Primary evidence points to Kitty before 0.26.2 and a fix in the upstream commit and release comparison. The bundle does not provide exploit proof, active exploitation evidence, or complete affected package version ranges for every distribution.

Mitigation direction

  • Upgrade Kitty to version 0.26.2 or later where available.
  • Apply relevant distribution security updates from Gentoo, Fedora, or Debian LTS.
  • Prioritize developer and administrator endpoints using Kitty.
  • Avoid clicking terminal-triggered notifications from untrusted content until patched.
  • Check vendor and distribution advisories for exact package status.

Validation and detection

  • Inventory endpoints for installed Kitty versions below 0.26.2.
  • Confirm package manager updates include the CVE-2022-41322 fix.
  • Review Gentoo, Fedora, and Debian advisories for applicable fleets.
  • Verify scanner findings clear after upgrading Kitty.
  • Check workstation build images for vulnerable Kitty packages.
Prepared
Confidence
high
Sources
9

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · medium confidence lookup

CWE-116: User-session and phishing behavior lookup

Client-side and session-facing weaknesses should be reviewed alongside initial-access and user-execution behaviors. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
description · low confidence lookup

Execution behavior lookup

The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2022-41322 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
High
CVSS
7.8 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
0Timeline events
0ADP providers
9Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
7.8CVSS 3.1HighCVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H1.85.9Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

7.8High
CVSS 3.1 vector shape for CVE-2022-41322Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
n/an/an/aListed
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-116 · source CWE mapping

Improper Encoding or Escaping of Output

Improper Encoding or Escaping of Output represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.