# CVE-2026-77806: Code injection in SPIP

> Unauthenticated attackers can execute arbitrary code via a malicious HTTP header, requiring immediate upgrades to SPIP.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 21 Aug 2026
- **Updated:** 21 Aug 2026
- **Also known as:** DEBIAN-CVE-2026-77806, GHSA-vgr8-rqwx-wqrp, UBUNTU-CVE-2026-77806

## What is CVE-2026-77806?

CVE-2026-77806 is a critical code injection vulnerability in SPIP, published on 21 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

SPIP before 4.4.21 allows unauthenticated remote attackers to execute arbitrary code, as exploited in the wild in August 2026. This is related to code injection via an X-Spip-Filtre HTTP request header that is mishandled by analyse_resultat_skel.

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

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


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

Upgrade to a fixed version.

## Is CVE-2026-77806 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-77806 exists.

Public exploit code:

- CVE-2026-77806漏洞检测代码 (github_poc): https://github.com/CuteeCat/CVE-2026-77806
- SPIP < 4.4.22 - Unauthenticated RCE (nuclei): http/cves/2026/CVE-2026-77806.yaml

## Fix prompt for AI coding agents

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

What it is: CVE-2026-77806 is a critical code injection vulnerability in SPIP, published on 21 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-77806 exists.

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-77806/ (Markdown: https://insights.sbomify.com/CVE-2026-77806/index.md)
```

## Sources

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

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