CVE-2005-1266: Apache SpamAssassin 3.0.1, 3.0.2, and 3.0.3 allows remote attackers to cause a denial of service (CPU consumpt

This month

MEDIUM 5.0WATCHLISTDOWNGRADE

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

Apache SpamAssassin 3.0.1, 3.0.2, and 3.0.3 allows remote attackers to cause a denial of service (CPU consumption and slowdown) via a message with a long Content-Type header without any boundaries.

Why this priority

EPSS top 5%: very likely to be exploited
On your watchlist

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

Risk facts

CVSS score	5.0 (Medium)
EPSS exploit chance	8.3% (top 5%)
CISA exploited list	No
Published	2005-06-15
Last modified	2026-06-16

Publisher (CNA): Red Hat, Inc. · Vendor: apache

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

Am I affected?

Timeline

2005-06-15 04:00 UTCPublished CVE record published
2026-06-16 22:12 UTCUpdated Record last modified

apache spamassassin DOWNGRADE

Affected: 3.0.1 · 3.0.2 · 3.0.3

Fixed in: no fixed release known

Safe to downgrade to: a release before 3.0.1

1. Check installed version

apt-cache policy spamassassin || rpm -q spamassassin || spamassassin --version

2. No fixed release: DOWNGRADE to a release before 3.0.1 (Debian / Ubuntu)

apt-cache madison spamassassin sudo apt install spamassassin=<VERSION_BEFORE_3.0.1> 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.0.1> 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.

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-2005-1266?

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

Is CVE-2005-1266 being exploited?

CVE-2005-1266 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-2005-1266 affect?

CVE-2005-1266 affects spamassassin. Severity is medium (CVSS 5.0). Apache SpamAssassin 3.0.1, 3.0.2, and 3.0.3 allows remote attackers to cause a denial of service (CPU consumption and slowdown) via a message with a long Content-Type header without any boundaries.

How urgent is CVE-2005-1266?

Priority 46/100. EPSS top 5%: very likely to be exploited; On your watchlist

Related CVEs

CVE-2020-1946 CRITICAL 9.8 UPGRADE MITIGATE In Apache SpamAssassin before 3.4.5, malicious rule configuration (.cf) files can be configured to run system
CVE-2020-1931 HIGH 8.1 UPGRADE A command execution issue was found in Apache SpamAssassin prior to 3.4.3
CVE-2020-1930 HIGH 8.1 UPGRADE A command execution issue was found in Apache SpamAssassin prior to 3.4.3
CVE-2019-12420 HIGH 7.5 UPGRADE MITIGATE In Apache SpamAssassin before 3.4.3, a message can be crafted in a way to use excessive resources
CVE-2018-11805 MEDIUM 6.7 UPGRADE MITIGATE In Apache SpamAssassin before 3.4.3, nefarious CF files can be configured to run system commands without any o

References

← Back to latest CVEs