CVE-2024-38226 | Microsoft Publisher Security Feature Bypass Vulnerability

Exp

Microsoft Publisher Security Feature Bypass Vulnerability

Published: 2024-09-10 Last update: 2025-10-28 Assigner: [email protected] Source: [email protected]
NVD Status：Analyzed，CVE State: published
View at NVD, CVE.org, EUVD

CVE-2024-38226 is rated Critical Active Threat (82.5/100): CVSS High severity, with medium exploitation likelihood (EPSS 1.43%). CISA KEV confirms active exploitation (added 2024-09-10) affecting Microsoft / Publisher. a weakness (CWE-693) Unauthenticated remote administrative access may be possible. The CISA remediation deadline has passed—treat as an emergency patch priority.

Risk is dynamic; we continuously reassess and refresh what is shown on this page as upstream context changes.

CISA KEV Record for CVE-2024-38226

Name: Microsoft Publisher Protection Mechanism Failure Vulnerability · CISA KEV detail

Exploit added: 2024-09-10

Action due: 2024-10-01

Required action: Apply mitigations per vendor instructions or discontinue use of the product if mitigations are unavailable.

Exploit prediction scoring system (EPSS) score for CVE-2024-38226

EPSS lead: Daily EPSS estimates relative likelihood of exploitation; percentile ranks this CVE among scored vulnerabilities (higher = more severe relative rank).

# Date Old EPSS score New EPSS score Delta (New - Old)
1 2026-01-04 1.24% 1.43% +0.19%
2 2025-11-21 36.58% 1.24% -35.34%
3 2025-11-18 — 36.58% —

Full EPSS history (19 records total)

Common vulnerability scoring system (CVSS) metrics for CVE-2024-38226

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
7.3 3.1 HIGH
CVSS:3.1/AV:L/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:H Click to expand
Attack vector (AV:L)
They already need access on the box, or another person has to do something wrong; it’s not a remote drive-by.
Attack complexity (AC:L)
Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:L)
A normal user session is enough; they don’t have to be admin.
User interaction (UI:R)
A real person has to do something—click, install, enable—otherwise it doesn’t land.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:H)
Serious risk that confidential data gets exposed in a big way.
Integrity (I:H)
They could widely tamper with or forge data—trust in the data is badly hurt.
Availability (A:H)
Could take the service down hard or make it unusable for people who depend on it.
 1.3 5.9 [email protected]

Weakness enumeration for CVE-2024-38226

Affected software / configurations for CVE-2024-38226

Vendor Product Version Raw CPE
microsoft office_2019 — cpe:2.3:a:microsoft:office_2019:-:*:*:*:*:*:x64:*
microsoft office_2019 — cpe:2.3:a:microsoft:office_2019:-:*:*:*:*:*:x86:*
microsoft office_long_term_servicing_channel 2021 cpe:2.3:a:microsoft:office_long_term_servicing_channel:2021:*:*:*:*:*:x64:*
microsoft office_long_term_servicing_channel 2021 cpe:2.3:a:microsoft:office_long_term_servicing_channel:2021:*:*:*:*:*:x86:*
microsoft publisher 2016 cpe:2.3:a:microsoft:publisher:2016:*:*:*:*:*:x64:*
microsoft publisher 2016 cpe:2.3:a:microsoft:publisher:2016:*:*:*:*:*:x86:*

References for CVE-2024-38226

cvelogic Threat Intelligence