Quick answers
- Is CVE-2026-109618 exploited in the wild?
- Yes. CVE-2026-109618 is known to be exploited in the wild, first recorded on 26 October 2026. Treat it as urgent.
- How severe is CVE-2026-109618?
- Critical severity, published 21 October 2026.
- Which products and versions are affected?
- PHP Group PHP 5.4 through 8.5.
- Is there a fix for CVE-2026-109618?
- Yes: fixed in PHP 8.5.12, 8.4.27, 8.3.36, 8.2.35. Until then: Customers on Google App Engine Standard and Cloud Run with automatic updates enabled may be automatically patched; redeploy workloads with updated PHP dependencies to receive fixes. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-109618 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-109618?
- Check whether you run Amazon AWS, Google Cloud Platform or PHP Group PHP at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- Fixed in: PHP 8.5.12, 8.4.27, 8.3.36, 8.2.35
Customers on Google App Engine Standard and Cloud Run with automatic updates enabled may be automatically patched; redeploy workloads with updated PHP dependencies to receive fixes.
Technical details
Two remote code execution vulnerabilities exist in PHP versions 5.4–8.5 that enable arbitrary code execution. The advisory does not specify the exact vulnerability classes or attack preconditions, but the "remote" classification indicates network-based exploitation is possible. Patches are available in PHP 8.5.12, 8.4.27, 8.3.36, and 8.2.35.
Affected products
- PHP Group PHP 5.4 through 8.5
Identifiers
- CVE-2026-109618
- CVE-2026-109619
Timeline
- 2026-10-21: advisory