Skip to content
Fencer Intel
medium 4.0

CVE-2026-45498 kev in the critical feed json

Microsoft Defender Denial of Service Vulnerability

published 5mo ago modified 2mo ago also EUVD-2026-31102

cvss
4.0
version 3.1, CNA
cisa kev
Exploited
added 2026-05-20
epss
63.1%
EPSS 63.1% chance of exploitation in 30 days, percentile 99.2%
public exploits
0
none known

Summary

Microsoft Defender Denial of Service Vulnerability

Patch / fix

cisa required action Apply mitigations per vendor instructions, follow applicable BOD 22-01 guidance for cloud services, or discontinue use of the product if mitigations are unavailable.

  • Microsoft Microsoft Defender Antimalware Platform 4.18.26040.7

Is CVE-2026-45498 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Timeline

  1. Added to CISA KEV
  2. Published
  3. CISA SSVC: exploitation active
  4. CISA patch deadline

Known exploited

Added
5mo ago
Patch by
2026-06-03 (5mo ago)
Ransomware
Not known
Required action
Apply mitigations per vendor instructions, follow applicable BOD 22-01 guidance for cloud services, or discontinue use of the product if mitigations are unavailable.
Vendor, product
Microsoft, Defender
CISA name
Microsoft Defender Denial of Service Vulnerability

CISA SSVC

Exploitation
Active, exploited in the wild
Automatable
no
Technical impact
partial
Assessed
5mo ago

Exploit prediction

63.08% chance of exploitation in the next 30 days, higher than 99.2% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by version score vector
CNA 3.1 4.0 CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L/E:U/RL:O/RC:C
CNA 3.1 4.0 CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L
NVD 3.1 7.5 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

Affected products

  • Microsoft Microsoft Defender Antimalware Platform

Classification

Weakness
  • CWE-400 Uncontrolled Resource Consumption

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.