CVE-2006-0021

HIGHCVSS v2 · 7.87.8—
EchelonGraph scoreLOW confidence

This CVE was only ever scored under CVSS v2.0. NVD CVSS v2.0 base 7.8 — v2 rates that HIGH (v2 bands: LOW 0.0–3.9 / MEDIUM 4.0–6.9 / HIGH 7.0–10.0; v2 has no CRITICAL band). Vector AV:N/AC:L/Au:N/C:N/I:N/A:C. CVSS v2 is an older, coarser metric than v3.1/v4.0 (no Scope, no User Interaction, no Attack Requirements), so it is not directly comparable to a v3 or v4 score. NVD has never re-scored this record under v3. EPSS predicts 62.9% exploitation probability in the next 30 days, which is reflected in EG Risk but does not lift the v2 base. Confidence: LOW.

Sources: epss, nvd_v2
Weaponized
7.8EG
EchelonGraph verdictPatch this weekExploitation is likely or a public exploit exists.
  • High exploitation likelihood — EPSS 63%
  • Public exploit code is available (Exploit-DB (verified), epss top5pct, epss high, public exploit)
CISA-KEV: Not listedEPSS PROB: 63%CVSS v2: 7.8Exploit: Exploit-DB (verified) · epss top5pct · epss high · public exploitExposed: 0

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

Microsoft Windows XP SP1 and SP2, and Server 2003 up to SP1, allows remote attackers to cause a denial of service (hang) via an IGMP packet with an invalid IP option, aka the "IGMP v3 DoS Vulnerability."

CVSS v2.0 (legacy)
7.8HIGHNVD never assigned a CVSS v3 rating to this CVE
EG Score
7.8(low)
EG Risk
66(Track)
EG Risk 66/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
Severity78% × 45%
Exploitation65% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
63%
EPSS %ILE
99%
KEV
Not listed

Published

February 14, 2006

Last Modified

April 16, 2026

References (32)

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

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

Publicly available exploits

(2 references)

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

  • Exploit-DBEDB-1603✓ verified
    First seen Mar 22, 2006

    Microsoft Windows XP/2003 - IGMP v3 Denial of Service (MS06-007) (2)

    Open source ↗
  • Exploit-DBEDB-1599✓ verified
    First seen Mar 21, 2006

    Microsoft Windows XP/2003 - IGMP v3 Denial of Service (MS06-007) (1)

    Open source ↗

Related CVEs(same CWE)

Frequently asked(4)

What is CVE-2006-0021?
CVE-2006-0021 is a high vulnerability published on February 14, 2006. Microsoft Windows XP SP1 and SP2, and Server 2003 up to SP1, allows remote attackers to cause a denial of service (hang) via an IGMP packet with an invalid IP option, aka the "IGMP v3 DoS Vulnerability."
When was CVE-2006-0021 disclosed?
CVE-2006-0021 was first published in the National Vulnerability Database on February 14, 2006, with the most recent update on April 16, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2006-0021 actively exploited?
CVE-2006-0021 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 63% probability of exploitation in the next 30 days, which ranks it in the top 0.9% of all scored CVEs.
How do I remediate CVE-2006-0021?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2006-0021, 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-2006-0021

Explore →

Is Your Infrastructure Affected by CVE-2006-0021?

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

Start Free Scan →Browse All CVEs