Skip to main content
Mallory
CriticalPublic exploitVulnerability

CVE-2026-77806: Unauthenticated Remote Code Execution in SPIP

Published Aug 21, 2026 · Updated 3 days ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 days2 mentions · peak 1 in a dayToday
CVSS9.8Critical · v3.1
EPSS4.5%92nd percentile
CISA KEVNoNot listed
In the wildReported4 exploitation records in Mallory
Vendor
Spip
IdentifiersCVE-2026-77806CWE-94 · Improper Control of Generation of…

CVE-2026-77806 is a code-injection vulnerability in SPIP versions before 4.4.21. The analyse_resultat_skel function mishandles the X-Spip-Filtre HTTP request header, allowing unauthenticated remote attackers to execute arbitrary code. Exploitation requires no user interaction. The vulnerability was exploited in the wild in August 2026 and has a CVSS v3.1 base score of 9.8.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Analyst brief

Impact, mitigation & remediation

What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

Successful exploitation permits arbitrary code execution on the affected SPIP instance, with high impacts on confidentiality, integrity, and availability. Attackers could access or modify data available to the compromised application and disrupt its operation.

Mitigation

If you can’t patch tonight, do this now.

Until upgrades can be completed, restrict access to SPIP instances to trusted networks where feasible and use an HTTP reverse proxy or web application firewall to reject requests containing the X-Spip-Filtre header. Monitor web-server and application logs for anomalous requests using this header and investigate potential compromise.

Remediation

Patch, then assume compromise.

Upgrade SPIP to version 4.4.21 or later. Distribution-managed installations should verify that the installed package includes the fix; an upstream fixed release does not necessarily indicate that a distribution package has been patched.

Exposure surface

Affected products & vendors

Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.

VendorProductType
SpipSpipapplication
FAQ

Frequently asked questions

Is CVE-2026-77806 exploited in the wild?
Yes. As of Nov 16, 2026, Mallory has reports of exploitation in the wild.
Is there a public exploit for CVE-2026-77806?
Yes. Mallory tracks 1 public exploit or proof of concept for CVE-2026-77806, the earliest disclosed Aug 24, 2026.
Is there a patch for CVE-2026-77806?
Upgrade SPIP to version 4.4.21 or later. Distribution-managed installations should verify that the installed package includes the fix; an upstream fixed release does not necessarily indicate that a distribution package has been patched.
What products are affected by CVE-2026-77806?
Spip.
How severe is CVE-2026-77806?
CVE-2026-77806 has a CVSS v3.1 score of 9.8 (Critical) and an EPSS score of 4.5% (92nd percentile) as of Nov 16, 2026.
Activity feed

Recent activity

21 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.

View more in app →
+2 more in the timeline. Sign up to see them
Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Mallory platform

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, and which detections to deploy tonight.
Exposure mappingQuery your assets running an affected version, and investigate the blast radius.
Threat actor evidenceEvery report linking this CVE to a named adversary.
Associated malwareMalware families linked to this CVE, with evidence and IOCs.
Detection signaturesYARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Vendor-by-vendor mappingCross-references every affected SKU, including bundled OEM variants.
Social activity15Community discussion across Reddit, Mastodon, and other social sources.