CVE-2016-7289

CVE-2016-7289 is a high-severity vulnerability in Microsoft Publisher with a CVSS 3.x base score of 7.8. Its EPSS exploit-prediction score of 25% places it in the 98th percentile, indicating an elevated likelihood of exploitation. The underlying weakness is classified as CWE-119.

Key facts

Description

Microsoft Publisher 2010 SP2 allows remote attackers to execute arbitrary code or cause a denial of service (memory corruption) via a crafted document, aka "Microsoft Office Memory Corruption Vulnerability."

Frequently asked questions

What is CVE-2016-7289?
Microsoft Publisher 2010 SP2 allows remote attackers to execute arbitrary code or cause a denial of service (memory corruption) via a crafted document, aka "Microsoft Office Memory Corruption Vulnerability."
How severe is CVE-2016-7289?
CVE-2016-7289 has a CVSS 3.x base score of 7.8, rated high severity. It is exploitable over local access with low attack complexity, requires no privileges and user interaction. Impact on confidentiality is high, integrity high, and availability high.
Is CVE-2016-7289 being actively exploited?
It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 25% (98th percentile), an estimate of the probability of exploitation in the next 30 days.
What products are affected by CVE-2016-7289?
CVE-2016-7289 affects Microsoft Publisher. See the affected-products list for the exact vulnerable versions.
How do I fix CVE-2016-7289?
Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its high severity, prioritise patching exposed systems.
When was CVE-2016-7289 published?
CVE-2016-7289 was published on 2016-12-20 and last updated on 2026-06-17.

References

Affected products (1)

More vulnerabilities in Microsoft Publisher

All CVEs affecting Microsoft Publisher →

Other CWE-119 (Improper Restriction of Operations within the Bounds of a Memory Buffer) vulnerabilities

Browse all CWE-119 (Improper Restriction of Operations within the Bounds of a Memory Buffer) vulnerabilities →