A security feature bypass vulnerability exists in the way that Office Click-to-Run (C2R) components handle a specially crafted file, which…

published 2019-11-12 6y ago modified 2026-06-17 4mo ago also EUVD-2019-10006

cvss: 9.8; version 3.1, NVD
cisa kev: Not listed; not in CISA's catalog
epss: 6.8%; EPSS 6.8% chance of exploitation in 30 days, percentile 94%
public exploits: 0; none known

A security feature bypass vulnerability exists in the way that Office Click-to-Run (C2R) components handle a specially crafted file, which could lead to a standard user, any AppContainer sandbox, and Office LPAC Protected View to escalate privileges to SYSTEM.To exploit this bug, an attacker would have to run a specially crafted file, aka 'Microsoft Office ClickToRun Security Feature Bypass Vulnerability'.

Patch / fix

links 1

portal.msrc.microsoft.com/en-US/security-guidance/advisory/CVE-2019-1449 advisory

Is CVE-2019-1449 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Exploit prediction

6.81% chance of exploitation in the next 30 days, higher than 94% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by	version	score	vector
NVD	3.1	9.8	CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
NVD	2.0	10.0	AV:N/AC:L/Au:N/C:C/I:C/A:C

Affected products

Microsoft Microsoft Office
Microsoft Office 365 ProPlus

References

portal.msrc.microsoft.com /en-US/security-guidance/advisory/CVE-2019-1449
patch, vendor-advisory

Sources

CVE List CVE-2019-1449
NVD CVE-2019-1449

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.