Microsoft Visual Basic for Applications (VBA): code execution flaw under attack

What is affected

Microsoft Visual Basic for Applications (VBA) is mostly run by companies, schools and public bodies, not on home computers. You are unlikely to have it yourself, but organisations that hold your data may. Breaches that start with flaws like this one are how personal data ends up leaked.

Microsoft Visual Basic for Applications (VBA) contains an insecure library loading vulnerability that could allow for remote code execution.

What an attacker can do

This is a code execution flaw. It lets an attacker run their own commands or programs on the affected system. In practice that usually means taking it over: installing malware, stealing data or using it to reach other devices on the same network.

How it is reached

Needs access to the device or a file opened on it

Access the attacker needs

No account needed

Does the victim have to do something?

Yes, the victim must open or click something

What to do

1. At home: nothing to install. Keep your own devices updated and use a different password for every service, so that a breach at one organisation does not open your other accounts.
2. If you administer Microsoft Visual Basic for Applications (VBA) at work: apply the vendor's fix or mitigation now and review logs for signs of compromise, because the flaw was being exploited before it was listed.
3. If the product is past its support date and no fix exists, take it off the internet or retire it.

Apply mitigations per vendor instructions, follow applicable BOD 22-01 guidance for cloud services, or discontinue use of the product if mitigations are unavailable.

Vendor advisories and fixes

• learn.microsoft.comlearn.microsoft.com/en-us/security-updates/securitybulletins/2012/ms12-046

How urgent is it

CISA added this vulnerability to its Known Exploited Vulnerabilities catalogue on April 13, 2026, which means there is reliable evidence of attacks in the wild. US federal agencies must fix it by April 27, 2026, a deadline that has already passed. That deadline does not bind anyone else, but it shows how seriously the agency rates it.

The EPSS model estimates a 21% probability that this flaw will be exploited somewhere in the next 30 days. That is higher than 98% of all scored vulnerabilities.

Its CVSS severity score is 7.8 out of 10 (high), as recorded in the US National Vulnerability Database.

Technical description

Untrusted search path vulnerability in VBE6.dll in Microsoft Office 2003 SP3, 2007 SP2 and SP3, and 2010 Gold and SP1; Microsoft Visual Basic for Applications (VBA); and Summit Microsoft Visual Basic for Applications SDK allows local users to gain privileges via a Trojan horse DLL in the current working directory, as demonstrated by a directory that contains a .docx file, aka "Visual Basic for Applications Insecure Library Loading Vulnerability," as exploited in the wild in July 2012.