CVE Intelligence
High Input validation

CVE-2025-59248 — Microsoft Exchange Server Spoofing Vulnerability

Improper input validation in Microsoft Exchange Server allows an unauthorized attacker to perform spoofing over a network.

Published Oct 14, 2025 · Updated Oct 13, 2026 · Sources: NIST National Vulnerability Database, CVE Program (cve.org) e CISA ADP · CNA: microsoft

Who exploits it and how urgent it is

A 0–100 score combining confirmed exploitation, ransomware and APT use, public exploits, EPSS and severity.

No exploitation signal in the sources consulted so far.
How the score was calculated
  • EPSS 1% (30-day exploitation probability)+9
  • Technical severity (high)+6
  • Automatable exploitation (SSVC)+3

The score orders the patch queue; it does not replace your asset context (internet exposure, criticality, compensating controls).

Triage

Is it exploited, how likely is exploitation, what does it touch, and how severe do the sources call it.

Exploitation
Not confirmed
Not in CISA KEV — an absence of record, not proof it is unexploited.
EPSS FIRST
1.02%
ahead of 63% of scored CVEs · Oct 14, 2026
Affects
Microsoft
Exchange Server and 5 more
CVSS base
7.5
High · 3 source(s)

CISA SSVC assessment CISA

Three decision points CISA publishes for the CVEs it assesses (SSVC 2.0.3). A stakeholder decision, not a severity score.

Exploitation
None
none · proof-of-concept · active
Automatable
Yes
can an attacker script the kill-chain steps
Technical impact
Partial
partial · total control of the vulnerable component

Remediation

Fixes and mitigations documented by the sources — linked to the original advisory.

No fix documented by the sources we poll. That does not mean none exists: check the vendor advisory.

First 24 hours

Ordered from the record’s own fields — exposure first, because you cannot patch what you have not found. A rule-generated starting point.

  1. Identify exposed assets running the affected vendor/product/version combinations (Microsoft Exchange Server, Microsoft Exchange Server Subscription Edition, Microsoft Microsoft Exchange Server 2016 Cumulative Update 23…).
  2. The attack is network-based and needs no privileges: restrict exposure (ACLs, VPN, WAF) until patched.
  3. No fix documented in the sources: reduce exposure and monitor the vendor advisory.
  4. Search available logs for exploit probes matching the vulnerability class (input validation), errors and authentication anomalies.

Affected scope

Vendor, product and versions as the sources word them.

VendorProductVersionsStatusSource
Microsoft Exchange Server version 2019-cumulative_update_13version 2016-cumulative_update_6version 2016-cumulative_update_7version 2016-cumulative_update_8version 2016-cumulative_update_9version 2019version 2019-cumulative_update_1version 2019-cumulative_update_10
and 29 more version 2019-cumulative_update_11version 2019-cumulative_update_12version 2016-cumulative_update_1version 2019-cumulative_update_2version 2019-cumulative_update_3version 2019-cumulative_update_4version 2019-cumulative_update_5version 2019-cumulative_update_6version 2019-cumulative_update_7version 2019-cumulative_update_8version 2019-cumulative_update_9version 2016-cumulative_update_4version 2016version 2016-cumulative_update_10version 2016-cumulative_update_11version 2016-cumulative_update_12version 2016-cumulative_update_13version 2016-cumulative_update_14version 2016-cumulative_update_15version 2016-cumulative_update_16version 2016-cumulative_update_17version 2016-cumulative_update_18version 2016-cumulative_update_19version 2016-cumulative_update_2version 2016-cumulative_update_20version 2016-cumulative_update_21version 2016-cumulative_update_22version 2016-cumulative_update_3version 2016-cumulative_update_5
Vulnerable NIST National Vulnerability Database
Microsoft Exchange Server Subscription Edition < 15.02.2562.029 Vulnerable NIST National Vulnerability Database
Microsoft Microsoft Exchange Server 2016 Cumulative Update 23 ≥ 15.01.0.0 and < 15.01.2507.061 Vulnerable CVE Program (cve.org) e CISA ADP
Microsoft Microsoft Exchange Server 2019 Cumulative Update 14 ≥ 15.02.0.0 and < 15.02.1544.036 Vulnerable CVE Program (cve.org) e CISA ADP
Microsoft Microsoft Exchange Server 2019 Cumulative Update 15 ≥ 15.02.0.0 and < 15.02.1748.039 Vulnerable CVE Program (cve.org) e CISA ADP
Microsoft Microsoft Exchange Server Subscription Edition RTM ≥ 15.02.0.0 and < 15.02.2562.029 Vulnerable CVE Program (cve.org) e CISA ADP

