Skip to main content
Mallory
MediumVulnerability

CVE-2020-1599: Windows Authenticode Spoofing via Embedded HTA Content

Published Nov 11, 2020 · Updated 1 month ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 daysNo mention activity in the last 30 days.
CVSS5.5Medium · v3.1
EPSS19.1%97th percentile
CISA KEVNoNot listed
In the wildReported2 exploitation records in Mallory
Vendor
Microsoft Corporation
IdentifiersCVE-2020-1599CWE-347

CVE-2020-1599 is a Windows spoofing vulnerability involving improper verification of signed files, allowing attacker-controlled script content to be embedded within another file format while the file continues to appear validly signed. Reported abuse shows adversaries appending HTA/script content to signed Windows DLLs and then invoking that content through mshta.exe, effectively hiding malicious logic inside files that retain trust indicators associated with Authenticode-signed content. The weakness is closely associated with a gap in signature validation that permits additional content in the certificate or signature padding area without invalidating trust decisions, enabling execution of embedded HTA content from ostensibly legitimate signed files.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Analyst brief

Impact, mitigation & remediation

What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

Successful exploitation enables defense evasion and trust abuse by allowing malicious script content to masquerade as part of a validly signed Windows file. This can reduce user suspicion, weaken security control effectiveness, and facilitate execution of follow-on malware. In observed intrusion chains, the vulnerability was used to launch malicious scripts that staged additional payloads, injected malware into trusted processes, and supported broader compromise activity.

Mitigation

If you can’t patch tonight, do this now.

Enable strict Authenticode padding verification where operationally feasible, and use application control such as Windows Defender Application Control in enforcement mode to block HTA execution paths. Restrict or disable mshta.exe where not required, monitor for rundll32.exe invocation of RunHTMLApplication, and alert on signed files being used as containers for script execution. Additional mitigations include constraining script execution, monitoring loads of mshtml.dll and script-engine components in unusual contexts, and treating signed files with appended content as suspicious.

Remediation

Patch, then assume compromise.

Apply Microsoft security updates addressing CVE-2020-1599 and ensure Windows systems are configured to enforce stricter Authenticode verification behavior where supported. Review trust and application-control policies so that signed status alone is not treated as sufficient evidence of safety, especially for script-capable content embedded in nonstandard containers. Validate that endpoint protection, EDR, and application-control policies are updated to detect or block execution chains involving signed files used as script carriers.

Public exploits

Exploits

No public exploits tracked yet. Mallory keeps watching.

View more in app →
No public exploit code observed for this vulnerability. Mallory keeps watching.
Exposure surface

Affected products & vendors

Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.

VendorProductType
Microsoft CorporationWindows 10operating_system
Microsoft CorporationWindows 7operating_system
Microsoft CorporationWindows 8.1operating_system
Microsoft CorporationWindows Rt 8.1operating_system
Microsoft CorporationWindows Server 2008operating_system
Microsoft CorporationWindows Server 2012operating_system
Microsoft CorporationWindows Server 2016operating_system
Microsoft CorporationWindows Server 2019operating_system
FAQ

Frequently asked questions

Is CVE-2020-1599 exploited in the wild?
Yes. As of Oct 16, 2026, Mallory has reports of exploitation in the wild.
Is there a public exploit for CVE-2020-1599?
As of Oct 16, 2026, Mallory has found no public exploit for CVE-2020-1599.
Is there a patch for CVE-2020-1599?
Apply Microsoft security updates addressing CVE-2020-1599 and ensure Windows systems are configured to enforce stricter Authenticode verification behavior where supported. Review trust and application-control policies so that signed status alone is not treated as sufficient evidence of safety, especially for script-capable content embedded in nonstandard containers.
What products are affected by CVE-2020-1599?
Microsoft Corporation Windows 10, Microsoft Corporation Windows 7, Microsoft Corporation Windows 8.1, Microsoft Corporation Windows Rt 8.1, Microsoft Corporation Windows Server 2008, and 3 more.
How severe is CVE-2020-1599?
CVE-2020-1599 has a CVSS v3.1 score of 5.5 (Medium) and an EPSS score of 19.1% (97th percentile) as of Oct 16, 2026.
Activity feed

Recent activity

6 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.

View more in app →
+2 more in the timeline. Sign up to see them
Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Mallory platform

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, and which detections to deploy tonight.
Exposure mappingQuery your assets running an affected version, and investigate the blast radius.
Threat actor evidenceEvery report linking this CVE to a named adversary.
Associated malware2Malware families linked to this CVE, with evidence and IOCs.
Detection signaturesYARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Vendor-by-vendor mappingCross-references every affected SKU, including bundled OEM variants.
Social activityCommunity discussion across Reddit, Mastodon, and other social sources.