PHP is a ubiquitous server-side runtime; an unauthenticated RCE in PHP can lead to widespread server compromise and major infrastructure disruption.
CVE-2026-109619
Use-after-free in PHP global state enabling remote code execution.
Is CVE-2026-109619 being exploited?
Yes. CVE-2026-109619 appears in CISA's Known Exploited Vulnerabilities catalog, which means exploitation in the wild has been confirmed and reported. Treat it as active rather than theoretical, and patch it ahead of higher-scoring vulnerabilities that carry no exploitation evidence.
How severe is CVE-2026-109619?
CVE-2026-109619 is rated Critical with a CVSS score of 9.2. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2026-109619?
Yes. A fix has been recorded for CVE-2026-109619. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-109619 affect?
CVE-2026-109619 affects PHP interpreter (server-side), Web servers running PHP scripts, PHP-FPM / Apache / Nginx with PHP modules. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-109619?
Install the PHP security update immediately, restart PHP processes, and audit for compromise.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Remote code execution on web servers via PHP use-after-free; attackers can execute arbitrary code and fully compromise hosts serving PHP.
Immediate action required
- affected>= 8.2.* and < 8.2.35
- affected>= 8.3.* and < 8.3.36
- affected>= 8.4.* and < 8.4.27
- affected>= 8.5.* and < 8.5.12
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.