What it is
Protection mechanism failure in MSHTML Framework allows an unauthorized attacker to bypass a security feature over a network.
Vulnerability report
MSHTML Framework Security Feature Bypass Vulnerability
Microsoft / Windows 10 Version 1607 · affected before 10.0.14393.8868
Decision summary
Direct answers before the deeper technical record.
What it is
Protection mechanism failure in MSHTML Framework allows an unauthorized attacker to bypass a security feature over a network.
Have exploitation attempts been observed?
Yes. Exploitation attempts have been reported for this vulnerability. Previdian lists it as a known exploited vulnerability. Listed in CISA KEV. Also reported by third-party sources. Confidence is confirmed.
Who is affected?
Affected products include Microsoft / Windows 10 Version 1607 and 22 other products, including affected before 10.0.14393.8868, affected before 10.0.17763.8389, and affected before 10.0.19044.6937.
What should we do?
Prioritize remediation. Validate affected assets and apply vendor fixes on an accelerated timeline.
Overview
Protection mechanism failure in MSHTML Framework allows an unauthorized attacker to bypass a security feature over a network.
Exploitation evidence
Third-party attestation and first-party sensor observation are shown separately so teams can judge the evidence chain.
CVE
A trusted third party reported exploitation attempts.
Per-source evidence links for KEV attestations are available through the Previdian Pro API.
Learn about Pro API access| Source | Added |
|---|---|
| CVE First | 2026-06-01 10:50 UTC |
| CISA | 2026-06-02 14:03 UTC |
| Tenable Blog | 2026-06-02 14:21 UTC |
Detection
Make the evidence actionable in scanner, SOC, and edge-control workflows.
No scanner integrations recorded yet.
No Previdian virtual patch is currently available. Future rules ship for ModSecurity, Cloudflare, and AWS WAF.
Learn about virtual patches →No detection artifacts or sensor request patterns are available for this CVE yet.
Check back as sensor telemetry and scanner integrations are updated.
Risk and context
CVSS v3.1
Potential damage if exploited. Separate from whether attackers are using it.
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H/E:U/RL:O/RC:C
EPSS
15.9%
Estimated chance of exploitation in the next 30 days. Previdian's warning comes from evidence, not this score.
Recent mention · Tenable Blog
Tenable Research has developed a graph-based model linking 600+ threat groups to real-world customer exposures. It reveals which vulnerabilities sit at the intersection of severity, active exploitation, and organizational risk.Key takeawaysThe "patch everything" strategy is...
Read full advisoryRecent mention · Tenable Blog
Inside the customer environment: Where threat actors, vulnerabilities, and exposed assets intersectTenable Blog · 27 May 2026
Tenable Research has developed a graph-based model linking 600+ threat groups to real-world customer exposures. It reveals which vulnerabilities sit at the intersection of severity, active exploitation, and organizational risk.Key takeawaysThe "patch everything" strategy is dead: Vulnerability prioritization based on exploitation risk offers a path forward. A directed graph model linking 600+ threat actors to vulnerabilities in 7,800 customer environments reveals that 68% of organizations carry at least one CVE previously exploited by a named adversary, and 321 tracked threat groups can...
Timeline
14:21 UTC
Exploitation attempts reported by an external source
14:03 UTC
Listed in the CISA Known Exploited Vulnerabilities catalog
10:50 UTC
High-confidence, third-party report of exploitation attempts
17:51 UTC
Vulnerability disclosed publicly
18:10 UTC
Identifier reserved by the CNA
Pro API
Confidence, exploit status, sensor telemetry, PoCs, scanner integrations, mentions, and tags are available programmatically for VM, SOC, and CTI workflows.
GET /api/v2/pro/kevs/CVE-2026-21513
Sample API response{
"cve_id": "CVE-2026-21513",
"confidence": "Confirmed",
"cvss_score": 8.8,
"cvss_estimated": false,
"epss_score": 0.15852,
"exploit_status": {
"exploited_in_the_wild": true,
"active_exploitation_observed": false
},
"sensor_telemetry": { "attempts": 0, "sensors": 0 }
}