CVE-2007-2873: SpamAssassin 3.1.x, 3.2.0, and 3.2.1 before 20070611, when running as root in unusual configurations using vpo

Routine

LOW 1.9DOWNGRADE

CVE-2007-2873 is a low-severity flaw (CVSS 1.9) affecting spamassassin. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

SpamAssassin 3.1.x, 3.2.0, and 3.2.1 before 20070611, when running as root in unusual configurations using vpopmail or virtual users, allows local users to cause a denial of service (corrupt arbitrary files) via a symlink attack on a file that is used by spamd.

Why this priority

No elevated risk signals yet

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

Risk facts

CVSS score	1.9 (Low)
EPSS exploit chance	0.3% (top 72%)
CISA exploited list	No
Published	2007-06-11
Last modified	2026-06-16

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

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

Am I affected?

Timeline

2007-06-11 23:30 UTCPublished CVE record published
2026-06-16 22:40 UTCUpdated Record last modified

spamassassin spamassassin DOWNGRADE

Affected: 3.1.0 · 3.1.1 · 3.1.2 · 3.1.3 · 3.1.4 · 3.1.5 · 3.1.6 · 3.1.7

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.

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-2007-2873?

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

Is CVE-2007-2873 being exploited?

CVE-2007-2873 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-2007-2873 affect?

CVE-2007-2873 affects spamassassin. Severity is low (CVSS 1.9). SpamAssassin 3.1.x, 3.2.0, and 3.2.1 before 20070611, when running as root in unusual configurations using vpopmail or virtual users, allows local users to cause a denial of service (corrupt arbitrary files) via a symlink attack on a file t

How urgent is CVE-2007-2873?

Priority 14/100. No elevated risk signals yet.

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