Visual Basic for Applications vulnerabilitiesAnd the versions its exploited flaws hit.
Visual Basic for Applications is made by Microsoft. We track 2 published vulnerabilities listed under that exact name, across 0 versions. 1 of them is on the list of flaws known to be exploited, the newest added on 13 April 2026. Microsoft lists newer releases under their own names, such as Visual Basic for Applications SDK, so check those pages too.
The most recent Visual Basic for Applications flaw added to the known-exploited list is CVE-2012-1854, on 13 April 2026. We keep watching the known-exploited list.
Is Visual Basic for Applications listed under other names? Yes.
Microsoft also lists Visual Basic for Applications under more specific names, such as Visual Basic for Applications SDK. Flaws listed only under those names are counted on their own pages, not here. If you run one of these, open its page for its own exploited flaws.
Which versions of Visual Basic for Applications do the exploited flaws hit?
Each exploited flaw lists the versions it affects, as published by the vendor. Find your version, then patch.
- CVE-2012-1854Exploited list, 13 Apr 2026
Microsoft Visual Basic for Applications Insecure Library Loading Vulnerability
all versions
Which Visual Basic for Applications vulnerabilities are being exploited?
1 flaw is on the government list of vulnerabilities known to be exploited. These are the ones criminals are using now, so they go first, whatever their severity score says.
- 6.9Microsoft Visual Basic for Applications Insecure Library Loading Vulnerability
Microsoft Visual Basic for Applications (VBA) contains an insecure library loading vulnerability that could allow for remote code execution.
Running Visual Basic for Applications? We'll keep checking.
Looking flaws up one at a time doesn't scale. Tell us what you run once, and we tell you which flaws matter to you, in what order, and keep watching for new ones.
- Tell us what you runPick your software from a list, or let us work it out from your website.
- We match it to every flawOver 400,000 published flaws, checked against your list.
- Ranked by real-world riskA 0 to 100 score, led by evidence criminals are using it.
- Told as soon as we knowAn alert by email, in the app or by webhook to your own tools.
Free plan, no card needed. Nothing to install.
1 flaw being exploited affects software Acme tracks
Microsoft Visual Basic for Applications (VBA) contains an insecure library loading vulnerability that could allow for remote code execution.
- Matched to
- Visual Basic for Applications on Acme's software list
- What to do
- Patch first, then check for signs of use
Sent to the alert recipients Acme chose. Also in the app and to Acme's webhook.
We track 2 published vulnerabilities listed under the name Visual Basic for Applications, across 0 versions. The most recent Visual Basic for Applications flaw added to the known-exploited list is CVE-2012-1854, on 13 April 2026.
1 is on the list of flaws known to be exploited. The most recently added is CVE-2012-1854.
Microsoft also lists Visual Basic for Applications under more specific names, such as Visual Basic for Applications SDK. Flaws listed only under those names are counted on their own pages, not here. Open the release you run to see its own list.
Each flaw names its own versions, usually as ranges. The newest, CVE-2012-1854, affects all versions. The versions for every exploited flaw are listed on this page.
Create a Precursor Intelligence account and track Visual Basic for Applications. We match it against every published flaw, give each one a risk score from 0 to 100 and keep watching, so you hear about new ones as soon as we know, by email, in the app or by webhook.