CVE-2016-2208

CRITICALNVD 9.19.1—
EchelonGraph scoreMEDIUM confidence

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

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
Weaponized
9.1
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 19%CVSS: 9.1Exploit: NoneExposed: 0

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

The kernel component in Symantec Anti-Virus Engine (AVE) 20151.1 before 20151.1.1.4 allows remote attackers to execute arbitrary code or cause a denial of service (memory access violation and system crash) via a malformed PE header file.

CVSS v3
9.1
EG Score
9.1(medium)
EG Risk
71(Track*)
EG Risk 71/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
Severity91% × 45%
Exploitation65% × 40%
Automatability30% × 15%
Action: Watch closely — could escalate to Attend.
EPSS
97.0%
KEV
Not listed

Published

May 19, 2016

Last Modified

May 6, 2026

Advisory Details (4)

Auto-updated May 9, 2026
🔬 Proof of concept available. No patch confirmed yet.
generic🟡 PoC Available

Symantec/Norton AntiVirus - ASPack Remote Heap/Pool Memory Corruption - Multiple dos Exploit

https://www.exploit-db.com/exploits/39835/
generic
https://bugs.chromium.org/p/project-zero/issues/detail?id=820
generic

Security Updates Detail

http://www.symantec.com/security_response/securityupdates/detail.jsp?fid=security_advisory&pvid=security_advisory&suid=20160516_00
generic
http://www.securityfocus.com/bid/90653

Data Freshness Timeline

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

Publicly available exploits

(1 reference)

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

  • Exploit-DBEDB-39835✓ verified
    First seen May 17, 2016

    Symantec/Norton AntiVirus - ASPack Remote Heap/Pool Memory Corruption

    Open source ↗

Frequently asked(5)

What is CVE-2016-2208?
CVE-2016-2208 is a critical vulnerability published on May 19, 2016. The kernel component in Symantec Anti-Virus Engine (AVE) 20151.1 before 20151.1.1.4 allows remote attackers to execute arbitrary code or cause a denial of service (memory access violation and system crash) via a malformed PE header file.
When was CVE-2016-2208 disclosed?
CVE-2016-2208 was first published in the National Vulnerability Database on May 19, 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-2208 actively exploited?
CVE-2016-2208 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 97.0% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2016-2208?
CVE-2016-2208 has a CVSS v3 base score of 9.1 (NVD).
How do I remediate CVE-2016-2208?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2016-2208, 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-2208

Explore →

Is Your Infrastructure Affected by CVE-2016-2208?

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

Start Free Scan →Browse All CVEs