Exploited vulnerabilities / CVE-2012-1854
Confirmed exploited · remote code execution · Microsoft Visual Basic for Applications (VBA)CVE-2012-1854
Microsoft Visual Basic for Applications (VBA) remote code execution, confirmed exploited in the wild.
Microsoft Visual Basic for Applications (VBA) contains an insecure library loading vulnerability that could allow for remote code execution.
| CISA's name for it | Microsoft Visual Basic for Applications Insecure Library Loading Vulnerability |
|---|---|
| Vendor and product | Microsoft · Visual Basic for Applications (VBA) |
| Type | remote code execution · CWE-426 |
| Exploited | Confirmed by CISA listed 13 April 2026 |
| Likelihood | one of the most likely to be exploited of every vulnerability tracked |
| Deadline | 27 April 2026 · already passed |
| Used in ransomware | Not reported |
| Advisories | learn.microsoft.com ↗ · nvd.nist.gov ↗ |
Three steps, in this order
Patch to the fixed version the vendor names, today if the product faces the internet.
Until it is patched, take the affected service off the internet or put it behind a VPN or allow-list.
Look for signs it was already used: new accounts, web shells, unexpected processes and outbound connections since the date it was listed.
| CISA's required action | Apply mitigations per vendor instructions, follow applicable BOD 22-01 guidance for cloud services, or discontinue use of the product if mitigations are unavailable. |
|---|
Know before someone else finds it
Threat Landscape Monitoring fingerprints the software your internet-facing hosts disclose and matches it, every day, against this list and the exploitation scores. When a new entry touches something you run, you are told once, with the host and the fix. The free plan covers one domain.
CVE-2012-1854 in short
Is CVE-2012-1854 being exploited?
Yes. CISA added CVE-2012-1854 to its Known Exploited Vulnerabilities catalogue on 13 April 2026, which it does only on evidence of exploitation in the wild.
What is the CISA deadline for CVE-2012-1854?
US federal agencies must remediate it by 27 April 2026. Everyone else should treat that date as the latest safe point to patch an internet-facing system.
How likely is CVE-2012-1854 to be exploited in the next 30 days?
FIRST's Exploit Prediction Scoring System gives it 21%, the 97th percentile of every CVE it scores.
How do I fix CVE-2012-1854?
Patch to the fixed version the vendor names, today if the product faces the internet. Until it is patched, take the affected service off the internet or put it behind a VPN or allow-list. Look for signs it was already used: new accounts, web shells, unexpected processes and outbound connections since the date it was listed.
Other Microsoft vulnerabilities being exploited
| CVE | Product | Type | Listed |
|---|---|---|---|
| CVE-2026-124194 | Office | exploited vulnerability | 10 November 2026 |
| CVE-2026-96951 | Windows | command injection | 13 October 2026 |
| CVE-2026-65660 | SharePoint | exploited vulnerability | 25 September 2026 |
| CVE-2026-81963 | Windows | privilege escalation | 8 September 2026 |
| CVE-2026-85880 | Windows | privilege escalation | 8 September 2026 |
| CVE-2019-1068 | SQL Server | remote code execution | 26 August 2026 |
Sources: CISA Known Exploited Vulnerabilities catalogue (released 10 November 2026) and FIRST EPSS. Page compiled automatically by SAK T.L.M, the threat-intelligence tool of SAK T.E.C, on 13 November 2026.