Loading vulnerability…
CVE-2025-43929 affects kitty before version 0.41.0. The issue is in open_actions.py, which does not require explicit user confirmation before running a local executable file when that file is opened via a link originating from an untrusted document, such as a document opened in KDE ghostwriter. This creates a trust-boundary failure in which content from an untrusted document can trigger execution of a local executable without an adequate confirmation step.
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
1 valid exploit after Mallory filtered fakes, detection scripts, and README-only repos.
This repository provides a proof-of-concept (POC) exploit for CVE-2025-43929, a high-severity local origin validation vulnerability in KiTTY (prior to version 0.41.0). The vulnerability allows local executables to be run without user confirmation if linked from an untrusted document, such as one opened in KDE ghostwriter. The main exploit file is a Bash script ('CVE-2025-43929-POC/test') that demonstrates arbitrary code execution by running 'whoami' and then exfiltrating data via a curl request to 'httpbin.org/get'. The repository also includes a README.md with a detailed description of the vulnerability and a markdown file ('test.md') referencing the exploit script. The exploit is a simple POC and does not include weaponized or customizable payloads. The only fingerprintable endpoint is the use of 'httpbin.org/get' for exfiltration demonstration.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
4 sources tracked across advisories and community write-ups. News coverage will land here when it surfaces.
No news coverage yet. Advisories and community discussion only.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.