CVE-2016-3236

CRITICALNVD 9.89.8—
EchelonGraph scoreMEDIUM confidence

Score 9.8 from GitHub Security Advisory (severity: CRITICAL) published 2022-05-14. NVD baseline CVSS 9.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
Weaponized
9.8
EchelonGraph verdictPatch this weekExploitation is likely or a public exploit exists.
  • High exploitation likelihood — EPSS 78%
CISA-KEV: Not listedEPSS: 78%CVSS: 9.8Exploit: NoneExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

The Web Proxy Auto Discovery (WPAD) protocol implementation in Microsoft Windows Vista SP2, Windows Server 2008 SP2 and R2 SP1, Windows 7 SP1, Windows 8.1, Windows Server 2012 Gold and R2, Windows RT 8.1, and Windows 10 Gold and 1511 mishandles proxy discovery, which allows remote attackers to redirect network traffic via unspecified vectors, aka "Windows WPAD Proxy Discovery Elevation of Privilege Vulnerability."

CVSS v3
9.8
EG Score
9.8(medium)
EG Risk
80(Track*)
EG Risk 80/100SSVC: Track*

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity98% × 45%
Exploitation78% × 40%
Automatability30% × 15%
Action: Watch closely — could escalate to Attend.
EPSS
99.5%
KEV
Not listed

Published

June 16, 2016

Last Modified

May 6, 2026

Advisory Details (1)

Auto-updated May 8, 2026
No patch confirmed yet.
generic

Microsoft Security Bulletin MS16-077 - Important | Microsoft Learn

https://docs.microsoft.com/en-us/security-updates/securitybulletins/2016/ms16-077

All Vendor Advisories

(1)

Every vendor that published an advisory referencing this CVE — pulled from our cve_vendor_advisories aggregation. Click any row for the vendor's original advisory page.

Data Freshness Timeline

