CVE-2018-8495 is a remote code execution vulnerability in Windows Shell caused by improper handling of URIs. It affects Windows Server 2016, Windows 10, and Windows 10 Servers.
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 is a proof-of-concept (POC) exploit for CVE-2018-8495, a remote code execution vulnerability in Microsoft Edge. The repository contains two files: a README.md describing the exploit and a poc.html file implementing the exploit. The HTML file uses a crafted <a> tag with a 'wshfile:' protocol handler and a relative file path to a .vbs script, attempting to trigger execution of the Windows Calculator (calc.exe) when the user interacts with the page (via a keydown event). The exploit demonstrates the vulnerability by leveraging browser handling of the WSH file protocol to achieve code execution. The main fingerprintable endpoint is the file path '../../WinSxS/AMD921~1.48_/SyncAppvPublishingServer.vbs' referenced in the exploit. The code is a simple POC and does not include advanced payloads or customization.
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.