Attack characteristics

The CVSS vector, decoded. It describes the attack, not your exposure to it.

Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
High
Availability
None

Every base score collected

Sources score independently and may disagree; each row says who scored it and under which version.

ScoreVersionSeverityExpl.ImpactScored by
7.5 CVSS 3.1 High 3.9 3.6 secure@microsoft.com via NIST National Vulnerability Database
7.5 CVSS 3.1 High 3.9 3.6 nvd@nist.gov via NIST National Vulnerability Database
7.5 CVSS 3.1 High — — microsoft via CVE Program (cve.org) e CISA ADP
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N (score shown at the top: nvd@nist.gov)

Weakness MITRE

Weakness class according to MITRE’s CWE catalog.

CWE-20 · Improper Input Validation

Other CVEs with this weakness →

EPSS over time FIRST

Oct 13, 2026 → Oct 14, 2026 · 2 reading(s) · max 1.02%

Detection

Read off the CVSS vector and the weakness class. Starting points, not tested rules.

  • Prioritize edge telemetry for the network-reachable component (proxy, WAF, IDS/IPS).
web/proxy/WAF logsnetwork IDS/IPS

Timeline

What happened to this CVE, newest first.

  • 2026
  • Affected products added · microsoft/microsoft exchange server 2016 cumulative update 23, microsoft/microsoft exchange server 2019 cumulative updat
    Oct 13, 2026 · CVE Program (cve.org) e CISA ADP
  • SSVC assessment updated
    Oct 13, 2026 · CVE Program (cve.org) e CISA ADP
  • Record published
    Oct 13, 2026
  • CVSS changed · 7.5
    Oct 13, 2026 · NIST National Vulnerability Database
  • Source status changed · → Analyzed
    Oct 13, 2026 · NIST National Vulnerability Database
  • Record created in this database
    Oct 13, 2026 · NIST National Vulnerability Database
  • 2025
  • CVE published
    Oct 14, 2025 · microsoft

Source activity

Repeated readings are counted rather than listed.

  • 1× Official description updated · Oct 13, 2026 – Oct 13, 2026

References

1 on the record

Elsewhere on this site

Microsoft
every CVE for this vendor
Input validation
same class
CWE-20
other pages naming this weakness

Related CVEs (same products)

  • CVE-2026-87696 Microsoft Exchange Server Elevation of Privilege Vulnerability 2d
  • CVE-2026-87695 Microsoft Exchange Server Elevation of Privilege Vulnerability 2d
  • CVE-2026-87692 Microsoft Exchange Server Elevation of Privilege Vulnerability 2d
  • CVE-2026-77910 Microsoft Exchange Server Elevation of Privilege Vulnerability 2d
  • CVE-2026-70571 Microsoft Exchange Server Remote Code Execution Vulnerability 2d
  • CVE-2026-70279 Microsoft Exchange Server Spoofing Vulnerability 2d

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 fixed version, patch or mitigation documented.
  • 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 record

Text assembled only from the fields above — no additional claims.

What should defenders know first?

CVE-2025-59248 is "Microsoft Exchange Server Spoofing Vulnerability", rated High. It affects Exchange Server (Microsoft); versions are in the scope table. It is not in CISA KEV, which does not rule out exploitation. CVSS 7.5 describes technical severity. EPSS 1.02% estimates the probability of exploitation in 30 days; neither replaces your asset context. First verify whether exposed or business-critical assets run the affected versions, apply vendor fixes or mitigations, and preserve logs for review.

Comments

Moderated technical discussion. Read the community guidelines.

No comments yet.

Sign in or create an account to comment and suggest corrections.