As of 11 a.m. on October 23, 2026, about 36 hours after the official PHP patch was released, only around 210 of the approximately 5,500 PHP 8.2-8.5 servers eligible for patching in South Korea had installed the fixed versions. The PHP patch adoption rate, calculated by Security News and SK Ecure based on a Shodan investigation, stood at just 3.8%, leaving about 96% of servers unpatched. Security News’ PHP patch adoption survey showed a faster response than in the past, but also revealed that a defensive gap remains as AI shortens attack preparation time.
3.2 Percentage-Point Rise in 15 Hours: A Somewhat Faster Response
After the official patch was released at 11 p.m. on October 21, the patch adoption rate among the surveyed servers remained at 0.6% until 6 p.m. on October 22, before rising by 3.2 percentage points approximately 15 hours later. Companies typically take anywhere from several days to several weeks to apply patches after a vulnerability is disclosed, with an average deployment time exceeding 30 days. Even so, bringing adoption of this PHP patch close to 4% within 36 hours can be interpreted as evidence that security teams are responding faster than before.
However, the PHP 8.2 series, which has the largest number of servers, had the lowest adoption rate at 2.8%, while the 8.3 and 8.4 series recorded 4.2% each and the latest 8.5 series reached 6.2%. Official support for the PHP 8.2 series is ending at the end of this year, potentially making unpatched servers in that series an urgent priority.
| PHP Version | Fixed Version | Patch Adoption Rate by Series |
|---|---|---|
| 8.2 | 8.2.35 | 2.8% |
| 8.3 | 8.3.36 | 4.2% |
| 8.4 | 8.4.27 | 4.2% |
| 8.5 | 8.5.12 | 6.2% |
No Confirmed Successful Attacks: Alert Needed as Large-Scale Attempts Begin
Threat intelligence company KELA assessed that, as of October 22, no cases had been confirmed as successful attacks exploiting this vulnerability. CISA also had not yet added the two vulnerabilities to its Known Exploited Vulnerabilities catalog. However, the absence of confirmed successful attacks does not mean the vulnerabilities can be treated as safe.
Attack attempts have already been detected through external security firms. Amazon detected an attack attempt on October 17, while Cloudflare reported finding millions of attempts following the vulnerability disclosure. According to SOCRadar, hacking forums such as BreachForums and Dread also shut down their own sites because of this vulnerability. Distinguishing between successful and attempted attacks highlights that attack activity is already widespread, potentially extending well beyond the confirmed scope of compromises.
AI Shortens Attack Preparation Time: Patches Are a Starting Point for Defense and Attack
The use of AI for vulnerability analysis and attack-code generation has reduced the time and cost of preparing attacks. Attackers can prepare attack code through patch diffing, comparing the newly patched source code with older versions, and the release of a patch can provide attackers with reference material as well as defenders. Sansec anticipated that large-scale attacks would occur within 15 minutes of the PHP vulnerability patch’s release.
SK Ecure Executive Kang Ki-ho pointed out that “the time required to write attack code has been drastically shortened by AI” and said defenders are still falling behind. He noted that attackers could strike during a single day of delay in applying a patch, stating that “speed is the key to the response” and that “continuous monitoring is necessary even after remediation, rather than periodic checks on a monthly or quarterly basis”.
Immediate Version-Specific Updates: Continuous Verification After Patching
First, exposed PHP servers should be sorted by version and updated to 8.2.35, 8.3.36, 8.4.27, and 8.5.12. Organizations should not merely check the current adoption rate and close the matter as completed. They need a system that continuously monitors attack attempts and asset conditions even after patching.
This investigation excluded servers from which PHP version information had been removed. The actual number of servers eligible for patching and remediation actions may be higher, but the research team estimated that this exclusion would have little impact on the remediation rate. The investigation also noted that query results may differ depending on the solution used. Responding immediately after a vulnerability disclosure is no longer a task that can be deferred until the next round of periodic checks.
Source Article
This article was prepared with reference to the following source: Boannews — [Exclusive] 36 Hours After PHP Patch Release, South Korean Companies’ Adoption Rate Reaches 4%… “96% Still Unprotected” [PHP Outcry]
![[단독] PHP 패치 공개 36시간, 국내 기업 적용율 4%... “96% 아직 무방비” [PHP 파장]](https://darkpulse.kr/wp-content/uploads/2026/10/article-job_1792-job_17-15.png.webp)
Leave a Reply