CTIPilot
AI-generated · no human review · verify critical claims against the linked source. how it works →

SPIP 2026 RCE wave

trend · trend:spip-2026-rce-wave

Successive 2026 SPIP CMS security releases tracked by CERT-FR: multiple RCEs in versions before 4.4.14 (CERTFR-2026-AVI-0564) followed by a security-policy bypass fixed in 4.4.15 (CERTFR-2026-AVI-0635).

Aliases: CERTFR-2026-AVI-0564, CERTFR-2026-AVI-0635

Coverage
2
first 2026-05-13 → last 2026-10-21
Latest activity
2026-05-23
ANSSI / CERT-FR publishes CERTFR-2026-AVI-0635 on SPIP < 4.4.15, security-policy bypass in the dominant…
Peak priority
notable
2 notable
Targets
public-sector
sectors: public-sector, education · regions: europe, switzerland
Sources cited
4
2 hosts

Defender insights

What each entry about SPIP 2026 RCE wave tells a defender to do, newest first.

2026-05-13NOTABLESPIP 4.4.14 fixes two RCE flaws, one reachable from the public area on certain nginx setups (CERTFR-2026-AVI-0564)

Exposure

Story timeline

  1. 2026-05-23ANSSI / CERT-FR publishes CERTFR-2026-AVI-0635 on SPIP < 4.4.15, security-policy bypass in the dominant French public-administration CMS
    active-threats
  2. 2026-05-13CERTFR-2026-AVI-0564: SPIP before 4.4.14, two remote code execution flaws in the private area and, on certain nginx configurations, the public area
    trending-vulnerabilitiesSPIP 4.4.14 fixes two RCE flaws, one reachable from the public area on certain nginx setups (CERTFR-2026-AVI-0564)

Hunting pivots

Affected products
ATT&CK techniques (1 across 1 tactic)

1 technique observed across 1 entry about this entity, derived from entry metadata and body evidence, never asserted without a published entry behind it · pinned to MITRE ATT&CK v20.1 · compare on the matrix · Navigator layer (JSON)

  • Initial AccessExploit Public-Facing Application

Initial Access TA0001

T1190Exploit Public-Facing Application×1

Adversaries may attempt to exploit a weakness in an Internet-facing host or system to initially access a network. The weakness in the system can be a software bug, a temporary glitch, or a misconfiguration.

Evidence: 2026-05-13/certfr-2026-avi-0564-spip-4-4-14-multiple-rces-public-and-pr · ATT&CK page ↗

Entries about SPIP 2026 RCE wave (2)

2026-05-23 · view entry permalink →

NOTABLE

ANSSI / CERT-FR publishes CERTFR-2026-AVI-0635 on SPIP < 4.4.15, security-policy bypass in the dominant French public-administration CMS

ANSSI / CERT-FR issued CERTFR-2026-AVI-0635 on 2026-05-22 covering a security-policy bypass vulnerability in SPIP (Système de Publication pour l'Internet) versions prior to 4.4.15; SPIP 4.4.15 was released the same day (SPIP blog, 2026-05-22). The advisory quotes the issue in CERT-FR's standard French: "Une vulnérabilité a été découverte dans SPIP. Elle permet à un attaquant de provoquer un contournement de la politique de sécurité. SPIP versions antérieures à 4.4.15 sont affectées." (in English: a vulnerability allows an attacker to bypass the security policy; versions prior to 4.4.15 are affected). No CVE identifier or CVSS score is attached to the CERT-FR notice yet; no exploitation in the wild has been reported.

The SPIP project blog characterises the underlying issue specifically as an open-redirect vulnerability in the cookie action; the "policy bypass" framing in the CERT-FR advisory is the standard generic catch-all used by ANSSI, not a separate finding. SPIP is the predominant CMS across French public administration (préfectures, ministries, research institutions) and the Francophone government sphere in Belgium, Switzerland (Romandie cantonal and communal sites) and Canada. Open-redirect issues in authenticated cookie paths are typically chained into account-impersonation or token-laundering against OAuth/OpenID-Connect identity providers, so the EU/CH public-sector risk is concrete even without a CVE in the loop yet. SPIP 4.4.15 is the immediate follow-on to the earlier-May 4.4.14 security release. Detection vantage: review SPIP access logs for unexpected redirect-parameter values on the cookie-action endpoint and any outbound 30x responses to attacker-controlled hosts; defenders should also note that Swiss cantonal and communal administrations using SPIP for public portals fall under the 24-hour NCSC.ch reporting obligation for critical-infrastructure operators if a SPIP intrusion is later confirmed.

Why it matters to us: every Romandie cantonal/communal SOC with a SPIP-built portal needs to patch in this cycle; the absence of a CVE makes it easy to overlook on automated patch-track reports.

threat23 May 05:00Zmulti-sourceOpen finding →

2026-05-13 · view entry permalink →

NOTABLEupdatedNATOA2

CERTFR-2026-AVI-0564: SPIP before 4.4.14, two remote code execution flaws in the private area and, on certain nginx configurations, the public area

SPIP's maintenance team released SPIP 4.4.14 on 2026-05-12 to fix two security flaws, a remote code execution (RCE) flaw in the private area and an RCE flaw in the public area that is limited to the use of certain nginx configurations, reported by Louka Jacques-Chevallier (Laluka), Baptiste Rolando, Arthur Deloffre (Vozec), jvoisin and Cezame (SPIP, 2026-05-12). The bulletin states that "these flaws are not covered by the security screen" (translated from French), so SPIP's built-in screen gives no interim protection; it gives no technical detail beyond the nginx condition, and the release's change list also includes better sanitisation of HTTP_HOST and a fix to REMOTE_USER handling under nginx (SPIP, 2026-05-12). CERT-FR's CERTFR-2026-AVI-0564 lists SPIP versions before 4.4.14 as affected with remote arbitrary code execution as the risk, refers to the SPIP bulletin for the fix and names no CVE identifiers (CERT-FR, 2026-05-12).

an RCE-type flaw in the public area, limited to the use of certain nginx configurations (translated from French)

These flaws are not covered by the security screen. (translated from French)

SPIP security bulletin 2026-05-12

SPIP versions before 4.4.14 (translated from French)

CERT-FR CERTFR-2026-AVI-0564 2026-05-12
Correctionrun 2026-10-21T1148Z-auditaffected_productsbodyclassificationentitiesevidenceheadlinesourcessourcing_notesummarytechniquestitle

SPIP's bulletin describes the public-area flaw only as limited to certain nginx configurations and names no exploit pattern, so there are no template or gadget signatures in access logs and no specific reverse-proxy location rule to audit for (SPIP, 2026-05-12). Its statement that "these flaws are not covered by the security screen" (translated from French) means the screen does not block them and the upgrade to 4.4.14 is the only fix; the bulletin counts two flaws (SPIP, 2026-05-12), and neither it nor CERT-FR gives figures on SPIP's use by ministries, universities or Swiss cantons (CERT-FR, 2026-05-12).

vulnerability13 May 05:00Zmulti-sourceOpen finding →

Co-occurring entities

Derived: referenced by the same focused operational entries (weekly summaries and report roundups don't count); ×N counts the shared entries.

Where this entity is cited

  • Vulns1
  • Threats1

Source distribution

  • blog.spip.net2 (50%)
  • cert.ssi.gouv.fr2 (50%)