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


- **Severity:** Critical 9.2 (`CVSS:4.0/AV:N/AC:H/AT:P/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Fix available:** Yes
- **Published:** 12 May 2026
- **Updated:** 14 Jul 2026
- **Also known as:** DEBIAN-CVE-2026-8430, GHSA-qjjx-7vj9-gr7c, UBUNTU-CVE-2026-8430

## What is CVE-2026-8430?

CVE-2026-8430 is a critical vulnerability in SPIP, published on 12 May 2026. 

### Official 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.

Weakness: CWE-94 (Improper Control of Generation of Code)

## Which versions are affected by CVE-2026-8430?


## How do I fix CVE-2026-8430?

Upgrade to a fixed version.

## Is CVE-2026-8430 being exploited?

There is no known exploitation of CVE-2026-8430 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-8430 and fix it if it is affected.

What it is: CVE-2026-8430 is a critical vulnerability in SPIP, published on 12 May 2026. 
Exploitation: There is no known exploitation of CVE-2026-8430 in the wild and no public exploit code.

Affected product: SPIP. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-8430/ (Markdown: https://insights.sbomify.com/CVE-2026-8430/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-8430
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-8430
- OSV: https://osv.dev/vulnerability/CVE-2026-8430

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-8430/
Summaries are generated and may contain mistakes; the official description above is the record.