CVE-2006-3439

HIGHCVSS v2 · 10.010.0—
EchelonGraph scoreLOW confidence

This CVE was only ever scored under CVSS v2.0. NVD CVSS v2.0 base 10.0 — 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:C/I:C/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 85.0% 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
10.0EG
EchelonGraph verdictPatch this weekExploitation is likely or a public exploit exists.
  • High exploitation likelihood — EPSS 85%
  • Public exploit code is available (Metasploit, Exploit-DB (verified), epss top5pct, epss high, public exploit)
CISA-KEV: Not listedEPSS PROB: 85%CVSS v2: 10.0Exploit: Metasploit · 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.

Buffer overflow in the Server Service in Microsoft Windows 2000 SP4, XP SP1 and SP2, and Server 2003 SP1 allows remote attackers, including anonymous users, to execute arbitrary code via a crafted RPC message, a different vulnerability than CVE-2006-1314.

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

Published

August 9, 2006

Last Modified

April 16, 2026

References (22)

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-08 16:30 UTCEPSS rescore
  4. 2026-07-26 13:29 UTCEG score recompute▲ 10.00
  5. 2026-07-24 14:11 UTCEPSS rescore
  6. 2026-07-23 00:50 UTCEG score recompute
  7. 2026-07-23 00:30 UTCEG score recompute▼ 9.00
  8. 2026-07-22 23:55 UTCEG score recompute▲ 9.00
  9. 2026-07-22 21:34 UTCEG score recompute▼ 9.00
  10. 2026-07-20 17:02 UTCEPSS rescore
  11. 2026-07-15 16:53 UTCEPSS rescore
  12. 2026-07-15 01:55 UTCEPSS rescore
  13. 2026-07-13 22:25 UTCEPSS rescore
  14. 2026-07-08 15:09 UTCEPSS rescore
  15. 2026-07-02 14:00 UTCEPSS rescore
  16. 2026-06-29 14:02 UTCEPSS rescore
  17. 2026-06-29 14:02 UTCEPSS rescore
  18. 2026-06-25 13:46 UTCEPSS rescore
  19. 2026-06-23 21:29 UTCEPSS rescore
  20. 2026-06-23 21:29 UTCEPSS rescore
  21. 2026-06-17 17:49 UTCEPSS rescore
  22. 2026-06-17 17:49 UTCEPSS rescore
  23. 2026-06-15 17:44 UTCEPSS rescore
  24. 2026-06-13 22:56 UTCEPSS rescore
  25. 2026-06-10 22:14 UTCEPSS rescore
Show 26 more
  1. 2026-06-10 13:17 UTCEPSS rescore
  2. 2026-06-05 22:43 UTCEPSS rescore
  3. 2026-06-05 06:07 UTCEPSS rescore
  4. 2026-06-05 06:07 UTCEPSS rescore
  5. 2026-06-04 13:09 UTCEPSS rescore
  6. 2026-06-04 13:09 UTCEPSS rescore
  7. 2026-06-01 13:49 UTCEPSS rescore
  8. 2026-06-01 13:49 UTCEPSS rescore
  9. 2026-06-01 13:49 UTCEPSS rescore
  10. 2026-05-31 22:28 UTCEPSS rescore
  11. 2026-05-31 07:19 UTCEG score recompute
  12. 2026-05-31 07:19 UTCGHSA enrichment
  13. 2026-05-29 13:40 UTCEPSS rescore
  14. 2026-05-28 13:42 UTCEPSS rescore
  15. 2026-05-28 13:42 UTCEPSS rescore
  16. 2026-05-27 13:37 UTCEPSS rescore
  17. 2026-05-27 13:37 UTCEPSS rescore
  18. 2026-05-26 13:41 UTCEPSS rescore
  19. 2026-05-26 13:41 UTCEPSS rescore
  20. 2026-05-26 07:16 UTCEPSS rescore
  21. 2026-05-26 07:16 UTCEPSS rescore
  22. 2026-05-22 21:15 UTCEPSS rescore
  23. 2026-05-22 21:15 UTCEPSS rescore
  24. 2026-05-20 22:36 UTCEPSS rescore
  25. 2026-05-20 22:36 UTCEPSS rescore
  26. 2026-05-18 21:29 UTCEPSS rescore

Publicly available exploits

(6 references)

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

  • Exploit-DBEDB-16367✓ verified
    First seen Feb 17, 2011

    Microsoft Server Service - NetpwPathCanonicalize Overflow (MS06-040) (Metasploit)

    Open source ↗
  • Exploit-DBEDB-2355✓ verified
    First seen Sep 13, 2006

    Microsoft Windows Server 2003 - NetpIsRemote() Remote Overflow (MS06-040) (Metasploit)

    Open source ↗
  • Exploit-DBEDB-2265✓ verified
    First seen Aug 28, 2006

    Microsoft Windows - NetpIsRemote() Remote Overflow (MS06-040) (2)

    Open source ↗
  • Exploit-DBEDB-2223✓ verified
    First seen Aug 19, 2006

    Microsoft Windows - CanonicalizePathName() Remote (MS06-040)

    Open source ↗
  • Exploit-DBEDB-2162✓ verified
    First seen Aug 10, 2006

    Microsoft Windows - NetpIsRemote() Remote Overflow (MS06-040) (Metasploit)

    Open source ↗
  • Metasploitexploit/windows/smb/ms06_040_netapi✓ verified
    First seen Aug 8, 2006

    MS06-040 Microsoft Server Service NetpwPathCanonicalize Overflow

    Open source ↗

Frequently asked(4)

What is CVE-2006-3439?
CVE-2006-3439 is a high vulnerability published on August 9, 2006. Buffer overflow in the Server Service in Microsoft Windows 2000 SP4, XP SP1 and SP2, and Server 2003 SP1 allows remote attackers, including anonymous users, to execute arbitrary code via a crafted RPC message, a different vulnerability than CVE-2006-1314.
When was CVE-2006-3439 disclosed?
CVE-2006-3439 was first published in the National Vulnerability Database on August 9, 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-3439 actively exploited?
CVE-2006-3439 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 85% probability of exploitation in the next 30 days, which ranks it in the top 0.3% of all scored CVEs.
How do I remediate CVE-2006-3439?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2006-3439, 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-3439

Explore →

Is Your Infrastructure Affected by CVE-2006-3439?

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

Start Free Scan →Browse All CVEs