CVE-2026-27475

HIGHPre-NVD 8.18.1—
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.

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.

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 computed
Severity81% × 45%
Exploitation1% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
1%
EPSS %ILE
55%
KEV
Not listed

Published

February 19, 2026

Last Modified

June 17, 2026

Advisory Details (3)

Auto-updated Jul 27, 2026
No patch confirmed yet.
generic

SPIP < 4.4.9 Insecure Deserialization | Advisories | VulnCheck

https://www.vulncheck.com/advisories/spip-insecure-deserialization
generic

Overload

https://git.spip.net/spip/spip
generic

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.html

Affected Packages

(3 across 3 ecosystems)
Debian:11(1)
PackageVulnerable rangeFixed inDependents
spip3.2.11-3 ... 4.4.9+dfsg-1 (70 versions)——
Debian:13(1)
PackageVulnerable rangeFixed inDependents
spip4.4.10+dfsg-1 ... 4.4.9+dfsg-1 (9 versions)4.4.11+dfsg-0+deb13u1—
Debian:14(1)
PackageVulnerable rangeFixed inDependents
spip4.4.3+dfsg-1 ... 4.4.8+dfsg-1 (6 versions)4.4.9+dfsg-1—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 8× in last 7d / 28× 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.

  1. 2026-09-20 20:15 UTCEPSS rescore
  2. 2026-09-20 20:15 UTCEPSS rescore
  3. 2026-09-19 15:03 UTCOSV refresh
  4. 2026-09-18 19:28 UTCEPSS rescore
  5. 2026-09-18 19:27 UTCEPSS rescore
  6. 2026-09-17 19:30 UTCEPSS rescore
  7. 2026-09-16 14:08 UTCEPSS rescore
  8. 2026-09-16 05:15 UTCEPSS rescore
  9. 2026-09-13 16:47 UTCEPSS rescore
  10. 2026-09-12 15:01 UTCEPSS rescore
  11. 2026-09-11 14:52 UTCEPSS rescore
  12. 2026-09-10 09:34 UTCEPSS rescore
  13. 2026-09-08 22:00 UTCEPSS rescore
  14. 2026-09-07 16:01 UTCEPSS rescore
  15. 2026-09-06 13:47 UTCEPSS rescore
  16. 2026-09-06 13:47 UTCEPSS rescore
  17. 2026-09-04 05:06 UTCEPSS rescore
  18. 2026-09-02 14:11 UTCEPSS rescore
  19. 2026-09-01 13:53 UTCEPSS rescore
  20. 2026-09-01 04:39 UTCEPSS rescore
  21. 2026-08-31 18:34 UTCOSV refresh
  22. 2026-08-30 19:17 UTCEPSS rescore
  23. 2026-08-30 01:22 UTCEPSS rescore
  24. 2026-08-28 21:41 UTCEPSS rescore
  25. 2026-08-27 14:25 UTCEPSS rescore
Show 49 more
  1. 2026-08-26 14:46 UTCEPSS rescore
  2. 2026-08-25 13:48 UTCEPSS rescore
  3. 2026-08-23 00:19 UTCEPSS rescore
  4. 2026-08-21 23:49 UTCEPSS rescore
  5. 2026-08-20 22:55 UTCEPSS rescore
  6. 2026-08-19 17:03 UTCEPSS rescore
  7. 2026-08-18 13:48 UTCEPSS rescore
  8. 2026-08-17 13:47 UTCEPSS rescore
  9. 2026-08-16 14:56 UTCEPSS rescore
  10. 2026-08-16 02:14 UTCEPSS rescore
  11. 2026-08-15 01:30 UTCEPSS rescore
  12. 2026-08-14 22:28 UTCGHSA enrichment
  13. 2026-08-14 09:33 UTCEG score recompute
  14. 2026-08-14 09:33 UTCGHSA enrichment
  15. 2026-08-13 22:00 UTCEPSS rescore
  16. 2026-08-13 01:44 UTCEG score recompute
  17. 2026-08-13 01:44 UTCGHSA enrichment
  18. 2026-08-12 13:50 UTCEPSS rescore
  19. 2026-08-12 02:01 UTCEG score recompute
  20. 2026-08-12 02:01 UTCGHSA enrichment
  21. 2026-08-11 13:42 UTCEPSS rescore
  22. 2026-08-11 07:09 UTCEG score recompute
  23. 2026-08-11 07:09 UTCGHSA enrichment
  24. 2026-08-11 00:00 UTCEPSS rescore
  25. 2026-08-09 22:01 UTCEG score recompute
  26. 2026-08-09 22:01 UTCGHSA enrichment
  27. 2026-08-09 13:46 UTCEPSS rescore
  28. 2026-08-09 09:09 UTCEG score recompute
  29. 2026-08-09 09:09 UTCGHSA enrichment
  30. 2026-08-08 16:37 UTCEPSS rescore
  31. 2026-08-08 10:16 UTCGHSA enrichment
  32. 2026-08-07 21:24 UTCEG score recompute
  33. 2026-08-07 21:24 UTCGHSA enrichment
  34. 2026-08-06 13:46 UTCEPSS rescore
  35. 2026-08-06 03:25 UTCEG score recompute
  36. 2026-08-06 03:25 UTCGHSA enrichment
  37. 2026-08-05 19:17 UTCEPSS rescore
  38. 2026-08-04 15:10 UTCEPSS rescore
  39. 2026-08-03 10:36 UTCEPSS rescore
  40. 2026-08-02 20:06 UTCEG score recompute
  41. 2026-08-02 20:06 UTCGHSA enrichment
  42. 2026-08-02 02:26 UTCEPSS rescore
  43. 2026-08-01 04:16 UTCEPSS rescore
  44. 2026-07-30 16:27 UTCEPSS rescore
  45. 2026-07-30 01:30 UTCEPSS rescore
  46. 2026-07-28 15:36 UTCEPSS rescore
  47. 2026-07-27 14:46 UTCEG score recompute
  48. 2026-07-27 14:45 UTCGHSA enrichment
  49. 2026-07-27 13:55 UTCOSV refresh

Related CVEs(same CWE)

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 45.3% 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

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-27475

Explore →

Is Your Infrastructure Affected by CVE-2026-27475?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs