cve.bz

CVE-2026-124228 Microsoft Office Outlook Remote Code Execution Vulnerability

8.8 highEPSS 0.8%

High (8.8) in microsoft. EPSS 0.8% estimated probability of exploitation activity in the next 30 days.

On this page
Improper limitation of a pathname to a restricted directory ('path traversal') in Microsoft Office Outlook allows an authorized attacker to execute code over a network.

Severity

CVSS 3.1

8.8 high
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
EPSS
0.8% estimated probability of exploitation activity in the next 30 days; 56th percentile. Scored 2026-11-13. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: no · Technical impact: total, assessed 2026-11-10. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-22 Improper Limitation of a Pathname to a Restricted Directory (Path traversal)
OWASP Top 10
A01:2025 Broken Access Control
Published
Modified
Assigned by
microsoft (CNA)
NVD analysis
Awaiting analysis
Record from
the NVD, synced

Ask an AI about this CVE

Show the promptExplain CVE-2026-124228 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-124228?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-124228?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-124228 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Badge for a README or a site

CVE-2026-124228

An image that stays current: it is drawn from the data each time it is fetched (a host that proxies images, as GitHub does, may show its copy for a while). Markdown:

[![CVE-2026-124228](https://cve.bz/cve/badge/CVE-2026-124228.svg)](https://cve.bz/cve/CVE-2026-124228)

HTML:

<a href="https://cve.bz/cve/CVE-2026-124228"><img src="https://cve.bz/cve/badge/CVE-2026-124228.svg" alt="CVE-2026-124228"></a>

Affected

  • microsoft:microsoft 365 apps for enterprise
  • microsoft:microsoft office ltsc 2021
  • microsoft:microsoft office ltsc 2024

Versions

From the CNA's record in the CVE List.

ProductAffected
Microsoft 365 Apps for Enterprisefrom 16.0.1 before https://aka.ms/OfficeSecurityReleases
Microsoft Office LTSC 2021from 16.0.1 before 16.0.14334.21048
Microsoft Office LTSC 2024from 16.0.0 before 16.0.17932.21140

Attack patterns (CAPEC)

  • CAPEC-64 Using Slashes and URL Encoding Combined to Bypass Validation Logic Likelihood: High · Severity: High
  • CAPEC-76 Manipulating Web Input to File System Calls Likelihood: High · Severity: Very High
  • CAPEC-78 Using Escaped Slashes in Alternate Encoding Likelihood: High · Severity: High
  • CAPEC-79 Using Slashes in Alternate Encoding Likelihood: High · Severity: High
  • CAPEC-126 Path Traversal Likelihood: High · Severity: Very High

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

References

Check your stackJSON