CVE-2026-124194: Microsoft Office flaw exploited in the wild, what we know

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

• Severity: MEDIUM (CVSS 3.1 6.5, vector CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N).
• Weakness: CWE-356.
• NVD published 2026-11-10, status Analyzed.

Anyone running Microsoft Office. Internet-facing instances are the priority.

NVD has not published affected version ranges for this CVE yet. Use the vendor advisory in the sources below to confirm which builds are affected.

• Exploited in the wild: added to the CISA Known Exploited Vulnerabilities catalog on 2026-11-10; federal remediation due date 2026-11-24.

CISA added CVE-2026-124194 to its Known Exploited Vulnerabilities catalog on 2026-11-10. A KEV listing means CISA has evidence that attackers are using the flaw against real systems, not just that it could be used.

If your business runs Microsoft Office, put this at the top of the patch list. CISA gave US federal agencies until 2026-11-24 to deal with it, and that is a sensible deadline for a small business too.

• Patch. Install the latest update from Microsoft. NVD does not list a fixed version, so the vendor advisory linked on this page is the reference for which release closes it.
• If you cannot patch yet. Follow CISA's 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.
• Check your exposure. Find out whether Microsoft Office can be reached from the internet, for example a VPN portal, an admin login page or a file-transfer site. Your firewall's port-forwarding rules and your IT provider's list of public-facing systems are the quickest places to look. Exposed copies come first.
• When to call IT support. Call your IT support provider now if you run Microsoft Office and cannot confirm it is updated, if it was reachable from the internet before you patched it, or if you notice accounts, sign-ins or files you do not recognise. The last two can mean the system was already hit, and checking that properly takes someone who can read the logs.

• EPSS (probability of exploitation activity in the next 30 days): n/a.
• CVERadar threat level: 48/100 (see methodology).

1. Find every instance. List where Microsoft Office runs, including test, DR and forgotten internet-facing systems, and record the installed version.

   # Windows edition and build
   Get-ComputerInfo -Property WindowsProductName, WindowsVersion, OsBuildNumber
   
   # Most recently installed updates
   Get-HotFix | Sort-Object InstalledOn -Descending | Select-Object -First 10 HotFixID, InstalledOn

2. Apply the latest vendor update. NVD does not list a fixed version, so follow the vendor advisory for the patched release.

   # After deploying the update through Windows Update, WSUS or Intune,
   # confirm the KB from the Microsoft advisory is installed:
   Get-HotFix -Id <KB-number-from-the-advisory>

3. If you can't patch today, follow CISA's 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.
4. Verify the fix. Re-run the version check above on every instance and confirm it reports the fixed build. Re-scan from outside if the service is exposed.
5. Hunt for signs of earlier compromise. If the system was exposed before you patched, assume it may have been hit and check the items below.
6. Rotate credentials stored on or used by the affected system if you cannot rule out compromise, and keep the logs you reviewed.

Detection hints

• Check the vendor advisory for indicators of compromise and review the affected system's logs back to the disclosure date.

Detection commands are generic starting points, not CVE-specific signatures. Use the indicators from the vendor advisory when it publishes them.

• NVD: CVE-2026-124194 nvd.nist.gov/vuln/detail/CVE-2026-124194
• CVE.org record www.cve.org/CVERecord?id=CVE-2026-124194
• Microsoft Security Update Guide msrc.microsoft.com/update-guide/vulnerability/CVE-2026-124194
• Vendor link from CISA KEV msrc.microsoft.com/update-guide/en-US/vulnerability/CVE-2026-124194
• CISA KEV catalog www.cisa.gov/known-exploited-vulnerabilities-catalog
• FIRST EPSS (n/a) api.first.org/data/v1/epss?cve=CVE-2026-124194