CVE-2023-35311

Microsoft Outlook Security Feature Bypass Vulnerability

HIGH
8.8
CVSS Score
Published: July 11, 2023 at 05:03 PM UTC
Updated: October 8, 2026 at 10:35 AM UTC
6 products affected across 1 vendorOffice365 AppsOffice 2021

Using Microsoft 365 Apps for Enterprise by Microsoft?

Get instant alerts when new vulnerabilities affect Microsoft 365 Apps for Enterprise - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
HIGH8.8
Exploitation
CISA KEV
Exploit prediction
EPSS 16%
SSVC
Active

Actively Exploited

CISA Known Exploited Vulnerabilities (KEV) Catalog

EPSS Score15.5%

EPSS (Exploit Prediction Scoring System) estimates a 15.5% chance this CVE is exploited in the wild within the next 30 days — higher than 97% of all CVEs. It complements CVSS: a high EPSS on a mid-severity CVE can still be urgent.

Microsoft Outlook contains a security feature bypass vulnerability that allows an attacker to bypass the Microsoft Outlook Security Notice prompt.

Required Action
Apply updates per vendor instructions or discontinue use of the product if updates are unavailable.
Ransomware Use
Unknown
Added to KEV
Jul 11, 2023
Remediation Due
Aug 1, 2023
1186 days overdue

Description

Microsoft Outlook 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/OfficeSecurityReleases-16.0.1
Affected range stops below https://aka.ms/OfficeSecurityReleases, so it looks safe — our inference, not a vendor statement
19.0.0 ≤ v < https://aka.ms/OfficeSecurityReleases
Affected range stops below https://aka.ms/OfficeSecurityReleases, so it looks safe — our inference, not a vendor statement
19.0.0 ≤ v < https://aka.ms/OfficeSecurityReleases-19.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/OfficeSecurityReleases-16.0.1
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/OfficeSecurityReleases
Affected range stops below https://aka.ms/OfficeSecurityReleases, so it looks safe — our inference, not a vendor statement
14.0.0 ≤ v < 15.0.5571.100015.0.0.0 ≤ v < 15.0.5571.100016.0.0.0 ≤ v < 16.0.5404.100014.0.015.0.0.016.0.0.020132013 sp12016
Affected range stops below 15.0.5571.1000, so it looks safe — our inference, not a vendor statement
Affected range stops below 16.0.5404.1000, 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

SSVCActiveNot automatableTotal impact

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

CVSS

8.8HIGHmicrosoft
Vector?

Quick Info

StatusANALYZED
CWE
CWE-367

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