CVE-2022-33632

Microsoft Office Security Feature Bypass Vulnerability

MEDIUM
4.7
CVSS Score
Published: July 12, 2022 at 10:37 PM UTC
Updated: June 17, 2026 at 04:49 AM UTC
7 products affected across 1 vendorOffice365 AppsOffice Long Term Servicing Channel

Using Microsoft Office LTSC 2021 by Microsoft?

Get instant alerts when new vulnerabilities affect Microsoft Office LTSC 2021 - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
MEDIUM4.7
Exploit prediction
EPSS 1%
SSVC
No known exploit

Description

Microsoft Office Security Feature Bypass Vulnerability

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

16.0.1 ≤ v < https://aka.ms/OfficeSecurityReleases16.0.1
Affected range stops below https://aka.ms/OfficeSecurityReleases, so it looks safe — our inference, not a vendor statement
15.0.0 ≤ v < 15.0.5467.100016.0.0 ≤ v < 16.0.5344.100019.0.0 ≤ v < https://aka.ms/OfficeSecurityReleases2013 sp120162019
Affected range stops below 15.0.5467.1000, so it looks safe — our inference, not a vendor statement
Affected range stops below 16.0.5344.1000, so it looks safe — our inference, not a vendor statement
Affected range stops below https://aka.ms/OfficeSecurityReleases, so it looks safe — our inference, not a vendor statement
16.0.1 ≤ v < https://aka.ms/OfficeSecurityReleases2021
Affected range stops below https://aka.ms/OfficeSecurityReleases, so it looks safe — our inference, not a vendor statement
15.0.0 ≤ v < 15.0.5467.100015.0.0
Affected range stops below 15.0.5467.1000, so it looks safe — our inference, not a vendor statement
16.0.0 ≤ v < 16.0.5344.100016.0.0
Affected range stops below 16.0.5344.1000, so it looks safe — our inference, not a vendor statement
19.0.0 ≤ v < https://aka.ms/OfficeSecurityReleases19.0.0
Affected range stops below https://aka.ms/OfficeSecurityReleases, so it looks safe — our inference, not a vendor statement
16.0.1 ≤ v < https://aka.ms/OfficeSecurityReleases16.0.1
Affected range stops below https://aka.ms/OfficeSecurityReleases, so it looks safe — our inference, not a vendor statement

Remediation

No guide yet

No remediation guidance has been written for this CVE yet. What the record does show:

SSVC — Action Prioritization

SSVCNo known exploitNot automatablePartial impact

SSVC signals action urgency (what to patch first), separate from CVSS which measures severity.

CVSS

4.7MEDIUMmicrosoft
Vector?

Quick Info

StatusMODIFIED
CWE
NVD-CWE-noinfo

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card