Free and open · new CVEs checked every 20 minutesStatusRSSOpen dataContact

CVE-2006-2447: SpamAssassin before 3.1.3, when running with vpopmail and the paranoid (-P) switch, allows remote attackers to

53
This week
MEDIUM 5.1WATCHLISTDOWNGRADE

CVE-2006-2447 is a medium-severity flaw (CVSS 5.1) affecting spamassassin. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

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.

Why this priority

  • EPSS top 1%: very likely to be exploited
  • Public exploit reference
  • On your watchlist

No fix is published yet: follow the downgrade or mitigation steps.

Risk facts

CVSS score5.1 (Medium)
EPSS exploit chance75.8% (top 1%)
CISA exploited listNo
Published2006-06-06
Last modified2026-06-16
Publisher (CNA): Red Hat, Inc. · Vendor: apache

Share: LinkedIn · X · Reddit

Last updated 2026-06-16 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

apache spamassassin DOWNGRADE
Affected: 3.1.0 · 3.1.1 · 3.1.2
Fixed in: no fixed release known
Safe to downgrade to: a release before 3.1.0
1. Check installed version
apt-cache policy spamassassin || rpm -q spamassassin || spamassassin --version
2. No fixed release: DOWNGRADE to a release before 3.1.0 (Debian / Ubuntu)
apt-cache madison spamassassin sudo apt install spamassassin=<VERSION_BEFORE_3.1.0> sudo apt-mark hold spamassassin
2. No fixed release: DOWNGRADE (RHEL / Amazon Linux / Fedora)
dnf --showduplicates list spamassassin sudo dnf downgrade spamassassin-<VERSION_BEFORE_3.1.0> sudo dnf versionlock add spamassassin
Downgrade risk
Downgrading can break dependent software and may reopen older bugs. Read the distro advisory first and test on a non-production host.
After downgrade
Restart the service, and keep the package held until a fixed release ships.

Public exploits and detection

Public code exists for this CVE. Treat unpatched systems as at risk, and only run PoCs in a lab.

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2006-2447?

spamassassin: downgrade or apply the listed mitigation. Exact commands for each OS are on this page.

Is CVE-2006-2447 being exploited?

CVE-2006-2447 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2006-2447 affect?

CVE-2006-2447 affects spamassassin. Severity is medium (CVSS 5.1). 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.

How urgent is CVE-2006-2447?

Priority 53/100. EPSS top 1%: very likely to be exploited; Public exploit reference; On your watchlist

Related CVEs

References

← Back to latest CVEs

Get the weekly exploited-CVE digest by emailThe CVEs being attacked this week and how to fix them. No spam, unsubscribe any time.