CVE-2016-0132 in the critical feed json
Microsoft .NET Framework 2.0 SP2, 3.0 SP2, 3.5, 3.5.1, 4.5.2, 4.6, and 4.6.1 mishandles signature validation for unspecified elements of XM…
published 2016-03-09 10 y ago modified 2026-06-17 4 mo ago also EUVD-2016-0170
- cvss
- 9.8
- version 3.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 21.5%
- EPSS 21.5% chance of exploitation in 30 days, percentile 97%
- public exploits
- 0
- none known
Summary
Microsoft .NET Framework 2.0 SP2, 3.0 SP2, 3.5, 3.5.1, 4.5.2, 4.6, and 4.6.1 mishandles signature validation for unspecified elements of XML documents, which allows remote attackers to spoof signatures via a modified document, aka ".NET XML Validation Security Feature Bypass."
Exploit prediction
21.46% chance of exploitation in the next 30 days, higher than 97% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.0 | 9.8 | CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H |
| NVD | 2.0 | 10.0 | AV:N/AC:L/Au:N/C:C/I:C/A:C |
Classification
- Weakness
-
- CWE-20 Improper Input Validation
References
-
docs.microsoft.com
/en-us/security-updates/securitybulletins/2016/ms16-035
vendor-advisory
-
securityfocus.com
/bid/84075
vdb-entry
-
securitytracker.com
/id/1035213
vdb-entry
Sources
- CVE List CVE-2016-0132
- NVD CVE-2016-0132
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.