(refreshed 9× in last 7d / 21× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-07-23 01:22 UTCEG score recompute
  2. 2026-07-22 22:02 UTCEG score recompute
  3. 2026-07-22 14:04 UTCEPSS rescore
  4. 2026-07-21 15:21 UTCEPSS rescore
  5. 2026-07-21 15:21 UTCEPSS rescore
  6. 2026-07-20 17:03 UTCEPSS rescore
  7. 2026-07-19 14:27 UTCEPSS rescore
  8. 2026-07-19 02:26 UTCEPSS rescore
  9. 2026-07-19 02:26 UTCEPSS rescore
  10. 2026-07-15 16:54 UTCEPSS rescore
  11. 2026-07-15 16:54 UTCEPSS rescore
  12. 2026-07-12 05:43 UTCEPSS rescore
  13. 2026-07-12 05:43 UTCEPSS rescore
  14. 2026-07-11 08:23 UTCEPSS rescore
  15. 2026-07-08 15:10 UTCEPSS rescore
  16. 2026-07-04 06:28 UTCEPSS rescore
  17. 2026-07-01 15:02 UTCEPSS rescore
  18. 2026-06-27 03:05 UTCEPSS rescore
  19. 2026-06-27 03:05 UTCEPSS rescore
  20. 2026-06-25 13:47 UTCEPSS rescore
  21. 2026-06-25 13:47 UTCEPSS rescore
  22. 2026-06-23 21:30 UTCEPSS rescore
  23. 2026-06-17 17:50 UTCEPSS rescore
  24. 2026-06-17 17:50 UTCEPSS rescore
  25. 2026-06-16 17:50 UTCEPSS rescore
Show 46 more
  1. 2026-06-16 17:50 UTCEPSS rescore
  2. 2026-06-15 17:45 UTCEPSS rescore
  3. 2026-06-13 22:57 UTCEPSS rescore
  4. 2026-06-13 22:57 UTCEPSS rescore
  5. 2026-06-12 23:09 UTCEPSS rescore
  6. 2026-06-12 23:09 UTCEPSS rescore
  7. 2026-06-11 13:57 UTCEPSS rescore
  8. 2026-06-10 22:15 UTCEPSS rescore
  9. 2026-06-10 13:18 UTCEPSS rescore
  10. 2026-06-07 15:22 UTCEPSS rescore
  11. 2026-06-07 15:22 UTCEPSS rescore
  12. 2026-06-06 13:45 UTCEPSS rescore
  13. 2026-06-05 06:08 UTCEPSS rescore
  14. 2026-06-05 06:08 UTCEPSS rescore
  15. 2026-06-01 13:49 UTCEPSS rescore
  16. 2026-06-01 13:49 UTCEPSS rescore
  17. 2026-05-31 22:28 UTCEPSS rescore
  18. 2026-05-31 22:28 UTCEPSS rescore
  19. 2026-05-31 00:14 UTCEPSS rescore
  20. 2026-05-29 13:41 UTCEPSS rescore
  21. 2026-05-26 13:42 UTCEPSS rescore
  22. 2026-05-22 21:15 UTCEPSS rescore
  23. 2026-05-22 21:15 UTCEPSS rescore
  24. 2026-05-21 22:40 UTCEPSS rescore
  25. 2026-05-20 22:37 UTCEPSS rescore
  26. 2026-05-20 22:37 UTCEPSS rescore
  27. 2026-05-20 22:37 UTCEPSS rescore
  28. 2026-05-20 07:35 UTCVendor advisory
  29. 2026-05-20 07:35 UTCGHSA enrichment
  30. 2026-05-20 03:14 UTCVendor advisory
  31. 2026-05-20 03:14 UTCGHSA enrichment
  32. 2026-05-19 22:53 UTCVendor advisory
  33. 2026-05-19 22:53 UTCGHSA enrichment
  34. 2026-05-19 18:32 UTCVendor advisory
  35. 2026-05-19 18:32 UTCGHSA enrichment
  36. 2026-05-19 14:12 UTCVendor advisory
  37. 2026-05-19 14:12 UTCGHSA enrichment
  38. 2026-05-19 09:52 UTCVendor advisory
  39. 2026-05-19 09:51 UTCGHSA enrichment
  40. 2026-05-19 05:31 UTCVendor advisory
  41. 2026-05-19 05:31 UTCGHSA enrichment
  42. 2026-05-19 01:10 UTCEG score recompute
  43. 2026-05-19 01:10 UTCVendor advisory
  44. 2026-05-19 01:09 UTCGHSA enrichment
  45. 2026-05-18 21:30 UTCEPSS rescore
  46. 2026-05-18 21:30 UTCEPSS rescore

Publicly available exploits

(1 reference)

Working exploit code is in the public domain (1 Metasploit module). Defenders should treat patch urgency accordingly — public PoCs typically lead to mass-exploitation within 24-72 hours.

  • Metasploitauxiliary/server/netbios_spoof_nat✓ verified
    First seen Jun 14, 2016

    NetBIOS Response "BadTunnel" Brute Force Spoof (NAT Tunnel)

    Open source ↗

Related CVEs(same vendor)

Frequently asked(5)

What is CVE-2016-3236?
CVE-2016-3236 is a critical vulnerability published on June 16, 2016. The Web Proxy Auto Discovery (WPAD) protocol implementation in Microsoft Windows Vista SP2, Windows Server 2008 SP2 and R2 SP1, Windows 7 SP1, Windows 8.1, Windows Server 2012 Gold and R2, Windows RT 8.1, and Windows 10 Gold and 1511 mishandles proxy discovery, which allows remote attackers to…
When was CVE-2016-3236 disclosed?
CVE-2016-3236 was first published in the National Vulnerability Database on June 16, 2016, with the most recent update on May 6, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2016-3236 actively exploited?
CVE-2016-3236 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 99.5% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2016-3236?
CVE-2016-3236 has a CVSS v3 base score of 9.8 (NVD).
How do I remediate CVE-2016-3236?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2016-3236, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2016-3236

Explore →

Is Your Infrastructure Affected by CVE-2016-3236?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs