RISIKOMONITOR

PHP2Shell situation report — Switzerland

CVE-2026-109618 / 109619 · Loading data…

Is your website affected? Check now, free of charge.

For privacy reasons we show the status of a specific domain only to its owner — confirm ownership by e-mail at the same domain.

Map by canton

Loading map…

Figures by canton

PHP versions (detail)

Daily comparison

Legend: low medium high calculating — share of affected web servers. Canton = registered office per imprint. All data without warranty.

Map by province

Loading map…

Figures by province

PHP versions (detail)

Daily comparison

Legend: low medium high calculating — province = server/hosting location. All data without warranty.

Map

Loading map…

PHP versions (detail)

Daily comparison

Liechtenstein — national aggregation (no regional breakdown). All data without warranty.

EU / EEA total. Countries by measured exposure — grey = no data yet. Click a covered country for the detail view.

Figures by country

Ranking by affected rate

Rate = affected web servers as a share of those reachable live. Rank 1 = lowest rate (least affected), last = most affected. Only countries with data.

Carte par région

Carte en cours de chargement…

Indicateurs par région

Versions PHP (détail)

Comparatif quotidien

Légende : vert = à jour / sans PHP · orange = version masquée · rouge = vulnérable. Région = hébergement / mentions légales. Sans garantie.

What is this about?

On 21 October 2026, two critical vulnerabilities in the PHP core were disclosed: CVE-2026-109618 and CVE-2026-109619 ("PHP2Shell", CVSS 9.2). Both allow remote takeover of a server without credentials. This report shows — without naming individual companies — how widespread the vulnerability still is across the EU/EEA.

Secure versions: PHP 8.5.12, 8.4.27, 8.3.36, 8.2.35 or newer. Anything below, as well as end-of-life branches (8.1 and older), is considered affected.

The vulnerabilities in detail

CVE-2026-109618 — "PHP2Shell", part 1 · CVSS v4.0 9.2 (critical)

Pre-announcement 20 Oct 2026, release 21 Oct 2026 at 14:00 UTC. Remote code execution via memory corruption on out-of-memory: OOM handling can interrupt PHP while internal request data is only half-initialised — cleanup then treats this invalid data as valid. Exploitable unauthenticated, with a demonstrated exploit that strikes before any application code runs (most at risk: mod_php).

CVE-2026-109619 — "PHP2Shell", part 2 · CVSS v4.0 9.2 (critical)

Same date, same rating. RCE via stale global state: request data survives although its memory has already been freed; the next request on the same worker accesses it before normal initialisation resets it. Technically a use-after-free (CWE-416). Both flaws are fixed by the same fix commit (fixed in 8.5.12 / 8.4.27 / 8.3.36 / 8.2.35; for 7.4, 8.0 and 8.1 only minimal source backports). Active attacks have been reported since 21 Oct 2026.

CVE-2026-115560 — new, still unpatched (published 23 Oct 2026)

A separate session vulnerability that the 21 Oct releases do not fix. Only an unusual setup is affected: session.serialize_handler is set to php_binary or php_serialize and is switched at runtime via ini_set() to php — specifically before session_start(). PHP has not yet named a score, affected versions or a fix version; the fix will come in the regular release cycle, not as an emergency. No exploitation known. Mitigation: session.upload_progress.enabled=0 — the same setting already recommended for 109619.

In short: 109618/109619 are critical, actively exploited and fixable by update. 115560 is a narrow edge case without an official severity and without a patch — but with the same mitigation.

Sources: PHP.net security advisory (21 Oct 2026) · The Hacker News · SOCRadar · slabbdev lab release.

How is this measured? — purely passive

A web server voluntarily sends headers with every normal page request (e.g. X-Powered-By: PHP/8.1.2). We load the homepage once, exactly like a browser, and read only this information that is sent publicly anyway.

  • No pentest, no exploit, no login attempt, no payload.
  • No more load than a single visitor.
  • No individual websites are published — only aggregate figures per country/region.
  • Servers that hide their version are reported as "version hidden", not counted as affected.

Affected? What to do?

  • Update PHP to a secure version (or have your host update it).
  • No immediate update possible: enable WAF/Cloudflare protection, check logs.
  • expose_php = Off setzen.

Questions, or want an entry checked/removed? Contact via risikomonitor.com.

Check now, free of charge — is your website affected?

Status for the owner only — confirmation by e-mail at the same domain.