VulertSecurity VulertSecurity

Vulnerability Database · Alpine · Package report

spamassassin: vulnerability history, versions and safety

spamassassin is a package in the Alpine ecosystem. Vulert records 17 vulnerabilities for it across 34 releases, from Aug 2016 to Mar 2021. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
17 vulnerabilities recorded U17
i
0 with no fix published

Every vulnerability has a patched version to move to.

i
0 in the last 12 months

Nothing new recorded in the last year.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all spamassassin vulnerabilities

Vulert verdict on spamassassin i

Updated on 23 Oct 2026

Every vulnerability Vulert records for this package has a fix, and the newest was recorded 25 Mar 2021. Apply the fixes listed below and you are clear.

Long-term outlook: usable, with an upgrade 17 vulnerabilities on record across 4 years, none in the last year.

What to do: Move the affected dependencies to the fixed versions listed below, then keep the package monitored so the next vulnerability reaches you. Fix it, then keep watch: Vulert alerts you when a new vulnerability affects the version you run. Monitor it with Vulert →

  • Vulnerabilities on record 17 over 4 years · 0 in the last year i
  • Latest disclosure 25 Mar 2021 i
  • Highest CVSS 9.8 i
  • With no published fix 0 i

Concerned about your application's security?

Vulert continues monitoring your dependencies and alerts you when new vulnerabilities are disclosed. No installation and no source-code access required.

01 Versions

Which versions are affected

Every version Vulert holds for spamassassin, newest first, with the vulnerabilities that name it. A version with a count of zero has no recorded vulnerabilities; open a version to see the vulnerabilities it is exposed to.

Newest 34 of 34 versions on record. Severity counts are the vulnerabilities recorded against that exact release.

02 Disclosure history

How often vulnerabilities are recorded

  • 2016 1
  • 2018 6
  • 2019 4
  • 2020 4
  • 2021 2

Counted by the year Vulert recorded each vulnerability — the same date the table below shows as disclosed. 0 of the 17 were recorded in the last 12 months.

03 Vulnerabilities

Recorded vulnerabilities for spamassassin

The 5 most severe of 17 vulnerabilities recorded for this package

Search all 17 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
Critical Remote Code Execution Vulnerability in SpamAssassin 9.8 critical 3.4.2-r0 17 Sep 2018
Remote Code Execution in Apache SpamAssassin PDFInfo Plugin 9.8 critical 3.4.2-r0 17 Sep 2018
Critical Command Injection Vulnerability in SpamAssassin 9.8 critical 3.4.5-r0 25 Mar 2021
Command Injection in Apache SpamAssassin 9.8 critical 3.4.5-r0 25 Mar 2021
Command Execution Vulnerability in Apache SpamAssassin 8.1 high 3.4.4-r0 30 Jan 2020

Vulnerability wrong, a fix missing, or a package we should cover? Report it and we will fix the record. Report Vulnerability Provide Feedback

Updated: 23/Oct/2026 · Vulnerabilities in our DB: 524315

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →

Questions

About spamassassin

Is spamassassin safe to use?

Vulert records 17 vulnerabilities for spamassassin in Alpine: 0 critical, 0 high, 0 medium and 0 low, plus 17 not yet rated. Every one of them has a published fix, so the practical answer is to run a supported release and keep it patched.

How many vulnerabilities does spamassassin have?

17 vulnerabilities are recorded for spamassassin in the Alpine ecosystem: 0 critical, 0 high, 0 medium and 0 low, plus 17 not yet rated. The ledger on this page lists the same counts next to the date of the most recent disclosure.

How often are new spamassassin vulnerabilities disclosed?

0 vulnerabilities were recorded for spamassassin in the last 12 months, and the oldest entry in this database dates to 02 Aug 2016. Recency matters more than a lifetime total: it shows how actively new issues are being disclosed for the package you are considering.

Which versions of spamassassin are affected?

Each vulnerability on this page lists the affected version range and the fixed version to move to. Open the vulnerability for the version you actually run — fixes are specific to a release line, not to the package as a whole.

How do I monitor spamassassin for upcoming vulnerabilities?

Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the spamassassin version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.