Exploited CVEs / Microsoft / CVE-2016-7200
CVE-2016-7200
Microsoft Edge Memory Corruption Vulnerability. Exploitation in the wild is confirmed by CISA, not predicted. Federal agencies were required to remediate by 2022-04-18 (that deadline has passed); treat that date as the outer bound for your own environment. The fix is in the vendor advisory: Microsoft Security Update Guide (MSRC), linked below.
Risk summary
Actively exploited Microsoft Edge vulnerability. Added to the CISA KEV catalog 2022-03-28.
Senserva AI Opinion for CVE-2016-7200
A companion to the other Chakra engine flaw of the same era, this Microsoft Edge memory corruption also delivers remote code execution from a crafted page and is confirmed exploited per CISA KEV. Attackers reach it simply by luring a user to a hostile site. Only pre-Chromium Edge carries the vulnerable engine.
Do this: Remove or update any remaining legacy Edge installs; the Chakra engine has no place on a managed endpoint.
AI-generated from public data, 2026-07-07. Verify against the vendor advisory before acting.
Senserva AI Opinion and rich prompt for CVE-2016-7200
Copy this prompt into Claude, ChatGPT, or Copilot. The facts are included, sourced from this page.
Updated August 14, 2026. Data refreshed on every build from MSRC, CISA KEV, and FIRST EPSS.
Full tracking and change history for CVE-2016-7200
- Published
- 2022-03-28
- Last revised
- 2022-03-28
- Changes tracked
- 1
Published and last-revised dates are authoritative, from Microsoft MSRC (or the CISA KEV date-added). Senserva additionally records day-to-day changes from 2026-07-07, refreshed several times a day; the change count reflects that forward-only tracking.
CISA required action
Federal (BOD 22-01) remediation due date: 2022-04-18 (past due).
Official fix for CVE-2016-7200
The authoritative fix and affected-version list are published by the vendor. Find the Edge advisory on Microsoft Security Update Guide (MSRC).
Common questions about CVE-2016-7200
Is CVE-2016-7200 actively exploited?
Yes. CVE-2016-7200 was added to the CISA Known Exploited Vulnerabilities (KEV) catalog on 2022-03-28, which means exploitation in the wild has been confirmed, not predicted.
What is the CISA deadline and required action for CVE-2016-7200?
CISA set the federal (BOD 22-01) remediation due date at 2022-04-18, which has passed; treat any unremediated system as overdue.
What fixes CVE-2016-7200?
The authoritative fix is in the vendor advisory: see Microsoft Security Update Guide (MSRC) for the patched Edge versions and any workarounds. KEV listing makes this a fix-first item: patch it ahead of higher-CVSS issues nobody is exploiting.
Can I ask my own AI about CVE-2016-7200?
Yes. This page includes a free, ready-to-paste AI prompt containing CVE-2016-7200's key facts: severity, CVSS, EPSS, the KEV date, the CISA due date, and the required action. Copy it into Claude, ChatGPT, or Copilot; the data is refreshed twice a day (5 AM and 3 PM US Central).
Scope and sources
- More exploited Microsoft CVEs
- CVE-2008-4250CVE-2009-1537CVE-2010-0249CVE-2010-0806CVE-2026-41091CVE-2026-45498CVE-2026-33825CVE-2009-0238
All Microsoft exploited CVEs on one page: Microsoft vulnerabilities actively exploited.
- Authoritative references
Every actively exploited CVE, searchable with due dates and CSV export: the exploited-CVE tracker. The newest additions: exploited this week.