On this page (7 sections)
On November 11, 2026, the Debian security team published DSA-6619-1, a security update for spip, the packaged version of the SPIP website publishing engine. Debian says several vulnerabilities were found that could result in unauthenticated remote code execution.
If you run SPIP, especially from Debian packages on trixie, you should plan to upgrade promptly. The advisory is short, so this article separates what Debian confirmed from what is still unknown and gives you practical ways to check and respond.
What happened
Debian's advisory states that several vulnerabilities were discovered in SPIP, described as a website engine for publishing. Debian says these problems could result in unauthenticated remote code execution. The advisory lists a single CVE identifier, CVE-2026-122032, and recommends upgrading the spip packages.
The advisory does not give a CVSS score, does not describe each individual flaw, and does not say whether anyone is exploiting them. Only one independent publisher covers this story so far, so treat details beyond the Debian notice as unconfirmed.
What we know about the weakness
Remote code execution means an attacker can make the server run commands or code of their choosing. The word unauthenticated is what makes this class of bug serious: no login or account is needed, so any visitor who can reach the site could in principle attempt it. For a publishing engine that is exposed to the internet by design, that widens the pool of potential attackers considerably.
Debian does not say which SPIP component is affected or how the flaws are triggered, and we will not guess. Check the Debian security tracker for spip and the SPIP project's own release notes for more detail as they appear.
Who is affected
- Debian trixie (stable) systems with the spip package installed, which should move to 4.4.30+dfsg-0+deb13u1.
- Sites that run SPIP installed from other sources (upstream archives, other distributions, containers). The Debian advisory only names the trixie fix, so these users should check the SPIP project for its own patched release.
- Agencies and hosts that manage several SPIP sites and may have old copies that are not tracked by a package manager.
The advisory only gives a fixed version for Debian trixie. It does not list affected versions for other Debian releases or for upstream SPIP, so we cannot say whether they are vulnerable.
How to check your exposure
On Debian, this read-only command shows the installed and candidate spip package versions. You are looking for an installed version older than 4.4.30+dfsg-0+deb13u1, which means you still need the update.
apt-cache policy spipThis read-only command shows whether the spip package is installed from the package manager and which version:
dpkg -l spipIf SPIP was not installed from a package, find the version through your admin area or the SPIP files on disk, then compare it with the latest release listed by the SPIP project. Also search your servers and hosting accounts for forgotten SPIP installs, such as old campaign or staging sites.
What to do now
- Back up your SPIP files and database.
- Update the package index and upgrade spip on Debian trixie (commands below).
- Confirm the installed version is 4.4.30+dfsg-0+deb13u1 or newer.
- For non-packaged SPIP installs, get the patched release from the SPIP project and upgrade, including any plugins.
- Review web server access logs for unusual requests to your SPIP site from before the update.
- Check the site for unexpected files, new admin accounts or changed templates.
- If you find signs of compromise, follow a recovery process and rotate credentials.
These commands, run as root on Debian trixie, refresh the package lists and upgrade only the spip package. Afterwards the installed version should match the fixed version above.
apt-get update
apt-get install --only-upgrade spipDebian itself says: "We recommend that you upgrade your spip packages." Afterwards, re-run the version check above to confirm.
Detection and monitoring afterwards
Because the flaw is described as unauthenticated, a patch only helps going forward. If your site was reachable before updating, look for signs that something ran on it. This read-only command counts requests per client address in an Apache access log so you can spot anything unusual. Adjust the path to your own server's log location.
awk '{print $1}' /var/log/apache2/access.log | sort | uniq -c | sort -rn | head -20- Watch for new or modified PHP files in your SPIP directories, and for unexpected processes started by your web server user.
- Keep an eye on outbound connections from the web server that you cannot explain.
- Run an outside-in check with the free malware scanner, and read what outside-in malware detection can and cannot see so you know its limits.
- Monitoring for header and certificate changes can help you notice unexpected changes, though it is not a substitute for patching.
If you suspect a compromise, see our guides on how to check if a website is hacked and what to do when a website is hacked.
Timeline
| Date | Event |
|---|---|
| November 11, 2026 | Debian publishes DSA-6619-1 for spip, fixed in 4.4.30+dfsg-0+deb13u1 on trixie |
Sources
This article is based on the public sources below. Details can change as vendors and researchers publish more; check the original advisories before acting on version numbers.
