Vulnerability Database · Debian · Package report

spip: vulnerability history, versions and safety

spip is a package in the Debian ecosystem. Vulert records 124 vulnerabilities for it across 74 releases, from Nov -0001 to Aug 2026. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
124 vulnerabilities recorded U124
i
20 with no fix published

No patched version yet — these are the ones to plan around.

See the unfixed vulnerabilities →
i
10 in the last 12 months

Most recent disclosure 21 Aug 2026.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

Vulert verdict on spip i

Updated on 23 Oct 2026

Careful: 20 of the 124 vulnerabilities Vulert records for this package have no fix yet. Plan around those, or apply the workaround listed for each. The rest have a fixed version to move to.

Long-term outlook: usable, but needs attention 124 vulnerabilities on record across 2026 years, 10 in the last year.

What to do: Plan around the 20 vulnerabilities with no published fix: each lists the affected range and any workaround that reduces exposure. No fix yet: Vulert alerts you the moment one is published. Monitor it with Vulert →

  • Vulnerabilities on record 124 over 2026 years · 10 in the last year i
  • Latest disclosure 21 Aug 2026 i
  • Highest CVSS 9.8 i
  • With no published fix 20 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 spip, 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.

i
Version Vulert vulnerabilities Fix published Details
4.4.21+dfsg-1 U2 No Details →
4.4.20+dfsg-1 U2 No Details →
4.4.19+dfsg-1 U3 No Details →
4.4.18+dfsg-1 U3 No Details →
4.4.16+dfsg-1 U3 No Details →
4.4.15+dfsg-1 U4 No Details →
4.4.14+dfsg-1 U4 No Details →
4.4.13+dfsg-1 U7 No Details →
4.4.11+dfsg-1 U7 No Details →
4.4.10+dfsg-1 U9 No Details →
4.4.9+dfsg-1 U19 No Details →
4.4.8+dfsg-1 U19 No Details →
4.4.7+dfsg-1 U20 No Details →
4.4.6+dfsg-1 U20 No Details →
4.4.5+dfsg-1 U20 No Details →
4.4.4+dfsg-1 U20 No Details →
4.4.3+dfsg-1 U20 No Details →
4.4.2+dfsg-1 U20 No Details →
4.3.8+dfsg-1 U20 No Details →
4.3.6+dfsg-1 U20 No Details →
4.3.5+dfsg-1 U20 No Details →
4.3.4+dfsg-1 U20 No Details →
4.3.3+dfsg-1 U20 No Details →
4.3.2+dfsg-1 U20 No Details →
4.3.1+dfsg-1 U20 No Details →
4.3.0~alpha.2+dfsg-1 U20 No Details →
4.3.0+dfsg-1 U20 No Details →
4.3.0~alpha+dfsg-1 U20 No Details →
4.3.0~beta+dfsg-1 U20 No Details →
4.2.14+dfsg-1 U20 No Details →
4.2.13+dfsg-1 U20 No Details →
4.2.12+dfsg-1 U20 No Details →
4.2.11+dfsg-1 U20 No Details →
4.2.10+dfsg-1 U20 No Details →
4.2.9+dfsg-2 U20 No Details →
4.2.9+dfsg-1 U20 No Details →
4.2.8+dfsg-1 U20 No Details →
4.2.7+dfsg-1 U20 No Details →
4.2.6+dfsg-1 U20 No Details →
4.2.5+dfsg-1 U20 No Details →
4.2.4+dfsg-1 U20 No Details →
4.2.3+dfsg-1 U20 No Details →
4.2.2+dfsg-1 U20 No Details →
4.1.15+dfsg-2 U20 No Details →
4.1.15+dfsg-1 U20 No Details →
4.1.13+dfsg-1 U20 No Details →
4.1.12+dfsg-1 U20 No Details →
4.1.11+dfsg-1 U20 No Details →
4.1.10+dfsg-1 U20 No Details →
4.1.9+dfsg-1 U20 No Details →
4.1.8+dfsg-1 U20 No Details →
4.1.7+dfsg-1 U20 No Details →
4.1.5+dfsg-1 U20 No Details →
4.1.2+dfsg-1 U20 No Details →
4.1.1+dfsg-1 U20 No Details →
4.1.0~alpha+dfsg-1 U20 No Details →
4.1.0~beta+dfsg-1 U20 No Details →
4.1.0~rc+dfsg-1 U20 No Details →
4.0.5-1 U20 No Details →
4.0.4-1 U20 No Details →
4.0.2-1 U20 No Details →
4.0.1-1 U20 No Details →
3.2.12-1 U20 No Details →
3.2.11-3 U42 No Details →
3.2.11-3+deb11u10 U20 No Details →
3.2.11-3+deb11u9 U22 No Details →
3.2.11-3+deb11u8 U22 No Details →
3.2.11-3+deb11u7 U22 No Details →
3.2.11-3+deb11u6 U25 No Details →
3.2.11-3+deb11u5 U28 No Details →
3.2.11-3+deb11u4 U30 No Details →
3.2.11-3+deb11u3 U30 No Details →
3.2.11-3+deb11u2 U34 No Details →
3.2.11-3+deb11u1 U34 No Details →

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

02 Disclosure history

How often vulnerabilities are recorded

  • 0 10
  • 2005 2
  • 2006 14
  • 2007 2
  • 2009 6
  • 2012 4
  • 2013 8
  • 2014 2
  • 2016 10
  • 2017 14
  • 2019 12
  • 2020 2
  • 2022 20
  • 2023 6
  • 2024 2
  • 2025 1
  • 2026 9

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

03 Vulnerabilities

Recorded vulnerabilities for spip

The 5 most severe of 124 vulnerabilities recorded for this package

Search all 124 in the database →

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 spip

Is spip safe to use?

Vulert records 124 vulnerabilities for spip in Debian: 0 critical, 0 high, 0 medium and 0 low, plus 124 not yet rated. 20 of them have no published fix yet, so those are the ones to avoid or mitigate.

How many vulnerabilities does spip have?

124 vulnerabilities are recorded for spip in the Debian ecosystem: 0 critical, 0 high, 0 medium and 0 low, plus 124 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 spip vulnerabilities disclosed?

10 vulnerabilities were recorded for spip in the last 12 months, and the oldest entry in this database dates to 30 Nov -0001. 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 spip 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 spip for upcoming vulnerabilities?

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