Microsoft Defender Antimalware Platform UnDefend denial of service
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 4.9 | $0-$5k | 0.00 |
Summary
A vulnerability identified as problematic has been detected in Microsoft Defender Antimalware Platform. The impacted element is an unknown function. The manipulation leads to denial of service. This vulnerability is uniquely identified as CVE-2026-45498. Local access is required to approach this attack. Moreover, an exploit is present.
Details
A vulnerability was found in Microsoft Defender Antimalware Platform (affected version not known). It has been rated as problematic. This issue affects some unknown functionality. The manipulation with an unknown input leads to a denial of service vulnerability. Using CWE to declare the problem leads to CWE-404. The product does not release or incorrectly releases a resource before it is made available for re-use. Impacted is availability.
The advisory is shared at msrc.microsoft.com. The identification of this vulnerability is CVE-2026-45498 since 05/12/2026. The exploitation is known to be easy. An attack has to be approached locally. Technical details are unknown but an exploit is available.
It is declared as attacked. The vulnerability scanner Nessus provides a plugin with the ID 316484 (Windows Defender < 4.18.26040.7 DoS (CVE-2026-45498)), which helps to determine the existence of the flaw in a target environment. The CISA Known Exploited Vulnerabilities Catalog lists this issue since 05/20/2026 with a due date of 06/03/2026:
Apply mitigations per vendor instructions, follow applicable BOD 22-01 guidance for cloud services, or discontinue use of the product if mitigations are unavailable.The vulnerability is also documented in the databases at Zero-Day.cz (1100), Tenable (316484) and EUVD (EUVD-2026-31102). If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Product
Type
Vendor
Name
License
Website
- Vendor: https://www.microsoft.com/
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 4.9VulDB Meta Temp Score: 4.9
VulDB Base Score: 3.3
VulDB Temp Score: 3.2
VulDB Vector: 🔒
VulDB Reliability: 🔍
NVD Base Score: 7.5
NVD Vector: 🔒
CNA Base Score: 4.0
CNA Vector (microsoft): 🔒
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍
Exploiting
Class: Denial of serviceCWE: CWE-404
CAPEC: 🔒
ATT&CK: 🔒
Physical: Partially
Local: Yes
Remote: Yes
Availability: 🔒
Status: Attacked
EPSS Score: 🔒
EPSS Percentile: 🔒
KEV Added: 🔒
KEV Due: 🔒
KEV Remediation: 🔒
KEV Ransomware: 🔒
KEV Notice: 🔒
Price Prediction: 🔍
Current Price Estimation: 🔒
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Nessus ID: 316484
Nessus Name: Windows Defender < 4.18.26040.7 DoS (CVE-2026-45498)
Zero-Day.cz: 🔒
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: no mitigation knownStatus: 🔍
0-Day Time: 🔒
Timeline
05/12/2026 CVE reserved05/20/2026 Advisory disclosed
05/20/2026 VulDB entry created
05/30/2026 VulDB entry last update
Sources
Vendor: microsoft.comAdvisory: msrc.microsoft.com
Status: Confirmed
CVE: CVE-2026-45498 (🔒)
GCVE (CVE): GCVE-0-2026-45498
GCVE (VulDB): GCVE-100-364877
EUVD: 🔒
scip Labs: https://www.scip.ch/en/?labs.20161013
Entry
Created: 05/20/2026 15:40Updated: 05/30/2026 06:35
Changes: 05/20/2026 15:40 (60), 05/20/2026 22:14 (13), 05/21/2026 01:40 (1), 05/22/2026 16:12 (2), 05/22/2026 22:38 (2), 05/23/2026 22:24 (11), 05/30/2026 06:35 (1)
Complete: 🔍
Cache ID: 216::103
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
No comments yet. Languages: en.
Please log in to comment.