Loading vulnerability…
The MHTML protocol handler in Microsoft Outlook Express 5.5 SP2 through 6 SP1 allows remote attackers to bypass domain restrictions and execute arbitrary code. This is achieved by leveraging script execution in a compiled help (CHM) file that references InfoTech Storage (ITS) protocol handlers such as ms-its, ms-itss, its, or mk:@MSITStore. The vulnerability, also known as the 'MHTML URL Processing Vulnerability,' enables attackers to execute code in the context of the user running Outlook Express or Internet Explorer, bypassing normal domain-based security restrictions.
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 valid public exploits. Mallory filtered out 3 candidates as fakes, detection scripts, or README-only repos.
All candidate exploits were filtered out by Mallory's validation.
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.
No public activity tracked yet. Mallory keeps watching.
No public activity observed for this vulnerability.
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.