Microsoft Office Security Feature Bypass Vulnerability
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Listed in CISA KEV
- Fix
- Fixed in 16.0.5539.1001, 16.0.10417.20095
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
Microsoft Office is affected by this vulnerability, which could allow a local attacker to get around a built-in security feature. Successful exploitation would let the attacker bypass protections that Office relies on to make trust decisions, because it depends on input that cannot be trusted.
Summarized by anthropic/claude-haiku-5.5. Verify details against the original sources.
Read the original description
Reliance on untrusted inputs in a security decision in Microsoft Office allows an unauthorized attacker to bypass a security feature locally.
Timeline
- Added to CISA KEV
CISA has evidence of exploitation in the wild
- CVE published
- CISA remediation deadline
Due date for US federal agencies to patch
- Record last updated
- EPSS reached 10%
FIRST estimates at least a 10% chance of exploitation in the next 30 days
Affected versions
- Microsoft Microsoft 365 Apps for Enterprise
From 16.0.1 · fixed in https://aka.ms/OfficeSecurityReleases
- Microsoft Microsoft Office 2016
From 16.0.0 · fixed in 16.0.5539.1001
- Microsoft Microsoft Office 2019
From 19.0.0 · fixed in 16.0.10417.20095
- Microsoft Microsoft Office LTSC 2021
From 16.0.1 · fixed in https://aka.ms/OfficeSecurityReleases
- Microsoft Microsoft Office LTSC 2024
From 16.0.0 · fixed in https://aka.ms/OfficeSecurityReleases