Is CVE-2026-77647 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2026-77647 being exploited in the wild.

How severe is CVE-2026-77647?

Critical severity, with a CVSS score of 9.8, published 20 August 2026.

Is there a fix for CVE-2026-77647?

No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.

How is CVE-2026-77647 attacked?

It is attacked over the network.

Am I affected by CVE-2026-77647?

Check whether you run Spip at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-77647: SPIP remote code execution via PHP block parsing

CVE-2026-77647 · Severity: critical · CVSS 9.8 · Published 2026-08-20

SPIP is a website engine and content management platform used to publish and manage website content. An unauthenticated attacker can exploit a flaw in how SPIP identifies and processes PHP code blocks to execute arbitrary code on the server. This vulnerability affects all versions and was actively exploited in the wild, putting any SPIP-based website at risk of complete compromise.

Technologies: Spip. Vendors: Spip.

Quick answers

Is CVE-2026-77647 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-77647 being exploited in the wild.
How severe is CVE-2026-77647?: Critical severity, with a CVSS score of 9.8, published 20 August 2026.
Which products and versions are affected?: Spip before 4.4.20.
Is there a fix for CVE-2026-77647?: No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
How is CVE-2026-77647 attacked?: It is attacked over the network.
Am I affected by CVE-2026-77647?: Check whether you run Spip at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

Technical details

The vulnerability is a pre-authentication remote code execution (RCE) flaw resulting from incorrect identification of PHP blocks combined with improper handling of var_export in cases where a less-than character (<) is present. The flaw is universal and affects all SPIP versions without any special preconditions required. An unauthenticated, network-adjacent attacker can trigger this vulnerability to achieve arbitrary code execution on the affected server. The vulnerability is not blocked by SPIP's security screen and was patched in version 4.4.20, released on August 17, 2026, following reports of active exploitation in the wild.

Affected products

SPIP SPIP before 4.4.20

Timeline

2026-08-17: disclosed: SPIP 4.4.20 released with security patch
2026-08-20: exploited: Active exploitation observed in the wild by August 20, 2026
2026-08-18: advisory: Debian Security Advisory DSA-6448-1 published

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.