CVE-2024-38226 kev in the critical feed json
Microsoft Publisher Security Feature Bypass Vulnerability
published 2024-09-10 2 y ago modified 2026-08-10 2 mo ago also EUVD-2024-37192
- cvss
- 7.3
- version 3.1, CNA
- cisa kev
- Exploited
- added 2024-09-10
- epss
- 2.7%
- EPSS 2.7% chance of exploitation in 30 days, percentile 85%
- public exploits
- 0
- none known
Summary
Microsoft Publisher Security Feature Bypass Vulnerability
Patch / fix
cisa required action Apply mitigations per vendor instructions or discontinue use of the product if mitigations are unavailable.
- Microsoft Microsoft Publisher 2016 16.0.5465.1001
Timeline
- Added to CISA KEV
- Published
- CISA SSVC: exploitation active
- CISA patch deadline
Known exploited
- Added
- 2 y ago
- Patch by
- 2024-10-01 (2 y ago)
- Ransomware
- Not known
- Required action
- Apply mitigations per vendor instructions or discontinue use of the product if mitigations are unavailable.
- Vendor, product
- Microsoft, Publisher
- CISA name
- Microsoft Publisher Protection Mechanism Failure Vulnerability
CISA SSVC
- Exploitation
- Active, exploited in the wild
- Automatable
- no
- Technical impact
- total
- Assessed
- 2 y ago
Exploit prediction
2.67% chance of exploitation in the next 30 days, higher than 85% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 7.3 | CVSS:3.1/AV:L/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:H/E:F/RL:O/RC:C |
| CNA | 3.1 | 7.3 | CVSS:3.1/AV:L/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:H |
Affected products
- Microsoft Microsoft Office 2019
- Microsoft Microsoft Office LTSC 2021
- Microsoft Microsoft Publisher 2016
Classification
- Weakness
-
- CWE-693 Protection Mechanism Failure
References
-
msrc.microsoft.com
/update-guide/vulnerability/CVE-2024-38226
vendor-advisory, patch
-
cisa.gov
/known-exploited-vulnerabilities-catalog?field_cve=CVE-2024-38226
government-resource, us-government-resource
Sources
- CVE List CVE-2024-38226
- NVD CVE-2024-38226
Fencer Vulns 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.