Skip to content
PHP2Shell Exploits Detected Before Public Disclosure

PHP2Shell Exploits Detected Before Public Disclosure

First seen 22 Oct 2026, 17:46 UTC • •

Article Content

Browse articles
ThreatCluster AI
ThreatCluster •October 22, 2026 at 18:44 UTC
  • •Exploitation attempts began four days before public disclosure on October 17, 2026.
  • •Two critical vulnerabilities, CVE-2026-109618 and CVE-2026-109619, allow unauthenticated remote code execution.
  • •Multiple proof-of-concept exploits were detected immediately after the patches were released.

Amazon Threat Intelligence reported that attempts to exploit two critical PHP vulnerabilities, CVE-2026-109618 and CVE-2026-109619, began on October 17, 2026, four days prior to their public disclosure. The exploit attempts originated from an anonymized IP address, indicating a potential threat actor's early access to the vulnerability details. On October 21, 2026, further proof-of-concept exploits were detected shortly before the scheduled patch release. The vulnerabilities allow unauthenticated remote code execution, posing significant risks to affected PHP systems. AWS has not confirmed whether the exploitation attempts would have succeeded against real-world systems. The PHP project has issued patches for supported versions, while older, unsupported versions remain at risk. Organizations are advised to apply the patches promptly and monitor for suspicious activity.

Start a free Starter trial for enhanced analysis

Ask AI about this cluster

Updated just now How this analysis works

Timeline

2026-10-17
First exploit attempt detected
Amazon identified an attempt to exploit PHP vulnerabilities from an anonymized IP address, four days before public disclosure.
Securityaffairs.Co
2026-10-21
Public disclosure of vulnerabilities
CVE-2026-109618 and CVE-2026-109619 were publicly disclosed, with patches released at 14:00 UTC.
Techtimes
2026-10-21
Further exploit attempts observed
Multiple proof-of-concept exploits were detected between 02:00 and 08:00 UTC, shortly before patches were available.
aws.amazon.com
2026-10-21
CVE-2026-109619 published
Vulnerability assigned a CVE identifier and published in the National Vulnerability Database.
MITRE
2026-10-21
CVE-2026-109618 published
Vulnerability assigned a CVE identifier and published in the National Vulnerability Database.
MITRE

More articles in this cluster (4)

Following this threat?

Track Amazon and CVE-2026-109618 in your own feed — you're alerted when they show up in new reporting, leak sites or exploitation.

Free account · no card needed

Common questions

Which PHP versions are affected?
The vulnerabilities affect multiple PHP releases, including versions that no longer receive security updates.
Is there evidence of exploitation in the wild?
Yes, Amazon confirmed that exploitation attempts were detected before and after the public disclosure of the vulnerabilities.
What should organizations do now?
Organizations should apply the available patches immediately and monitor their systems for any suspicious activity.