Loading vulnerability…
CVE-2026-4878 is a local privilege escalation vulnerability in libcap affecting cap_set_file() in libcap/cap_file.c. The flaw is a time-of-check-to-time-of-use race condition caused by validating a pathname with lstat() and later modifying file capabilities on that pathname with setxattr() or removexattr(). Because lstat() does not follow symlinks while the later extended-attribute operations do, an attacker with write access to the parent directory can swap the checked file with a symlink or another file between the check and use phases, redirecting the capability update to an unintended target. This can result in file capabilities being injected into an attacker-controlled executable or removed from another executable. The issue is reported to affect libcap releases from 2.04 through 2.77 and was fixed in libcap 2.78. The setcap utility is identified as the primary attack surface because it directly invokes cap_set_file() on user-supplied paths.
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.
No public exploits tracked yet. Mallory keeps watching.
No public exploit code observed for this vulnerability.
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.
13 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.