Publisher vulnerabilitiesAnd the versions its exploited flaws hit.

Product2 known exploited7 versions
The short answer

Publisher is made by Microsoft. We track 43 published vulnerabilities in it, across 7 versions. 2 of them are on the list of flaws known to be exploited, the newest added on 12 August 2025. If you run Publisher, check your version against the exploited flaws below and patch those first.

Check your version

The most recent Publisher flaw added to the known-exploited list is CVE-2007-0671, on 12 August 2025. We keep watching the known-exploited list.

Versions

Which versions of Publisher do the exploited flaws hit?

Each exploited flaw lists the versions it affects, as published by the vendor. Find your version, then patch.

  • CVE-2007-0671Exploited list, 12 Aug 2025

    Microsoft Office Excel Remote Code Execution Vulnerability

    200020022003
  • CVE-2024-38226Exploited list, 10 Sep 2024

    Microsoft Publisher Protection Mechanism Failure Vulnerability

    2016
Known exploited

Which Publisher vulnerabilities are being exploited?

2 flaws are on the government list of vulnerabilities known to be exploited. These are the ones criminals are using now, so they go first, whatever their severity score says.

  1. 8.8
    CVE-2007-0671HighKnown exploited
    Microsoft Office Excel Remote Code Execution Vulnerability

    Microsoft Office Excel contains a remote code execution vulnerability that can be exploited when a specially crafted Excel file is opened.

    Chance of use43%Known exploited since12 Aug 2025
  2. 7.3
    CVE-2024-38226HighKnown exploited
    Microsoft Publisher Protection Mechanism Failure Vulnerability

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

    Chance of use2.7%Known exploited since10 Sep 2024
Exploit likelihood

Which Publisher flaws are most likely to be used?

Ranked by the latest exploit-likelihood forecast: the chance each flaw is used in an attack in the next 30 days. A high severity score on its own doesn't tell you that. Flaws shared by many other makers' products are left out.

50% or more10% to 49%Under 10%
  1. 49%

    Buffer overflow in the JPEG (JPG) parsing engine in the Microsoft Graphic Device Interface Plus (GDI+) component, GDIPlus.dll, allows remote attackers to execute arbitrary code via a JPEG image with a small JPEG COM...

    CVSS9.3Published28 Sep 2004
  2. 43%
    CVE-2007-0671HighKnown exploited

    Unspecified vulnerability in Microsoft Excel 2000, XP, 2003, and 2004 for Mac, and possibly other Office products, allows remote user-assisted attackers to execute arbitrary code via unknown attack vectors, as...

    CVSS8.8Published3 Feb 2007
  3. 42%

    Stack-based buffer overflow in Microsoft Publisher 2000 through 2003 allows user-assisted remote attackers to execute arbitrary code via a crafted PUB file, which causes an overflow when parsing fonts.

    CVSS9.3Published12 Sep 2006
  4. 37%

    Unspecified vulnerability in Microsoft Office Publisher 2000, 2002, and 2003 SP2 allows remote attackers to execute arbitrary code via a crafted .pub file, related to invalid "memory values," aka "Publisher Invalid...

    CVSS10.0Published12 Feb 2008
  5. 33%

    PUBCONV.DLL in Microsoft Office Publisher 2007 does not properly clear memory when transferring data from disk to memory, which allows user-assisted remote attackers to execute arbitrary code via a malformed .pub...

    CVSS9.3Published10 Jul 2007
  6. 29%

    Buffer overflow in Microsoft Publisher 2003 SP3 allows remote attackers to execute arbitrary code via a crafted Publisher file, aka "Publisher Buffer Overflow Vulnerability."

    CVSS10.0Published15 May 2013
  7. 29%

    Unspecified vulnerability in Microsoft Office Publisher 2000, 2002, and 2003 SP2 allows remote attackers to execute arbitrary code via a crafted .pub file, aka "Publisher Memory Corruption Vulnerability."

    CVSS9.3Published12 Feb 2008
  8. 29%

    Array index error in Microsoft Publisher 2003 SP3, and 2007 SP2 and SP3, allows remote attackers to execute arbitrary code via a crafted Publisher file that leverages incorrect handling of values in memory, aka...

    CVSS9.3Published14 Dec 2011
  9. 27%

    Microsoft Publisher 2003 SP3 allows remote attackers to execute arbitrary code via a crafted Publisher file that leverages incorrect handling of values in memory, aka "Publisher Invalid Pointer Vulnerability."

    CVSS9.3Published14 Dec 2011
Precursor Intelligence

Running Publisher? We'll keep checking.

Looking flaws up one at a time doesn't scale. Tell us what you run once, and we tell you which flaws matter to you, in what order, and keep watching for new ones.

  1. Tell us what you runPick your software from a list, or let us work it out from your website.
  2. We match it to every flawOver 400,000 published flaws, checked against your list.
  3. Ranked by real-world riskA 0 to 100 score, led by evidence criminals are using it.
  4. Told as soon as we knowAn alert by email, in the app or by webhook to your own tools.

Free plan, no card needed. Nothing to install.

FAQ

Common questions, answered plainly.

Something else? Talk to the team →

We track 43 published vulnerabilities listed under the name Publisher, across 7 versions. The most recent Publisher flaw added to the known-exploited list is CVE-2007-0671, on 12 August 2025.

2 are on the list of flaws known to be exploited. The most recently added are CVE-2007-0671 and CVE-2024-38226.

Each flaw names its own versions, usually as ranges. The newest, CVE-2007-0671, affects 2000, 2002, 2003. The versions for every exploited flaw are listed on this page.

Create a Precursor Intelligence account and track Publisher. We match it against every published flaw, give each one a risk score from 0 to 100 and keep watching, so you hear about new ones as soon as we know, by email, in the app or by webhook.