CVE-2026-124194
CVE-2026-124194 — Microsoft Outlook Spoofing Vulnerability
Product ui does not warn user of unsafe actions in Microsoft Office Outlook allows an unauthorized attacker to perform spoofing over a network.
Published Updated Sources: NVD, Microsoft (CNA), CISA, GitHub, GitHub Security Advisory, SOCRadar CTI
Triage
Is it exploited, how likely is exploitation, what does it touch, and how severe do the scoring sources call it.
Exploitation
Confirmed
CISA KEV, listed Nov 10, 2026
EPSS
0%
ahead of 0% of scored CVEs
CVSS base
6.5
medium · 2 sources
CISA SSVC assessment
Three decision points CISA publishes for the CVEs it assesses · SSVC 2.0.3. A stakeholder decision, not a severity score.
Exploitation
Active
none · proof-of-concept · active
Automatable
No
can an attacker script all four kill-chain steps
Technical impact
Partial
partial · total control of the vulnerable component
Remediation
The vendor's own words where we have them.
Upgrade Microsoft 365 Apps for Enterprise to a fixed release. Apply vendor patches per advisory and restrict external exposure of the affected component until patched.
CISA required action
Apply mitigations in accordance with vendor instructions, ensuring compliance with CISA’s BOD 26-04 Prioritizing Security Updates Based on Risk (see URL in Notes) guidance and CISA’s “Forensics Triage Requirements” (see URL in Notes). Follow applicable BOD 26-04 guidance for cloud services or discontinue use of the product if mitigations are unavailable. Stakeholders are responsible for evaluating each asset's internet exposure and ensuring adherence to BOD 26-04 patching guidelines.
Federal deadline Nov 24, 2026 — in 7 days
First 24 hours
Ordered from the record's own fields — exposure first, because you cannot patch what you have not found.
- Identify exposed assets running affected vendor/product/version combinations.
- Treat as emergency remediation because CISA KEV status is present.
- Search available logs for exploit probes, errors, authentication anomalies, or suspicious child processes matching the vulnerability class.
Affected scope
Vendor, product and version as the advisories word them.
| Vendor | Product | Versions | Status |
|---|---|---|---|
| Microsoft | Microsoft 365 Apps for Enterprise | 16.0.1 | Vulnerable |
| Microsoft | Microsoft Office LTSC 2021 | 16.0.1 to < 16.0.14334.21048 | Vulnerable |
| Microsoft | Microsoft Office LTSC 2024 | 16.0.0 to < 16.0.17932.21140 | Vulnerable |
Attack characteristics
The CVSS vector, decoded. It describes the attack, not your exposure to it.
Availability
None
Confidentiality
High
Integrity
None
Scope
Unchanged
Attack Complexity
Low
Attack Vector
Network
Privileges Req
None
User Interaction
Required
Every base score collected
Sources score independently and disagree; each row says who scored it and under which version.
| Score | Version | Severity | Expl. | Impact | Source |
|---|---|---|---|---|---|
| 6.5 | CVSS 3.1 | medium | 2.8 | 3.6 | Microsoft (CNA), GHSA |
| 6.5 | CVSS 3.1 | medium | n/a | n/a | Microsoft (CNA) |
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N
What this weakness leads to
MITRE's own consequences and mitigations for the weakness class — the authority's wording, not guidance derived from the CVSS vector.
CWE-356 · Product UI does not Warn User of Unsafe Actions
- Hide Activities::
Weakness & attack patterns
- CWE-356
CISA KEV details
CISA lists a CVE here once it has evidence of exploitation against real targets.
Listed
Nov 10, 2026
Federal deadline
Nov 24, 2026
in 7 days
Ransomware use
Unknown
CISA records ransomware use only for campaigns it has confirmed, so “Unknown” means unrecorded, not ruled out. The deadline binds US federal agencies; for everyone else it is a date to argue against.
Public exploit
Capability, not use: code existing is a different claim from anyone running it.
PoC repos
4
Detection
Read off the CVSS vector and the weakness class. Starting points, not rules we have tested.
- Prioritize edge telemetry for network-reachable Microsoft 365 Apps for Enterprise, Microsoft Office LTSC 2021, Microsoft Office LTSC 2024.
- Monitor for scanner or exploit-pattern traffic after 4 public PoC repositories were reported.
Timeline
What happened to this CVE, newest first — with the readings a source repeats on a schedule counted underneath rather than listed.
- 2026
Added to CISA KEV catalog
Nov 10, 2026 · CISA
Added · CVSS 3.1 6.5 (AV:N)
Nov 10, 2026 · NVD
Initial · CVE published
Nov 10, 2026 · NVD
Added · GHSA-69hg-ppjj-gg27 published (medium)
Nov 10, 2026 · GitHub Security Advisory
CVE published by MITRE.
Nov 10, 2026 · SOCRadar CTI
Source activity
Readings a source repeats on a schedule, counted rather than listed.
- 1×CVE modified by NIST: CISA KEV details updated.Nov 10, 2026 · SOCRadar CTI
References
5 on the record
- msrc.microsoft.com/update-guide/vulnerability/CVE-2026-124194
Vendor Advisory, Mitre, NIST
- www.cisa.gov/known-exploited-vulnerabilities-catalog?field_cve=CVE-2026-124194
US Government Resource, NIST
- nvd.nist.gov/vuln/detail/CVE-2026-124194
NVD, Vendor Advisory
- github.com/advisories/GHSA-69hg-ppjj-gg27
Exploit, Third Party Advisory
- msrc.microsoft.com/update-guide/en-US/vulnerability/CVE-2026-124194
Vendor Advisory
Coverage
3 stories from the feeds we poll
Elsewhere on this site
- Microsoftevery CVE for this vendor
- Microsoft 365 Apps for Enterpriseevery page on this product
- Microsoft Office LTSC 2021every page on this product
- Patch Tuesdayacross patch cycles
- November 2026what else CISA listed
- Unclassifiedsame class
- CWE-356other pages naming this weakness
Not in any source we poll
Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.
- No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
- No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
- No exploit packet captures, log samples, or incident case IDs supplied.
Answered from this record1
What should defenders know first?
CVE-2026-124194 is Microsoft Outlook Spoofing Vulnerability, a medium vulnerability affecting Microsoft 365 Apps for Enterprise, Microsoft Office LTSC 2021, Microsoft Office LTSC 2024 from Microsoft. The current evidence lists it in CISA KEV, and the exploit status is: Yes: CISA KEV signal present. Public exploit evidence is: 4 public PoC repositories reported; 0 marked weaponized in current dataset. The affected-version evidence is listed in the key facts and affected products tables. Defenders should first verify whether exposed or business-critical assets run those versions, then apply vendor patches or mitigations, restrict reachable attack surface, and preserve logs for detection review. CVSS 6.5 describes technical severity, while EPSS 0% helps estimate near-term exploit likelihood; neither replaces asset context. Unknown fields should remain explicit in tickets, and threat actor, IOC, victimology, or payload claims should not be added unless a cited source supports them. Monitor CISA KEV, vendor advisories, NVD changes, public PoC repositories, and internal telemetry for update triggers.