CVE-2011-3412 in the critical feed json
Microsoft Publisher 2003 SP3, and 2007 SP2 and SP3, allows remote attackers to execute arbitrary code via a crafted Publisher file that lev…
published 2011-12-14 14 y ago modified 2026-06-16 4 mo ago also EUVD-2011-3375
- cvss
- 9.3
- version 2.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 26.4%
- EPSS 26.4% chance of exploitation in 30 days, percentile 98%
- public exploits
- 0
- none known
Summary
Microsoft Publisher 2003 SP3, and 2007 SP2 and SP3, allows remote attackers to execute arbitrary code via a crafted Publisher file that leverages incorrect memory handling, aka "Publisher Memory Corruption Vulnerability."
Exploit prediction
26.38% chance of exploitation in the next 30 days, higher than 98% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 2.0 | 9.3 | AV:N/AC:M/Au:N/C:C/I:C/A:C |
Classification
- Weakness
-
- CWE-94 Improper Control of Generation of Code
References
-
docs.microsoft.com
/en-us/security-updates/securitybulletins/2011/ms11-091
vendor-advisory
-
us-cert.gov
/cas/techalerts/TA11-347A.html
third-party-advisory, us-government-resource
-
kb.cert.org
/vuls/id/361441
third-party-advisory, us-government-resource
-
securitytracker.com
/id?1026414
vdb-entry
-
oval.cisecurity.org
/repository/search/definition/oval%3Aorg.mitre.oval%3Adef%3A14808
vdb-entry, signature
Sources
- CVE List CVE-2011-3412
- NVD CVE-2011-3412
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.