We checked this claim: is it true that
JPCERT/CC updated its PHP advisory to warn of rising active attacks and added vulnerability CVE-2026-115560?
JPCERT/CC updated its advisory on October 26 after finding active attack probes, public exploit tools, and an added flaw tracked as CVE-2026-115560
Japan cyber agency warns of rising web attacks
JPCERT/CC updated its PHP alert after attackers began using public tools against exposed servers.
The story continues

Third PHP Flaw Demands Settings Check Over Fresh Patch
30 October 2026A newly identified weakness in the engine behind millions of websites requires precise settings changes rather than emergency software updates.Cloudflare bets bounty on web defenses
29 October 2026Cloudflare is offering cash rewards to researchers who can crack its web firewall protecting unpatched server software against emerging exploits.
Nextron flags unproven botnet code threat
28 October 2026A German firm found attack code inside a malware file, but no one has shown it works in the wild.
In a nutshell
Japan's cybersecurity agency elevated its warning for web servers running PHP after online attackers began weaponizing publicly shared exploit scripts against live systems. The agency maintained its initial patching guidance but expanded its alert to include a related security flaw, urging administrators to audit their networks immediately for active intrusions.
Highlights
- JPCERT/CC first instructed administrators on October 22 to apply vendor patches and configuration fixes for CVE-2026-109618 and CVE-2026-109619.
- The agency revised its alert on October 26 after tracking active network probes using publicly circulated proof-of-concept exploit tools.
- The updated guidance added flaw CVE-2026-115560, widening the known attack surface for unpatched deployments.
- Defenders must inspect server logs for evidence of active compromise rather than relying solely on future patching.
From the Editor’s Diary
When theoretical software flaws turn into circulating public attack tools, defense must shift immediately from routine patching to active compromise audits.
Who's involved
JPCERT/CC
Japan's national computer emergency response coordination center
goal → Protect network infrastructure by delivering timely vulnerability warnings and defense guidance
PHP Development Team
The open-source programming group maintaining the PHP web language engine
goal → Issue software patches that block unauthorized remote code execution
Web Infrastructure Administrators
Corporate and public-sector technical teams managing PHP servers
goal → Safeguard network assets by applying official fixes before attackers strike
In short
Corporate servers face immediate break-ins rather than theoretical flaws after internet attackers weaponized public tools against systems running PHP, the software engine powering much of the global web. The shift turns a standard maintenance chore into an urgent defense emergency for system operators.
Unpatched organizations face break-ins unless administrators inspect their system logs immediately to see if intruders already bypassed early defenses.
That outcome is likely because attackers are already probing exposed setups with publicly shared exploit methods, making quick intrusion attempts easy to automate.
Previously in this story

CISA orders federal agencies to patch PHP flaws by October 29
27 October 2026The cybersecurity agency warns hackers are actively exploiting code that runs behind millions of web services and federal systems.Wikidot restores sites after fixing flaw
25 October 2026The hosting service brought creative writing archives back online after closing a severe server security gap without finding any intruder activity.IIJ catches hackers weaponizing PHP2Shell flaw
25 October 2026Japanese telecom provider finds live attacks turning servers into attack botnets right after emergency software fixesVulnCheck breaks web defenses on millions of servers
24 October 2026Flaws in the PHP web language bypass standard Linux memory protections to seize control of live internet applications.
CISA sharpens rules as website bug risks spread
24 October 2026Flaws in code powering millions of sites drew attacks, but feared break-ins remain unconfirmed.
UK Parliament shuts 36 public digital services
24 October 2026Britain took dozens of online public portals offline as a precaution after security flaws were discovered in widely used web software.UNAM leaves web security warning unanswered
24 October 2026Mexico's largest public university has not confirmed or denied a researcher warning of an unpatched flaw on its main site.
New Flaw Leaves Patched Websites Open to Attack
24 October 2026Emergency repairs for the web's most popular code missed a narrow backdoor.
Japan scrambles to patch widespread software flaws
22 October 2026A race to fix underlying web software causes temporary public disruptions, but officials report no verified breaches.
PHP emergency website patch faces unproven bypass fears
21 October 2026Online warnings claimed that a new fix for the programming language powering millions of websites had failed, but technical evidence shows no broken security update.
PHP fixes flaws rated 9.2 as exploit leaks drive early attacks
21 October 2026Millions of web servers face takeover risks after flaws leaked before fixes arrived.
How it unfolded
JPCERT Updates Exploitation Notice
JPCERT/CC issued a formal alert update across official channels and social media on October 26 to report active attacks against online systems.
Active Exploitation Forces Advisory Revision
Public release of exploit code accelerated attacks, forcing the agency to broaden its warning to cover an extra software flaw. JPCERT/CC had monitored public forums after its October 22 patch instructions as functional exploit scripts spread across online security circles. The agency updated its alert on October 26 after tracking live attacks against exposed PHP servers, adding CVE-2026-115560 to its docket and telling delayed defenders to audit system logs for signs of compromise.
Where things stand
The updated alert confirms that public exploit blueprints are now actively running against internet-facing servers. Defense teams must look backward through server traffic records rather than simply applying patches, checking whether newer exploit variants slipped past initial server workarounds.