cve.bz

CVE-2026-124194 Microsoft Outlook Spoofing Vulnerability

6.5 mediumKEVEPSS 1.6%

Medium (6.5) in Microsoft Office. In CISA KEV since 2026-11-10. EPSS 1.6% estimated probability of exploitation activity in the next 30 days.

On this page
Product ui does not warn user of unsafe actions in Microsoft Office Outlook allows an unauthorized attacker to perform spoofing over a network.

Severity

CVSS 3.1

6.5 medium
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N
EPSS
1.6% estimated probability of exploitation activity in the next 30 days; 76th percentile. Scored 2026-11-13. A forecast for this CVE across the internet, not for your own systems.
CISA KEV
listed 2026-11-10, due 2026-11-24
CISA's assessment (SSVC)
Exploitation: active · Automatable: no · Technical impact: partial, assessed 2026-11-09. 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-356 Missing User Interaction for Potentially Unsafe Action
Published
Modified
Assigned by
microsoft (CNA)
NVD analysis
Analyzed
Record from
the NVD, synced

Ask an AI about this CVE

Show the promptExplain CVE-2026-124194 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-124194?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-124194?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-124194 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-124194

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-124194](https://cve.bz/cve/badge/CVE-2026-124194.svg)](https://cve.bz/cve/CVE-2026-124194)

HTML:

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

Affected

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

Fix and patched versions

GitHub PoC (unverified)

Repositories on GitHub named after this CVE. Nobody has checked them and they are not scanned: some hold a working proof of concept, some nothing useful, and some malware made to look like one. Read the code before you run any of it.

History

  1. Listed in CISA KEV
  2. Analyzed by the NVD

Changes since this site first stored the record. The same for every record: /api/public/changes.

References

Check your stackJSON