Skip to content
Fencer Vulns
high 8.8

CVE-2023-35311 kev in the critical feed json

Microsoft Outlook Security Feature Bypass Vulnerability

published 2023-07-11 3 y ago modified 2026-10-08 32 d ago also EUVD-2023-39314

cvss
8.8
version 3.1, CNA
cisa kev
Exploited
added 2023-07-11
epss
15.5%
EPSS 15.5% chance of exploitation in 30 days, percentile 96%
public exploits
0
none known

Summary

Microsoft Outlook Security Feature Bypass Vulnerability

Patch / fix

cisa required action Apply updates per vendor instructions or discontinue use of the product if updates are unavailable.

  • Microsoft Microsoft Outlook 2016 16.0.5404.1000
  • Microsoft Microsoft Outlook 2013 15.0.5571.1000
  • Microsoft Microsoft Outlook 2013 Service Pack 1 15.0.5571.1000

Timeline

  1. Added to CISA KEV
  2. Published
  3. CISA patch deadline
  4. CISA SSVC: exploitation active

Known exploited

Added
3 y ago
Patch by
2023-08-01 (3 y ago)
Ransomware
Not known
Required action
Apply updates per vendor instructions or discontinue use of the product if updates are unavailable.
Vendor, product
Microsoft, Outlook
CISA name
Microsoft Outlook Security Feature Bypass Vulnerability

CISA SSVC

Exploitation
Active, exploited in the wild
Automatable
no
Technical impact
total
Assessed
21 mo ago

Exploit prediction

15.52% chance of exploitation in the next 30 days, higher than 96% of all scored CVEs (FIRST EPSS, 2026-11-08).

CVSS scores

assigned by version score vector
CNA 3.1 8.8 CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H/E:F/RL:O/RC:C
NVD 3.1 8.8 CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
CNA 3.1 7.5 CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:H

Affected products

  • Microsoft Microsoft 365 Apps for Enterprise
  • Microsoft Microsoft Office LTSC 2021
  • Microsoft Microsoft Office 2019
  • Microsoft Microsoft Outlook 2016
  • Microsoft Microsoft Outlook 2013
  • Microsoft Microsoft Outlook 2013 Service Pack 1

Classification

Weakness
  • CWE-367 Time-of-check Time-of-use (TOCTOU) Race Condition

References

Sources

Fencer Vulns 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.