Loading vulnerability…
CVE-2026-21436 is a directory traversal vulnerability in the Python-based Solus eopkg package manager before version 4.4.0. A malicious package can cause files installed with the --destdir option to be written outside the specified destination directory and into another location on the host.
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 demonstrates a proof-of-concept exploit for CVE-2026-21436, a directory traversal vulnerability in the Solus OS eopkg package manager (<= 4.3.4). The exploit consists of a Python script (archiveCreator.py) that creates a malicious tar.xz archive containing a file (hello.txt) with a directory traversal path. When this archive is included in a .eopkg package and installed, eopkg extracts the file to an arbitrary location (e.g., /tmp/hello.txt) on the filesystem, even when the --destdir parameter is used. The exploit leverages the lack of path sanitization in eopkg's extraction process. The repository includes a README.md with detailed instructions, the exploit script, and a sample payload file. The main attack vector is local, requiring the attacker to supply a malicious package to the target system. No network endpoints are involved; the exploit targets the file system via crafted archive paths.
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.