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.
CVE-2026-27475
HIGHPre-NVD 8.18.1—Trending — 4 sources updated this week
EchelonGraph scoreMEDIUM confidence
Score 8.1 from GitHub Security Advisory (severity: CRITICAL) published 2026-02-19. a secondary CVSS source baseline 8.1; sources differ by 0.0.
Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
8.1EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
- High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 1%CVSS: 8.1Exploit: None knownExposed: 0
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 8.1
- EG Score
- 8.1(medium)
- EG Risk
- 41(Track)EG Risk 41/100SSVC: Track
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computedSeverity81% × 45%Exploitation1% × 40%Automatability30% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- 1%
- EPSS %ILE
- 52%
- KEV
- Not listed
Published
February 19, 2026
Last Modified
June 17, 2026
Advisory Details (3)
Auto-updated Jul 27, 2026No patch confirmed yet.
generic
SPIP < 4.4.9 Insecure Deserialization | Advisories | VulnCheck
https://www.vulncheck.com/advisories/spip-insecure-deserializationgeneric
Mise à jour de sécurité : sortie de SPIP 4.4.9 - SPIP Blog
https://blog.spip.net/Mise-a-jour-de-securite-sortie-de-SPIP-4-4-9.htmlWeakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 4× in last 7d / 4× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
- 2026-07-28 15:36 UTCEPSS rescore
- 2026-07-27 14:46 UTCEG score recompute
- 2026-07-27 14:45 UTCGHSA enrichment
- 2026-07-27 13:55 UTCOSV refresh
Related CVEs(same CWE)
Same CWE
10 shownCWE-502
- CVE-2017-10992EG 9.8EPSS p95CRITICAL
- CVE-2013-4521EG 9.8EPSS p90CRITICAL
- CVE-2014-1860EG 9.8CRITICAL
- CVE-2016-1000027EG 9.8EPSS p98CRITICAL
- CVE-2014-3699EG 9.8CRITICAL
- CVE-2017-10934EG 9.8CRITICAL
- CVE-2016-9498EG 9.8EPSS p97CRITICAL
- CVE-2016-9483EG 9.8CRITICAL
- CVE-2015-2020EG 9.8CRITICAL
- CVE-2017-15692EG 9.8EPSS p91CRITICAL
Frequently asked(5)
What is CVE-2026-27475?
CVE-2026-27475 is a high vulnerability published on February 19, 2026. 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…
When was CVE-2026-27475 disclosed?
CVE-2026-27475 was first published in the National Vulnerability Database on February 19, 2026, with the most recent update on June 17, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-27475 actively exploited?
CVE-2026-27475 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 1% probability of exploitation in the next 30 days, which ranks it in the top 47.9% of all scored CVEs.
What is the CVSS score of CVE-2026-27475?
CVE-2026-27475 has a CVSS v3 base score of 8.1 (NVD).
How do I remediate CVE-2026-27475?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-27475, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-27475
Is Your Infrastructure Affected by CVE-2026-27475?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.