CVE-2016-10717 json
A vulnerability in the encryption and permission implementation of Malwarebytes Anti-Malware consumer version 2.2.1 and prior (fixed in 3.0…
published 2018-03-21 8 y ago modified 2026-06-17 4 mo ago also EUVD-2016-1716
- cvss
- 7.8
- version 3.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 1.2%
- EPSS 1.2% chance of exploitation in 30 days, percentile 69%
- public exploits
- 0
- none known
Summary
A vulnerability in the encryption and permission implementation of Malwarebytes Anti-Malware consumer version 2.2.1 and prior (fixed in 3.0.4) allows an attacker to take control of the whitelisting feature (exclusions.dat under %SYSTEMDRIVE%\ProgramData) to permit execution of unauthorized applications including malware and malicious websites. Files blacklisted by Malwarebytes Malware Protect can be executed, and domains blacklisted by Malwarebytes Web Protect can be reached through HTTP.
Exploit prediction
1.24% chance of exploitation in the next 30 days, higher than 69% of all scored CVEs (FIRST EPSS, 2026-11-09).
Exploits and checks
- github.com https://github.com/mspaling/mbam-exclusions-poc-/blob/master/mbam-whitelist-poc.txt referenced PoC, tagged "exploit" by a source, unverified
- github.com https://github.com/mspaling/mbam-exclusions-poc- referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.0 | 7.8 | CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H |
| NVD | 2.0 | 4.6 | AV:L/AC:L/Au:N/C:P/I:P/A:P |
Classification
- Weakness
-
- CWE-254 7PK - Security Features
References
-
github.com
/mspaling/mbam-exclusions-poc-/blob/master/mbam-whitelist-poc.txt
exploit, third-party-advisory
-
github.com
/mspaling/mbam-exclusions-poc-
exploit, third-party-advisory
-
forums.malwarebytes.com
/topic/158251-malwarebytes-hall-of-fame/
vendor-advisory
-
youtube.com
/watch?v=LF5ic5nOoUY
third-party-advisory
-
securitytube.net
/video/16690
third-party-advisory
Sources
- CVE List CVE-2016-10717
- NVD CVE-2016-10717
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.