安全客•October 30, 2026•🇨🇳Translated from Chinese

360 Security Cloud Opens PHP2Shell Vulnerability Self-Check Platform to Government and Enterprise Users

360 Security Cloud has officially released a self-check platform for the PHP2Shell vulnerability, now open to government enterprises, large organizations, and small-to-medium businesses.

The platform enables organizations to answer critical questions about their PHP infrastructure: how many websites and systems are running on PHP, which of those instances are on affected versions, and whether any have already been compromised.

Users can apply for access by scanning a QR code provided in the announcement. Once approved, the service performs automated scans to map PHP deployments and flag vulnerable instances.

The release comes at a time when many organizations still rely heavily on PHP for web applications, making rapid self-assessment an important defensive step.

The original report was published on October 30, 2026, and states that the platform is intended to help both public-sector and private-sector entities reduce exposure to the PHP2Shell issue.

Related articles

Security NEXT•Vulnerabilities & Exploits

Critical PHP Vulnerability to Receive Patch on November 19 at 23:00 JST

A critical-severity vulnerability has been identified in the PHP scripting language, affecting all supported branches. The PHP security team has pre-announced a security update release scheduled for 14:00-14:30 UTC on November 19, which corresponds to 23:00-23:30 Japan Standard Time. Although the maximum severity rating is critical, the flaw does not impact default configurations and requires uncommon system setups to be exploitable. No specific technical details, CVE identifiers, or attack vectors have been disclosed ahead of the patch. The update forms part of PHP's regular four-week release cycle. This follows another serious PHP flaw called PHP2Shell that required emergency remediation in October. Organizations are strongly advised to prepare for immediate deployment once the fix becomes available.

BoletimSec•Vulnerabilities & Exploits

Java4Shell Vulnerability Enables Remote Code Execution Without Authentication Across Keycloak, Jira, Confluence and Other Enterprise Platforms

A critical flaw tracked as CVE-2026-114938 and dubbed Java4Shell allows unauthenticated remote code execution on multiple widely deployed Java applications including Keycloak, Jira, Confluence, JFrog Artifactory, Jenkins and PingFederate when running in their default configurations. The root cause lies in a buffer overflow inside the AVX-512-accelerated Base64 decoder of HotSpot JVM on x86-64 processors that support the VBMI instruction set. Malformed Base64 strings ending with an extra equals sign cause the decoder to write 62 or 63 bytes past the allocated output buffer before the Java runtime rejects the input. Because several authentication-related components such as Basic Auth headers, SAML artifacts and CSRF tokens are decoded before any session or access-control checks occur, the vulnerable code path executes with attacker-controlled data prior to authentication. The issue affects Java 17.0.6 and later releases on lines 21, 25 and 27 when running on Intel Xeon Ice Lake or newer and AMD Zen 4 CPUs; ARM64 systems remain unaffected. Oracle and OpenJDK released fixes on 18 November, CISA issued an urgent advisory the same day, and Amazon has already updated Corretto builds while Red Hat continues work on its distributions.

BoletimSec•Vulnerabilities & Exploits

Attackers Exploit Critical Apache Roller Flaw CVE-2026-129448 for Unauthenticated Remote Code Execution

Cybercriminals are actively exploiting a critical vulnerability in Apache Roller that allows remote code execution on the server without any credentials. The Java-based blogging platform received CVE-2026-129448 with a CVSS score of 9.8, and the Apache Software Foundation has confirmed active exploitation in the wild. The attack path targets the XML-RPC endpoint, which accepts vendor extension types and deserializes requests before performing authentication. The flaw affects versions 4.0.0 through 6.1.4, expanding the scope beyond the earlier CVE-2026-82384 that only listed version 6.1.5 as affected. Disabling XML-RPC through the admin interface provides no protection on older versions because deserialization occurs before the setting is checked. The recommended fix is upgrading to version 6.1.6 or later, which properly disables extension types and enforces the configuration. Organizations unable to update immediately should set enabledForExtensions to false in web.xml or remove the XML-RPC servlet mapping.

Habr•Vulnerabilities & Exploits

PHP Prepares Critical Patches for All Supported Versions One Month After Emergency Update

The PHP development team announced on November 18 that it will release updates for all supported interpreter versions to address multiple vulnerabilities, including critical ones. The fixes target a use-after-free flaw in file upload progress tracking that can lead to remote code execution when specific session serialization formats are combined. This comes shortly after emergency patches issued on October 21 resolved two remote code execution issues collectively known as PHP2Shell. The new vulnerability, tracked as CVE-2026-115560 with a CVSS score of 9.8, arises when applications switch session formats from php_binary or php_serialize to php after upload tracking has begun. Developers are advised to disable session.upload_progress.enabled until patches are applied and verified. Releases are scheduled for November 19 between 17:00 and 17:30 Moscow time, accompanied by a detailed security bulletin.