Publisher ↗
Auto-added after CISA flagged Publisher as actively exploited (KEV catalog). Version and lifecycle mapping is pending review, so this is assessed at the product level and is never reported as a confident "healthy".
Summary iPlain-English security verdict for Publisher, generated from its current health score, actively-exploited vulnerabilities, and latest supported version.
Publisher currently scores 20/100 — critical, with active exploitation. 1 of its known vulnerability is being actively exploited in the wild (CISA KEV), including CVE-2024-38226. Upgrade immediately and review your exposure to the actively-exploited CVEs below.
The known vulnerabilities
IsItPatched tracks 4 known vulnerabilities in Microsoft Publisher disclosed between 2024 and 2026. CVE-2024-20673 is a high-severity vulnerability (CVSS 7.8). CVE-2024-38226 is a high-severity vulnerability (CVSS 7.3), which is actively exploited in the wild (CISA KEV). CVE-2026-69742 is a high-severity integer overflow vulnerability (CVSS 8.8). CVE-2026-81385 is a high-severity insecure deserialization vulnerability (CVSS 8.8). Move to a patched, supported release — this issue is being exploited in the wild, so treat it as urgent.
Disclosure trend iNew CVEs published for Publisher each year (NVD). A higher bar means more disclosures that year — more scrutiny, not necessarily less safe.
Patch priority — what to act on iThe issues to fix first — actively exploited (CISA KEV) first, then by exploitation probability (EPSS), then severity. Each row's "→ fixed in" is the earliest version that patches it; "see advisory" means no fixed version is published.
Most urgent first — actively exploited, then likeliest to be exploited.
CVE-2024-38226 HIGH exploited CWE-693 EPSS 3% → see advisoryGet alerted about Publisher
Be emailed the moment Publisher gets a newly exploited vulnerability (CISA KEV) or a release reaches end of life. Free · double opt-in · unsubscribe anytime.
We email only on real events for Publisher — no marketing, no sharing, and we never know what you run. Track your whole stack →
Frequently asked
Is Publisher safe and patched?
Publisher currently scores 20/100 — critical, with active exploitation. 1 of its known vulnerability is being actively exploited in the wild (CISA KEV), including CVE-2024-38226. Upgrade immediately and review your exposure to the actively-exploited CVEs below.
What should I do about Publisher now?
Review the patch-priority list, apply the available fixes (or move to the latest release), and confirm against Microsoft's official advisory. Some issues are under active exploitation, so treat this as urgent.
Why is Publisher listed on IsItPatched?
Publisher was added automatically because CISA's Known Exploited Vulnerabilities (KEV) catalog flagged it as actively exploited in the wild. IsItPatched tracks its known CVEs, severity (CVSS), exploitation probability (EPSS) and KEV status from public data; its version and lifecycle mapping is verified over time.
Has Publisher been actively exploited?
Yes. CISA added Publisher to its Known Exploited Vulnerabilities (KEV) catalog after confirming exploitation in the wild — the triggering vulnerability is CVE-2024-38226. Make sure you are running a patched, supported version of Publisher and confirm it against Microsoft's security advisory.
Similar software we track
More from Microsoft tracked on IsItPatched.
lifecycle unknown — needs latest supported version
Informational only, from public data (NVD · CISA KEV · EPSS · endoflife.date), and can lag or miss vendor-specific fixes. Always confirm against Microsoft's official advisory before you patch or upgrade — Publisher official site ↗