CVE-2006-2447

MEDIUMCVSS v2 · 5.15.1—
EchelonGraph scoreLOW confidence

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

A fix is available — apply it.

SpamAssassin before 3.1.3, when running with vpopmail and the paranoid (-P) switch, allows remote attackers to execute arbitrary commands via a crafted message that is not properly handled when invoking spamd with the virtual pop username.

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

Published

June 6, 2006

Last Modified

April 16, 2026

References (38)

Patch Availability(1)

Vendor / EcosystemFixed in / PatchReleasedSource
redhatspamassassin-0:3.0.6-1.el42006-06-06redhat

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(5 across 5 ecosystems)
Debian:11(1)
PackageVulnerable rangeFixed inDependents
spamassassin—3.1.3-1—
Debian:12(1)
PackageVulnerable rangeFixed inDependents
spamassassin—3.1.3-1—
Debian:13(1)
PackageVulnerable rangeFixed inDependents
spamassassin—3.1.3-1—
Debian:14(1)
PackageVulnerable rangeFixed inDependents
spamassassin—3.1.3-1—
Debian:3.1(1)
PackageVulnerable rangeFixed inDependents
spamassassin3.0.3-1, 3.0.3-23.0.3-2sarge1—

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

Publicly available exploits

(3 references)

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

  • Exploit-DBEDB-16920✓ verified
    First seen Apr 30, 2010

    SpamAssassin spamd - Remote Command Execution (Metasploit)

    Open source ↗
  • Exploit-DBEDB-9914✓ verified
    First seen Jun 6, 2006

    SpamAssassin spamd 3.1.3 - Command Injection (Metasploit)

    Open source ↗
  • Metasploitexploit/unix/misc/spamassassin_exec✓ verified
    First seen Jun 6, 2006

    SpamAssassin spamd Remote Command Execution

    Open source ↗

Frequently asked(4)

What is CVE-2006-2447?
CVE-2006-2447 is a medium vulnerability published on June 6, 2006. SpamAssassin before 3.1.3, when running with vpopmail and the paranoid (-P) switch, allows remote attackers to execute arbitrary commands via a crafted message that is not properly handled when invoking spamd with the virtual pop username.
When was CVE-2006-2447 disclosed?
CVE-2006-2447 was first published in the National Vulnerability Database on June 6, 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-2447 actively exploited?
CVE-2006-2447 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 76% probability of exploitation in the next 30 days, which ranks it in the top 0.5% of all scored CVEs.
How do I remediate CVE-2006-2447?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2006-2447, 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

See which npm, PyPI, Go, and Maven packages are affected by CVE-2006-2447

Explore →

Is Your Infrastructure Affected by CVE-2006-2447?

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

Start Free Scan →Browse All CVEs