Skip to content
Blog

Microsoft · Microsoft Outlook · Microsoft Office

Microsoft, November 2026: Exploited Outlook Spoofing (CVE-2026-124194), SharePoint at 9.9 and VS Code at 9.6

Outlook CVE-2026-124194 is exploited and in KEV, two SharePoint privilege escalations (9.9 and 9.0) and a VS Code code injection at 9.6. What to do first.

On November 10, 2026, Microsoft shipped a new batch of fixes, and CISA added one of them to its Known Exploited Vulnerabilities catalog the same day: CVE-2026-124194, a spoofing flaw in Outlook. Its score is modest (6.5), but confirmed exploitation outweighs a number.

The same release brought three CVEs that Microsoft rates critical: two privilege escalations in SharePoint and a code injection in Visual Studio Code.

CVEProductWeaknessCVSS 3.1 (Microsoft)NVD statusKEV
CVE-2026-124194Outlook (Office)UI fails to warn about an unsafe action (CWE-356)6.5 MEDIUMAnalyzedYes, 2026-11-10
CVE-2026-120002SharePointIncorrect authorization (CWE-863)9.9 CRITICALAwaiting AnalysisNo
CVE-2026-80095SharePointCross-site scripting (CWE-79)9.0 CRITICALAwaiting AnalysisNo
CVE-2026-120779Visual Studio CodeCode injection (CWE-94)9.6 CRITICALAwaiting AnalysisNo

All scores are Microsoft's. NVD has not published its own score for any of the four.


Outlook: CVE-2026-124194, exploited

The NVD description is short: Outlook's UI does not warn the user about unsafe actions, which lets an unauthorized attacker perform spoofing over a network.

Microsoft's vector (AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N) fills in the rest: no privileges needed, user interaction required, and high confidentiality impact with no integrity or availability impact. In other words, the documented consequence is information disclosure. Microsoft has not released technical details; the obvious scenario, a crafted message that gets the user to act without the expected warning, remains an assumption.

CISA set the federal remediation deadline to November 24, 2026. Ransomware use is listed as "Unknown".

Products in NVD's CPE configuration:

  • Microsoft 365 Apps for Enterprise (x86 and x64);
  • Office LTSC 2021 (x86 and x64);
  • Office LTSC 2024 (x86 and x64).

NVD does not give a fixed build number; it is in Microsoft's MSRC entry for the CVE.


SharePoint: two critical privilege escalations

  • CVE-2026-120002 (9.9): incorrect authorization lets an already authenticated attacker elevate privileges over the network. The vector (PR:L/UI:N/S:C) means a plain user account is enough, no victim interaction is needed, and the impact reaches beyond the vulnerable component.
  • CVE-2026-80095 (9.0): a cross-site scripting flaw also leads to privilege escalation. This one needs a victim to interact (UI:R), typically by opening a page where the attacker has planted script. That is a reading of the vector, not something Microsoft states.

Both require an account. On a SharePoint open to partners or guests, that bar is low. NVD has no CPE configuration yet, so the affected SharePoint Server versions and their fixes are in the MSRC advisories.

SharePoint has had several KEV listings this year, including CVE-2026-65660 in late September. These two are not known to be exploited yet, but the target is well established.


Visual Studio Code: CVE-2026-120779 (9.6)

A code injection flaw in VS Code lets an unauthorized attacker execute code over a network. The vector (PR:N/UI:R/S:C) indicates a developer has to do something, such as opening a file or repository supplied by the attacker; Microsoft does not describe the trigger.

A developer workstation holds secrets (Git tokens, cloud keys, pipeline access), so code execution there quickly becomes access to the software supply chain. NVD gives no CPE configuration and no fixed version. VS Code auto-updates by default, but not everywhere: portable installs, offline machines and pinned dev images often lag behind.


Detection

  • Outlook / Office: inventory Microsoft 365 Apps channels and Office LTSC build numbers (Intune, Configuration Manager, Microsoft 365 admin center) and compare them with the builds in the MSRC advisory.
  • SharePoint Server: check the installed update level on every farm; flag farms reachable from outside or open to guest accounts.
  • VS Code: code --version on endpoints, and look for unmanaged installs (portable builds, dev containers).

Mitigation

  1. Outlook first: it is being exploited. Roll out the November Office update on every channel before November 24.
  2. SharePoint: apply the November fixes; meanwhile, review guest accounts and limit external exposure.
  3. VS Code: force the update and remind teams to open unfamiliar repositories in Workspace Trust's Restricted Mode.
  4. Do not triage on CVSS alone: the lowest-scored of the four is the only one under active exploitation.

Why continuous monitoring of your Microsoft estate matters

Every Microsoft release mixes critical flaws nobody is exploiting yet with moderate ones attackers already use. Cross-referencing score, KEV status and the versions actually installed is how you decide what to deploy first.

With cveo.tech, add Office, SharePoint and your developer tools to your inventory and get an alert as soon as a critical CVE or KEV listing affects them.

Know which CVEs hit the versions you run.

Add the product and its version: cveo.tech lists the CVEs that affect it right away, then alerts you by email when a new one affects it — including before NVD has finished its analysis. Free, an account is all it takes.

Every Monday

The week's critical CVEs, in your inbox

One email a week: the CVSS ≥ 9 vulnerabilities published in the last seven days, plus our latest analyses. Nothing else.

Double opt-in by email. Unsubscribe in one click, any time.