# CVE-2026-77647: Code injection in SPIP

> Unauthenticated remote attackers can execute arbitrary code in SPIP CMS due to incorrect PHP block identification and var_export mishandling.

- **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:** 20 Aug 2026
- **Updated:** 21 Aug 2026
- **Also known as:** DEBIAN-CVE-2026-77647, GHSA-wj6g-rh9q-6vvm, UBUNTU-CVE-2026-77647

## What is CVE-2026-77647?

CVE-2026-77647 is a critical code injection vulnerability in SPIP, published on 20 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.20 allows unauthenticated remote attackers to execute arbitrary code, as exploited in the wild in August 2026. This is related to incorrect identification of <?php blocks, and var_export's mishandling of certain cases such as presence of a '<' character.

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

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


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

Upgrade to a fixed version.

## Is CVE-2026-77647 being exploited?

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

Public exploit code:

- SPIP X-Spip-Filtre Unauthenticated RCE (metasploit)
- SPIP before 4.4.20 allows unauthenticated remote attackers to execute arbitrary code (github_poc): https://github.com/Nxploited/CVE-2026-77647

## Fix prompt for AI coding agents

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

What it is: CVE-2026-77647 is a critical code injection vulnerability in SPIP, published on 20 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-77647 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-77647/ (Markdown: https://insights.sbomify.com/CVE-2026-77647/index.md)
```

## Sources

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

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