Palo Alto Networks
Responding to core PHP vulnerabilities CVE-2026-109618 and CVE-2026-109619
At a glance
Elevated attack likelihood (~100% in 30 days). Exploitation not confirmed.
Medium rather than High: UK relevance is 40 of 100, little UK-specific signal so far.
Briefing
- PHP uses longjmp() for out-of-memory (OOM) errors to exit the current context and abort handling of the request
- Do not treat uncorroborated claims as confirmed breaches.
Questions to ask IT
- Do we run PHP and Palo Alto Networks PAN-OS, and which versions?
- Is any of it reachable from the internet?
- If it is still not patched, what mitigation is in place, and what is holding the fix up?
Next steps
- Confirm whether this affects systems or suppliers in your estate
Vulnerability facts
Full CVE detail CVE-2026-109618- 9.2 · CriticalExploitable over the network without any account, under specific conditions, and no one has to click or open anything. High impact on confidentiality, integrity and availability.CVSS:4.0/AV:N/AC:H/AT:P/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
- Listed: attacks using it have been seen
- Elevated attack likelihood (~100% in 30 days)
These facts are for CVE-2026-109618. This event covers 1 more CVE, each with its own record.
- PHP uses longjmp() for out-of-memory (OOM) errors to exit the current context and abort handling of the request
Next steps
- Review the advisory against your asset inventory and patch cadence
Summary
- CVE-2026-109618 has an estimated ~100% chance of attack in 30 days (100th percentile) as of 2026-10-26 — probability signal, not confirmed exploitation
Products and services involved
- PHP93% match confidence · CVE-2026-109618
- Palo Alto Networks PAN-OS93% match confidence · CVE-2026-109618
Same event, different frames
Distinct often headline the same incident differently.
Pulse
Last checked 30 Oct · Recheck overdue since 31 Oct 2026, 21:05 UK time
Listed on the CISA catalogue.
Listed on the — prioritise confirming exposure and patching.
Sources
- SecurityWeekNews
Tech and Security Companies Respond to PHP2Shell Vulnerabilities
- wiz.ioNews
PHP2Shell: AI uncovers critical RCE vulnerabilities affecting 70% of the Internet
- OpenAINews
Patch the Planet: global response coordination as agents uncover critical vulnerabilities
- SecurityWeekNews
Tech and Security Companies Respond to PHP2Shell Vulnerabilities
- BBCNews
PHP: What is it and why did it spark a global cyber security scramble?
Responding to core PHP vulnerabilities CVE-2026-109618 and CVE-2026-109619
How we know
Statements extracted from sources. Higher confidence means stronger corroboration.
- ClaimedHeadline60% confidence
PHP uses longjmp() for out-of-memory (OOM) errors to exit the current context and abort handling of the request
- ProbableSummary fact75% confidence
Responding to core PHP vulnerabilities CVE-2026-109618 and CVE-2026-109619 Google Cloud
- ConfirmedCVE identifier95% confidence
Event involves CVE-2026-109618
- ConfirmedEstimated attack likelihood95% confidence
CVE-2026-109618 has an estimated ~100% chance of attack in 30 days (100th percentile) as of 2026-10-26 — probability signal, not confirmed exploitation
- ConfirmedCVE identifier95% confidence
Event involves CVE-2026-109619
- ConfirmedEstimated attack likelihood95% confidence
CVE-2026-109619 has an estimated ~100% chance of attack in 30 days (100th percentile) as of 2026-10-26 — probability signal, not confirmed exploitation

