CVE-2026-27475 json
SPIP < 4.4.9 Insecure Deserialization
published 2026-02-19 8 mo ago modified 2026-06-17 4 mo ago also EUVD-2026-8322
- cvss
- 8.1
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.9%
- EPSS 0.9% chance of exploitation in 30 days, percentile 60%
- public exploits
- 0
- none known
Summary
SPIP before 4.4.9 allows Insecure Deserialization in the public area through the table_valeur filter and the DATA iterator, which accept serialized data. An attacker who can place malicious serialized content (a pre-condition requiring prior access or another vulnerability) can trigger arbitrary object instantiation and potentially achieve code execution. The use of serialized data in these components has been deprecated and will be removed in SPIP 5. This vulnerability is not mitigated by the SPIP security screen.
Patch / fix
- SPIP SPIP 4.4.9
- spip Debian 13 4.4.11+dfsg-0+deb13u1
- spip Debian 14 4.4.9+dfsg-1
debian advisories DEBIAN-CVE-2026-27475
CISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- total
- Assessed
- 8 mo ago
Exploit prediction
0.91% chance of exploitation in the next 30 days, higher than 60% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 4.0 | 9.2 | CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N |
| CNA | 3.1 | 8.1 | CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H |
| CNA | 4.0 | 9.2 | CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X |
Affected products
- SPIP SPIP
Classification
- Weakness
-
- CWE-502 Deserialization of Untrusted Data
References
-
blog.spip.net
/Mise-a-jour-de-securite-sortie-de-SPIP-4-4-9.html
vendor-advisory, patch, release-notes
-
git.spip.net
/spip/spip
product
-
vulncheck.com
/advisories/spip-insecure-deserialization
third-party-advisory
Sources
- CVE List CVE-2026-27475
- NVD CVE-2026-27475
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.