Microsoft Publisher Protection Mechanism Failure Vulnerability
Microsoft — Microsoft Office 2019
Microsoft Publisher Security Feature Bypass Vulnerability
7.3
2.7%
Vector breakdown
- Attack vector
- Local
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
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
- Published
- Sep 10, 2024
- Modified
- Aug 10, 2026
- Added to KEV
- Sep 10, 2024
- Federal patch due
- Oct 1, 2024
CISA required action
Apply mitigations per vendor instructions or discontinue use of the product if mitigations are unavailable.
Weakness classification
Proof-of-concept & exploitation references
Weaponization
Public repositories whose name or description references CVE-2024-38226, found via a live GitHub search at request time. These are community-sourced signals, not a verified working exploit — cross-check each one before relying on it, and treat higher star counts and recent activity as (weak) corroboration, not proof.
No public GitHub repositories referencing CVE-2024-38226 were found at last check. Absence here is not proof no exploit exists — see the references below for vendor advisories and write-ups.
References
Frequently asked questions
What is CVE-2024-38226?
Microsoft Publisher Security Feature Bypass Vulnerability
How severe is CVE-2024-38226?
CVE-2024-38226 has a CVSS base score of 7.3 out of 10 (CVSS 3.1).
Is CVE-2024-38226 actively exploited in the wild?
Yes. CVE-2024-38226 is listed in the CISA Known Exploited Vulnerabilities (KEV) catalog, added Sep 10, 2024, meaning CISA has confirmed evidence of active exploitation.
What is the EPSS score for CVE-2024-38226?
2.7% - meaning FIRST.org's EPSS model estimates a 2.7% probability this vulnerability will be exploited in the wild within 30 days (85% percentile among all scored CVEs).
What type of vulnerability is CVE-2024-38226?
CVE-2024-38226 is classified under CWE-693 (CWE-693: Protection Mechanism Failure).
Cross-checked against
Impactr finds and proves whether CVE-2024-38226 — or flaws like it — are actually reachable in your own web apps and APIs, with a reproducible exploit as evidence.