Skip to content
Server Security Center
KEVhigh7.3

CVE-2024-38226: Microsoft Publisher Protection Mechanism Failure

Microsoft Publisher · listed in the CISA catalog of actively exploited vulnerabilities since 2024-09-10.

CVSS v3.1 (CVE record)
7.3
high
EPSS (exploit probability, 30 days)
2.7%
higher than 86.1% of all CVEs
Added to CISA KEV
2024-09-10
US federal due date 2024-10-01
Automatable (CISA SSVC)
no
technical impact: total

CVE-2024-38226 explained

CVE-2024-38226 is a protection mechanism failure in Microsoft Publisher. It lets an attacker bypass the Office macro policies that are meant to block untrusted or malicious files. CISA lists it as known to be exploited, so organizations relying on macro blocking to stop malicious documents should treat it as a priority.

Impact

An attacker who bypasses Office macro policies can get untrusted or malicious content past a key defence. The attack is local, needs low privileges and requires user interaction, such as opening a file. Successful exploitation can fully compromise confidentiality, integrity and availability. CISA rates the technical impact as total but not automatable, meaning each attack needs manual steps. Attackers are known to use this vulnerability. Ransomware use is unknown.

Who is affected

The CVE record lists Microsoft Publisher 2016 (32-bit and x64) versions before 16.0.5465.1001 as affected, fixed in 16.0.5465.1001. Microsoft Office 2019 and Microsoft Office LTSC 2021 (32-bit and x64) are affected in builds before the fixed release. For these two products the record names no fixed version and points to the vendor release notes.

Written with AI from the data on this page and checked against it automatically.

Official description

Microsoft Publisher contains a protection mechanism failure vulnerability that allows attacker to bypass Office macro policies used to block untrusted or malicious files.

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

CISA notes

Affected and fixed versions

From the CVE record published by the vendor or CVE numbering authority.

  • Microsoft Office 201932-bit, x64
    Affected
    • builds before the fixed release (see vendor release notes)
    Fixed in
  • Microsoft Office LTSC 202132-bit, x64
    Affected
    • builds before the fixed release (see vendor release notes)
    Fixed in
  • Microsoft Publisher 201632-bit, x64
    Affected
    • < 16.0.5465.1001
    Fixed in
    • 16.0.5465.1001

How to fix it

  • Update to the fixed version for your product:
    • Microsoft Publisher 2016: 16.0.5465.1001
    For the other affected products the CVE record names no fixed version – see the table and the vendor advisory.
  • Vendor advisory: msrc.microsoft.com/update-guide/vulnerability/CVE-2024-38226
  • CISA's deadline for US federal agencies: 2024-10-01 (passed) – a useful benchmark for everyone else, too.

What to do

  1. Update Microsoft Publisher 2016 to 16.0.5465.1001 or later.
  2. Update Microsoft Office 2019 and Microsoft Office LTSC 2021 to the fixed build named in Microsoft's advisory and release notes.
  3. Apply mitigations per vendor instructions, as CISA requires, or discontinue use of Publisher if mitigations are unavailable.
  4. Warn users not to open Publisher files from untrusted sources until updates are confirmed.
  5. Check endpoints for signs of compromise from suspicious Publisher files.

For Microsoft Office 2019 and Microsoft Office LTSC 2021, the CVE record names no fixed version. Check Microsoft's advisory and release notes for the fixed build and install it. Until it is confirmed, follow CISA's required action: apply the vendor's mitigations, or stop using the product if mitigations are unavailable. Do not let users open untrusted Publisher files in the meantime.

Written with AI from the data on this page and checked against it automatically.

CISA's assessment (SSVC)

Exploitation
Exploited in the wild
Automatable
No – each attack needs manual steps
Technical impact
Total – full control of the component or total information disclosure

Weakness: CWE-693 Protection Mechanism Failure

Questions about CVE-2024-38226

Is CVE-2024-38226 being exploited?
Yes. CISA added it to its Known Exploited Vulnerabilities catalog on 2024-09-10, with a US federal due date of 2024-10-01. Whether it has been used in ransomware campaigns is unknown.
Can it be exploited remotely without user action?
No. The attack vector is local, it requires low privileges, and a user must interact, for example by opening a file. CISA rates it as not automatable.
Which version fixes Publisher 2016?
Microsoft Publisher 2016 is fixed in 16.0.5465.1001. For Office 2019 and Office LTSC 2021, the record refers to the vendor release notes for the fixed build.

Written with AI from the data on this page and checked against it automatically.

References

Data: CISA Known Exploited Vulnerabilities (public domain) · CVE Program records incl. CISA ADP enrichment · OSV.dev (CC BY 4.0) incl. Ubuntu and Debian security data · FIRST EPSS · endoflife.date. Updated automatically – facts last changed 2026-11-22. Always confirm with the vendor's or distribution's advisory before patching.