Publisher vulnerabilities: known CVEs & security history
Microsoft · Actively exploited · 43 tracked CVEs · 2 actively exploited · updated June 2026 · what is a CVE? →
This is the full list of known vulnerabilities (CVEs) across all Publisher release lines — 43 in total, with 2 actively exploited in the wild. A CVE here doesn't mean your version is affected — check Publisher's current status and the safe version to run.
Known Publisher CVEs
Actively-exploited and most-severe first. Open any CVE for full details.
| CVE | Severity | CVSS | EPSS | Year |
|---|---|---|---|---|
| CVE-2007-0671⚡ exploited | high | 8.8 | 42% | 2007 |
| CVE-2024-38226⚡ exploited | high | 7.3 | 3% | 2024 |
| CVE-2013-1322 | high | 10 | 25% | 2013 |
| CVE-2013-1320 | high | 10 | 29% | 2013 |
| CVE-2013-1319 | high | 10 | 25% | 2013 |
| CVE-2013-1318 | high | 10 | 26% | 2013 |
| CVE-2008-0102 | high | 10 | 37% | 2008 |
| CVE-2007-1117 | high | 10 | 18% | 2007 |
| CVE-2015-2503 | high | 9.3 | 17% | 2015 |
| CVE-2014-1759 | high | 9.3 | 13% | 2014 |
| CVE-2013-1329 | high | 9.3 | 21% | 2013 |
| CVE-2013-1328 | high | 9.3 | 21% | 2013 |
| CVE-2013-1327 | high | 9.3 | 21% | 2013 |
| CVE-2013-1323 | high | 9.3 | 21% | 2013 |
| CVE-2013-1321 | high | 9.3 | 22% | 2013 |
| CVE-2013-1317 | high | 9.3 | 21% | 2013 |
| CVE-2013-1316 | high | 9.3 | 22% | 2013 |
| CVE-2011-3412 | high | 9.3 | 27% | 2011 |
| CVE-2011-3411 | high | 9.3 | 28% | 2011 |
| CVE-2011-3410 | high | 9.3 | 28% | 2011 |
| CVE-2011-1508 | high | 9.3 | 14% | 2011 |
| CVE-2010-3955 | high | 9.3 | 19% | 2010 |
| CVE-2010-3954 | high | 9.3 | 21% | 2010 |
| CVE-2010-2571 | high | 9.3 | 22% | 2010 |
| CVE-2010-2570 | high | 9.3 | 25% | 2010 |
| CVE-2010-2569 | high | 9.3 | 21% | 2010 |
| CVE-2010-0479 | high | 9.3 | 23% | 2010 |
| CVE-2008-0104 | high | 9.3 | 29% | 2008 |
| CVE-2007-1754 | high | 9.3 | 33% | 2007 |
| CVE-2006-3877 | high | 9.3 | 12% | 2006 |
| CVE-2006-0001 | high | 9.3 | 40% | 2006 |
| CVE-2004-0200 | high | 9.3 | 49% | 2004 |
| CVE-2020-0760 | high | 8.8 | 9% | 2020 |
| CVE-2024-20673 | high | 7.8 | 1% | 2024 |
| CVE-2023-28295 | high | 7.8 | 1% | 2023 |
| CVE-2023-28287 | high | 7.8 | 1% | 2023 |
| CVE-2018-8245 | high | 7.8 | 15% | 2018 |
| CVE-2017-8725 | high | 7.8 | 20% | 2017 |
| CVE-2016-7289 | high | 7.8 | 25% | 2016 |
| CVE-2008-3068 | high | 7.5 | 17% | 2008 |
| CVE-2004-0573 | high | 7.5 | 42% | 2004 |
| CVE-2007-6534 | medium | 6.8 | 11% | 2007 |
| CVE-2022-29107 | medium | 5.5 | 3% | 2022 |
Is my Publisher version affected?
The list above spans every release. To know whether your version is affected — and the minimum safe version to upgrade to — check it directly.
Check your Publisher version → · Monitor Publisher for new CVEs →
Publisher vulnerabilities — frequently asked
How many known vulnerabilities does Publisher have?
IsItPatched tracks 43 CVEs for Publisher, 2 of which are actively exploited (CISA KEV). 0 are critical-severity and 41 high-severity. These span every release line — what matters is whether the version you run is affected.
Does Publisher have any actively-exploited vulnerabilities?
Yes — 2 Publisher CVEs are in CISA's Known Exploited Vulnerabilities catalog, meaning they are confirmed exploited in the wild. Patch these as a priority.
What is the most severe Publisher vulnerability?
Among tracked issues, CVE-2007-0671 (HIGH, CVSS 8.8), which is actively exploited, ranks highest.
Is Publisher safe to use?
It depends on the version. The latest supported Publisher release clears the known issues; older versions may still be affected. Check the exact version you run for a verdict.
CVE data aggregated from NVD, CISA KEV and EPSS (FIRST.org). Related: Publisher security status · Publisher end-of-life · actively-exploited CVEs. Always verify against Microsoft's advisories — see our disclaimer.