Home › Intelligence › Brief
VULNERABILITY BRIEF 🔴 Critical Vulnerability

Critical PHP Stale Internal Request‑State Vulnerability (CVE‑2026‑109619) Allows Unauthenticated Remote Code Execution

A newly disclosed PHP runtime flaw (CVE‑2026‑109619) lets attackers execute code without authentication. The issue tests an organization’s patch‑and‑vulnerability‑management controls, a key trust signal for audit readiness.

Verisq™ Intelligence · 📅 October 27, 2026 · 📰 nvd.nist.gov
🔴
Severity
Critical
VU
Type
Vulnerability
🎯
Confidence
High
🏢
Affected
1 sector(s)
✅
Actions
3 recommended
📰
Source
nvd.nist.gov

PHP Stale Internal Request‑State Vulnerability (CVE‑2026‑109619) Enables Unauthenticated Remote Code Execution

What It Is — The PHP runtime contains a “stale internal request‑state” flaw that lets an unauthenticated attacker inject and execute arbitrary code on the host. The issue resides in the way PHP re‑uses internal request structures across separate HTTP calls, allowing a crafted request to corrupt the state of a later request and trigger code execution. The vulnerability is publicly listed in the CISA Known Exploited Vulnerabilities (KEV) catalog and is assigned CVE‑2026‑109619. No public exploit code has been released, but the CVSS vector (AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H) yields a 9.8 Critical base score. The PHP Group has issued an advisory and is preparing a patch; customers are urged to apply updates as soon as they become available.

Affected Products – PHP Group PHP (all supported versions prior to the forthcoming security release).

Why It Matters for Trust & Control Assurance – The flaw tests an organization’s patch‑and‑vulnerability‑management controls; a lapse lets attackers bypass authentication entirely.

Recommended Actions –

  1. Verify the exact PHP version in use across all web‑application servers.
  2. Apply the vendor‑released patch immediately once available; if a patch is not yet released, implement temporary mitigations such as disabling the affected request‑handling modules or enforcing strict input validation.
  3. Record the remediation step in your change‑management system to provide auditable evidence of control execution.

Source: CISA KEV – CVE‑2026‑109619

📰 Original Source
https://nvd.nist.gov/vuln/detail/CVE-2026-109619 ↗

This Verisq Intelligence Brief is an independent analysis. Read the original reporting at the link above.

Vulnerability exposure

Is this CVE in your supply chain?

Verisq matches published vulnerabilities against the software your vendors run, so you know which relationships this touches before the next review.

See vendor exposure →