Skip to content
Server Security Center
KEVcritical9.8

CVE-2014-1776: Microsoft Internet Explorer Memory Corruption

Microsoft Internet Explorer · listed in the CISA catalog of actively exploited vulnerabilities since 2022-01-28.

CVSS v3.1 (CISA ADP)
9.8
critical
EPSS (exploit probability, 30 days)
83%
higher than 99.6% of all CVEs
Added to CISA KEV
2022-01-28
US federal due date 2022-07-28
Automatable (CISA SSVC)
yes
technical impact: total

CVE-2014-1776 explained

CVE-2014-1776 is a use-after-free vulnerability in Microsoft Internet Explorer 6 through 11 that lets remote attackers execute arbitrary code or cause memory corruption. It was exploited in the wild in April 2014, and CISA lists it as a known exploited vulnerability, which makes patching affected systems a priority.

Impact

A remote attacker can run arbitrary code on the affected system or crash the browser through memory corruption. The CVSS assessment shows a network attack with low complexity that needs no privileges or user interaction. CISA rates it automatable with total technical impact, meaning attackers can exploit it at scale and gain full control of the affected component. CISA's known-exploited catalog confirms real-world use. Ransomware use is unknown.

Who is affected

The description names Microsoft Internet Explorer versions 6 through 11 as affected. The CVE record itself lists no affected versions in structured form. It also names no fixed version. Use the Microsoft vendor advisory to identify the update that addresses this issue for each Internet Explorer version and Windows platform you run.

Written with AI from the data on this page and checked against it automatically.

Official description

Use-after-free vulnerability in Microsoft Internet Explorer 6 through 11 allows remote attackers to execute arbitrary code or cause a denial of service (memory corruption) via vectors related to the CMarkup::IsConnectedToPrimaryMarkup function, as exploited in the wild in April 2014.

NOTE: this issue originally emphasized VGX.DLL, but Microsoft clarified that "VGX.DLL does not contain the vulnerable code leveraged in this exploit. Disabling VGX.DLL is an exploit-specific workaround that provides an immediate, effective workaround to help block known attacks."

CISA required action: Apply updates per vendor instructions.

CISA notes

How to fix it

  • The CVE record names no fixed version – check the vendor advisory and CISA's required action for updates and mitigations.
  • Vendor advisory: docs.microsoft.com/en-us/security-updates/securitybulleti…
  • CISA's deadline for US federal agencies: 2022-07-28 (passed) – a useful benchmark for everyone else, too.

What to do

  1. Apply the Microsoft security update for Internet Explorer as described in the vendor advisory.
  2. Follow CISA's required action: apply updates per vendor instructions.
  3. Until patched, consider disabling VGX.DLL, which Microsoft describes as an exploit-specific workaround that helps block known attacks.
  4. Inventory systems still running Internet Explorer and limit its use for browsing untrusted sites.
  5. Check exposed systems for signs of compromise, since the flaw was exploited in the wild.

The CVE record names no fixed version. Follow the Microsoft vendor advisory to find and apply the relevant update, as CISA's required action directs. Until the update is applied, Microsoft's workaround of disabling VGX.DLL helps block known attacks, though VGX.DLL does not contain the vulnerable code itself. Restrict Internet Explorer use on affected systems in the meantime.

Written with AI from the data on this page and checked against it automatically.

CISA's assessment (SSVC)

Exploitation
Exploited in the wild
Automatable
Yes – attackers can automate it at scale
Technical impact
Total – full control of the component or total information disclosure

Weakness: CWE-416 Use After Free

Questions about CVE-2014-1776

Is CVE-2014-1776 being exploited?
Yes. The description states it was exploited in the wild in April 2014, and CISA added it to its Known Exploited Vulnerabilities catalog on 2022-01-28.
Does disabling VGX.DLL fix the vulnerability?
No. Microsoft clarified that VGX.DLL does not contain the vulnerable code. Disabling it is an exploit-specific workaround that helps block known attacks. Apply the vendor update for a proper fix.
What deadline did CISA set for US federal agencies?
CISA set a due date of 2022-07-28, with the required action to apply updates per vendor instructions.

Written with AI from the data on this page and checked against it automatically.

References

Data: CISA Known Exploited Vulnerabilities (public domain) · CVE Program records incl. CISA ADP enrichment · OSV.dev (CC BY 4.0) incl. Ubuntu and Debian security data · FIRST EPSS · endoflife.date. Updated automatically – facts last changed 2026-11-22. Always confirm with the vendor's or distribution's advisory before patching.