⚠ Known Exploited Vulnerability (KEV) Tracker

Description

Microsoft Exchange Server Spoofing Vulnerability

Lifecycle Timeline

• 2024-11-12
  CVE published

  Entered the public CVE record.

  CVE.org →
• 2024-11-12
  Vendor fix published

  Microsoft shipped a fix for Microsoft Exchange Server.

  MSRC →
• 2024-11-13
  First national advisory 1 day later

  CERT-EU — 2024-116: Microsoft November 2024 Patch Tuesday

  CyberzSOC advisory index →
• 2025-08-02
  EPSS flags exploitation risk 9 months later

  Probability rose past 10%, from 8.1% to 10.1%. Dated to the sampled week.

  FIRST EPSS →
• not recorded
  Public exploit code

  No dated exploit found in Metasploit, Exploit-DB or public GitHub repositories.
• not recorded
  Added to CISA KEV

  Not in the CISA KEV catalog.
• not recorded
  Federal remediation due

  No remediation deadline set.

Each milestone comes from a different source, so gaps between them are gaps in what those sources publish, not evidence that nothing happened. EPSS history for this CVE holds 109 points from 2024-11-16, tracked daily from 2026-09-09; earlier points are weekly, which dates a spike to within a week. Peak probability 15.6% on 2025-12-13.

Published Applicability

Check whether a specific version is affected →

What each source publishes about which product versions carry this vulnerability, kept as written rather than merged. Absence here means no source has published applicability data, not that nothing is affected.

Research & News Coverage

No mentions found in monitored research blogs or news feeds.

Detection & Exploitation

Blind spot. No public detection — verify by version/patch. Nothing in the monitored scanner, IDS, SIEM or offensive-tool collections references this CVE, so exposure has to be established from asset inventory and patch level rather than from a signature.

Coverage across public collections only: Nuclei and OpenVAS NVT (scan); Snort and Suricata ET Open (network); Sigma and YARA (host/SIEM); Metasploit, Exploit-DB and public GitHub repositories (exploit). Absence here means nothing public was found, not that detection is impossible.
GitHub PoC repositories are collected automatically by PoC-in-GitHub (CC0) and are not vetted: some are fakes and some are malware. Treat them as evidence that code was published, not as code to run.
OpenVAS coverage derives from the Greenbone Community Feed, made available under the Open Database License (ODbL) v1.0; its individual Vulnerability Tests are licensed GNU GPL v2.

Microsoft Exchange Server Spoofing Vulnerability

The vendor's own judgement about their own code, shown alongside CISA's rather than merged into it. The exploitability index is a forward-looking prediction, distinct from a CVSS severity or CISA's SSVC decision, and vendors often report observed exploitation before a CVE reaches the KEV catalog. Vendor advisory →

CISA Assessment (Vulnrichment / SSVC)

Listed By

Referenced in Advisories

Weaponization Timeline — Offensive & Testing Tools

No exploit-tool sightings recorded for this CVE.

Evidence tiers are explained on the About page — a merged Metasploit module is far stronger evidence than a distro package mention.

External References

CVE.org record → NVD entry → Microsoft MSRC advisory → FortiGuard Labs → Rapid7 AttackerKB →