Loading vulnerability…
CVE-2026-42473 is an unsafe deserialization vulnerability in MixPHP Framework 2.x through 2.2.17. According to the provided content, the flaw is in the session and cache handling logic, where the FileHandler object uses PHP's native unserialize() on data read from the filesystem without integrity verification or class restrictions. The broader disclosure characterizes this as a direct unserialize($input) pattern on untrusted data across MixPHP deserialization paths. Because PHP object deserialization can invoke gadget chains present in the application or its dependencies, attacker-controlled serialized data can be turned into code execution on the application server.
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.
8 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.