CVE-2026-0014 is an improper input-validation vulnerability in the isPackageNullOrSystem method of Android AppOpsService.java. A local attacker can supply input that causes a persistent denial-of-service condition.
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 three-file repository contains a standalone Python proof of concept for an InputLeap drag-and-drop path traversal flaw (CWE-22), tested against InputLeap v3.0.3 and described as affecting versions where --enable-drag-drop is enabled. The README explains that DragInformation::parseDragInfo uses a global separator heuristic and fails to handle find_last_of() returning npos; unsigned arithmetic then preserves a backslash-based traversal path when a stray forward slash is embedded elsewhere in the metadata. DropHelper::writeToDir subsequently concatenates that unsanitized path with the drop directory without canonicalization. The sole code file, input-leap-directory-traversal-poc.py, implements InputLeap protocol packet construction, outer length framing, optional TLS client-identity generation/fingerprinting, a plaintext mode for crypto-disabled servers, and transfer of a hard-coded marker payload. Default execution demonstrates escaping one directory; an optional Windows Startup-path demonstration shows the persistence/RCE impact if an executable were transferred. .gitignore excludes generated TLS certificate material. No established exploit framework is used.
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, community write-ups, and news. New activity surfaces here as Mallory finds it.
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.