basicsecurity.net
Proof, not just disclosure.
Threats / Microsoft / CVE-2016-7201
CVE-2016-7201 · EUVD no mirror located · GCVE no mirror located Verified 2026-06-22

Microsoft Edge vulnerability

Memory corruption vulnerability in Microsoft Edge's Chakra JavaScript engine allows remote code execution or denial of service through malicious web content.

Verdict

Today item — known-exploited.

Remote attackers can exploit memory corruption in Edge's JavaScript engine via crafted websites to achieve code execution or crash the browser. The high EPSS score and active exploitation in the wild indicate immediate risk to users visiting untrusted sites.

CISA KEV Yes · 2022-03-283EPSS 0.79687 (verify live)4Exploit Public PoC5
01

Is it exploitable?

— the evidence, ranked above the score
Exploit available
Public proof-of-concept exploit code is cataloged for this vulnerability.We link the existence of the exploit; we do not host or redistribute payloads.
Reported exploitation
4 independent public reports of in-the-wild exploitation are cataloged.Distinct reporting sources (vendor, incident response, government); open them for the underlying claims.
Exploited in the wild
Listed in the CISA Known Exploited Vulnerabilities catalog (added 2022-03-28).
CISA KEV ↗Confirmed
Probability (EPSS)
EPSS 0.79687 — modeled likelihood of exploitation activity.EPSS is a daily-changing model output — open the source for today's value.
Severity / affected
Affected: Microsoft, Edge. Confirm exact fixed builds in the vendor advisory.
NVD ↗Reported
Weakness (CWE)
Mapped to CWE-119 Memory Buffer Bounds Error — weakness family: Memory safety.CWE assignment from the public NVD record; the weakness class drives how the flaw is exploited.
NVD ↗Reported
02

Who’s exploiting it?

— attribution turns risk into urgency
Attribution not established

No confirmed (advisory-backed) threat-actor attribution is established for this record. Absence of a named actor is not absence of compromise — see Coverage & confidence.

03

Why it matters

— the attack path, told twice: adversary, then board
1

Front door — unauthenticated access narrative 1

Attacker
I craft a malicious webpage containing JavaScript that triggers memory corruption in the Chakra engine.
Business
Users visiting the attacker's site or redirected content face immediate compromise of their browser process and potential system access.
2

Keys to the kingdom — privilege/identity takeover narrative 2

Attacker
I host the exploit on a compromised or attacker-controlled domain and distribute the link through phishing or watering hole attacks.
Business
Enterprise endpoints running Edge become vectors for lateral movement and data exfiltration without user awareness of the technical exploit.
3

Lateral reach — past segmentation narrative 3

Attacker
I trigger a denial of service by causing repeated memory corruption, crashing the browser or degrading system stability.
Business
User productivity is disrupted and support costs increase as affected systems become unreliable or unresponsive.
04

What to do

— defensible action
  • Remediate per the vendor advisory — confirm the fixed build for your version and verify exposure.1
Say it to the boardA vulnerability with this evidence profile is a defensible budget line, not a backlog ticket — fund the change against the proof above.
05

Coverage & confidence

— what we know, and what we don’t

Established (cited)

  • KEV listing (CISA)
  • EPSS probability (FIRST)
  • Public PoC available (VulnCheck)
  • 4 reported-exploitation source(s)
  • CWE weakness mapping (NVD)
  • Public exploit availability
  • Catalogued by microsoft (CNA)
  • Coverage gaps — stated, not hidden

  • No EUVD / GCVE mirror in feed — single-authority dependency for the identifier.
  • EPSS & exposure are time-varying; verify live at the source.
  • Threat-actor attribution not established from feed data — absence of a name is not absence of compromise.
  • No finder/reporter credit recorded in the public CVE entry — the work behind this find is unattributed.
  • Disclosure & credit2
    Catalogued by microsoftCNA
    Credited with finding itNo finder named in the public CVE record — the work behind this find is unattributed.