LiveActive security incident?Get immediate response
CVE Record

CVE-2016-7200: The Chakra JavaScript scripting engine in Microsoft Edge allows remote attackers to execute arbitrary code...

The Chakra JavaScript scripting engine in Microsoft Edge allows remote attackers to execute arbitrary code or cause a denial of service (memory corruption) via a crafted web site, aka "Scripting Engine Memory Corruption Vulnerability," a different vulnerability than CVE-2016-7201, CVE-2016-7202, CVE-2016-7203, CVE-2016-7208, CVE-2016-7240, CVE-2016-7242, and CVE-2016-7243.

HighCVSS 8.8Known exploitedUpdated
Glexia's TakeAutomated analysiscritical

Security readout for executives and security teams

Plain-English summary

CVE-2016-7200 is a Microsoft Edge Chakra scripting engine memory corruption flaw. A malicious website could let an attacker run code or crash the browser after user interaction. CISA KEV marks it as known exploited, so any remaining vulnerable Edge/Chakra exposure should be treated as urgent legacy risk.

Executive priority

Prioritize remediation for any remaining vulnerable legacy systems. The business risk is code execution through web browsing, backed by KEV known-exploitation status, but exposure may be limited if legacy Edge has been retired.

Technical view

The issue is a Chakra JavaScript engine memory corruption vulnerability in Microsoft Edge, categorized as CWE-787. The CVSS 3.1 vector is 8.8: network attack, low complexity, no privileges, user interaction required, with high confidentiality, integrity, and availability impact.

Likely exposure

Exposure is most likely on legacy Microsoft Edge installations using the vulnerable Chakra engine and missing the MS16-129-era security update. The source bundle does not provide exact affected versions or CPEs.

Exploitation context

CISA KEV support indicates known exploitation. Public exploit references are listed, but the bundle does not provide campaign details, targets, exploitation volume, or current weaponization context.

Researcher notes

The bundle names Microsoft Edge Chakra and CWE-787, with CVSS 8.8 and KEV status. It does not include precise affected versions, patch supersedence, exploit telemetry, or safe detection artifacts, so validation should rely on vendor update state and asset inventory.

Mitigation direction

  • Apply Microsoft MS16-129 guidance where applicable.
  • Inventory legacy Microsoft Edge and Chakra-based systems.
  • Remove or upgrade unsupported vulnerable browser environments.
  • Limit vulnerable browsers from accessing untrusted websites until remediated.
  • Check Microsoft guidance for exact platform-specific update requirements.

Validation and detection

  • Confirm whether Microsoft Edge with Chakra exists in the environment.
  • Verify MS16-129 or superseding Microsoft updates are installed.
  • Review browser fleet, VDI, kiosk, and legacy endpoint inventories.
  • Check vulnerability scanner findings for CVE-2016-7200.
  • Prioritize systems still used for web browsing.
Prepared
Confidence
medium
Sources
6

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · low confidence lookup

CWE-787: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
description · low confidence lookup

Execution behavior lookup

The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2016-7200 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
High
CVSS
8.8 (3.1)
Known Exploited
Yes
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
0Timeline events
0ADP providers
6Source links

CISA KEV status

Status
Known exploited
Source
CISA / ADP
Date added
Not provided

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
8.8CVSS 3.1HighCVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H2.85.9Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

8.8High
CVSS 3.1 vector shape for CVE-2016-7200Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
n/an/an/aListed
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-787 · source CWE mapping

Out-of-bounds Write

Out-of-bounds Write represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.