AI translation. Check versions, conditions and actions against the Japanese original and primary sources.
SECURITY REVIEW · 2026-10-26 10:27 JST
A broad recheck of incidents since PHP. Covers missing .NET fixes, effects on devices, credential compromise, and corrected explanations.
As of: 2026-10-26 10:27 JST / 01:27 UTC. Actual retrieval occurred after the cutoff.
“What is happening now” includes ongoing responses, not only incidents occurring this morning.
The following 4 items are changes in fix availability, public information, and investigation explanations. Disclosure times are distinguished from attack start times.
Out-of-band fix announcement · 03:50:05 JST (UTC 10/25 18:50:05).
Microsoft says the fix for CVE-2026-70197 was not included in the 10/13 updates. It involves reuse across IPv4/IPv6 datagram sockets on Windows.
What to check Update Windows runtimes to applicable branches such as 8.0.33 / 9.0.22 / 10.0.14. Rebuild and redistribute self-contained applications and verify the runtime actually running.
Developer technical report · Sent 01:56–01:57 JST; feed delivery later
Issues in HTTP framing and connection processing were disclosed. Starman and PSGI/Plack differ in affected scope and fixes. Do not count registered CVEs as attacks.
What to check Starman 0.4019 or later. For Plack, check the original advisory's fix guidance of 1.0057 or later and note version-boundary inconsistencies with its affected-scope section.
Japanese information updates / supplements to existing advisories · JVN feed at 09:00 JST; text gives date only
Siemens' October (month 10) information was updated, and a PHP2Shell advisory for PAN-OS on RUGGEDCOM APE1808 was confirmed. This does not mean all Siemens products have the same flaw.
What to check Check SSA-566512 products, virtual appliances, and fix conditions. The 19 new/21 updated entries are a monthly list, not new intrusions this morning.
Correction to the investigation explanation · Unit 42 original updated 10/25, time unspecified.
Unit 42 could not confirm PHP2Shell as the initial entry point in the government incident and withdrew its 10/23 explanation. This does not negate observed attack attempts.
What to check Distinguish observation of attempts, successful exploitation, and attribution of initial intrusion. Do not write that this is confirmed as the cause of a government agency compromise.
Vendor status update · Original source 10/25, time unspecified
For some PAN-OS series bundling PHP2Shell, the vendor changed status from planned to available. This differs from the ETAs for other series.
What to check 10.2.18-h13 / 11.1.16-h4 / 11.2.10-h16 and related versions; match the series and model in use against the official table.
Vendor disclosure and supplementary coverage this run · Original dated 10/19; exact JST time unconfirmed.
This additional investigation also includes two official reports absent from the earlier list. APITemplate.io reports intrusion through template processing; Genesys reports on internal business systems. Their affected scopes differ.
What to check Compare stored external storage credentials and API keys with each service's impact explanation. See the additional research notes for details and primary links.
APITemplate.io official statement / Genesys official statement
PHP, GitLab, Arista, CODE, Plex, SiteGuard, and others. Check public reachability, affected configurations, and running versions. Installing a patch does not prove an existing intrusion has been removed.
LiteLLM, Railway, ConnectWise, and others. Preserve logs and check leaked keys, added owners, permissions, and consent. For keys used outside your app, consult provider-side logs.
Includes .NET self-contained applications, Brotli, JRE, certifi, kernels, and appliances including PAN-OS. A source fix or downloaded update alone does not complete remediation.
Check Tailworm, AI/MCP, and other issues by permissions, features, and input paths. Preserve unconfirmed minimum fixed versions and numbering discrepancies, and reduce unnecessary permissions and exposure.
21 groups including important past matters. This is not a count of 21 new compromises. Each row's sources record affected conditions, series-specific fixes, and caveats.
| Affected products | Conditions and current assessment | Actions to check | Evidence and details |
|---|---|---|---|
| PHP itself | Public PHP, including older versions from 5.4 onward. AWS observed attempts from 10/17. Investigate individual host compromise separately. | Check 8.2.35 / 8.3.36 / 8.4.27 / 8.5.12. Maintain upload progress mitigation for subsequent 115560 as well. | Attack attempts observed |
| PAN-OS / embedded products | Management Web UI / XML API and product-specific configurations. PAN-OS on RUGGEDCOM APE1808 is also in scope. | Separate available hotfixes from planned series. Match models against the vendor table and restrict management-interface reachability. | Updated fix availability |
| Node / Brotli / Bun / Envoy / Istio | Untrusted-input decompression, automatic HTTP response decompression, and bundled copies. Researchers demonstrated this in official builds. | Node 22.23.4 / 24.22.1 / 26.12.1. Check Bun 1.4.4, brotli 1.2.1 / brotlicffi 1.2.1.0, and others individually. | Researcher demonstration |
| GitLab / Ruby | Self-managed GitLab and Ruby applications compiling untrusted Regexp. | GitLab 19.5.1 / 19.4.3 / 19.3.6 / 19.2.9 / 19.1.9 / 19.0.10 / 18.11.13. Ruby 4.0.9 / 3.4.12 / 3.3.13. | Check fixes and configuration |
| Arista VCO | A reachable valid account. Privilege escalation is possible even from read-only access. | 5.2.3.18 / 6.1.3.10 / 6.4.2.12 or later. Investigate management configuration and account compromise. | Exploitation confirmed |
| Nextcloud Built-in CODE | richdocumentscode <26.4.303. Watch paths that remain while stopped. | Update to 26.4.303 or later, or remove. Disabling the app alone is insufficient. | Exploitation confirmed |
| Plex / SiteGuard / KEV edge devices. | Check affected configurations and exposure for Plex, SiteGuard, VPNs, and other products. | Plex minimum fixed version: 1.43.3.10861. Continue product-specific updates, key/token measures, and compromise investigations. | Exploitation confirmed |
| 5 Fortinet products | FortiOS / Manager / Analyzer / Mail / Authenticator. By model and branch. | Consult the 10/21 hardening scope table and upgrade paths. Do not postpone updates while awaiting detailed PSIRT publication. | Vendor update guidance |
| Windows .NET | Requires reuse of SocketAsyncEventArgs between IPv4/IPv6 datagram sockets. | 8.0.33 / 9.0.22 / 10.0.14 and others. Verify rebuilding/redistribution of self-contained applications and the running runtime. | Out-of-band release for missing fixes |
| Perl HTTP servers | Starman HTTP handling and HTTP::Server::PSGI. An advisory separate from confirmation of actual harm. | Starman 0.4019 or later. For Plack, check 1.0057 or later as listed in Solutions, noting the inconsistent numbers in the announcement. | Technical advisory |
| Java / Python / CA | eMudhra keys and TLS trust. OS stores and app-bundled JRE, certifi, and pip also have separate distribution paths. | Do not stop at Java's routine CPU; verify emergency CA remediation and distributed builds. A Python main merge is not evidence of an installed fix. | Keys and trust paths |
| DNS / Apache / NGINX | Product-specific conditions for BIND / Unbound / PowerDNS / Knot, Tomcat / httpd / ATS, and NGINX. | BIND 9.20.30 / 9.21.27, Unbound1.26.2, and others. Check unfixed exceptions in ATS 9.2.16 and NGINX configurations. | Product-specific technical advisories |
| Kernel / containers / CI | Infinity Core and others. The boundary from execution privileges inside containers to shared hosts. | Apply distribution fixes and restart. Check the running kernel. Do not consider application updates alone sufficient. | Public PoC and privilege escalation |
| LiteLLM / Railway / Andromeda | Malicious distributions, environment variables, and entrusted credentials. Impact scope and cause differ by incident. | Isolation, evidence preservation, key revocation, usage-log review, and clean rebuilding. Do not retain earlier cause hypotheses as confirmed explanations. | First-party compromise report |
| ConnectWise / M365 | Cloud Backup application credentials and customer-tenant permissions. | Keep connections disabled until formal individual procedures arrive. Investigate service principal authentication, added keys, owners, consent, and mail operations. | Completed reopening unconfirmed |
| APITemplate.io / Genesys | An incident disclosed on 10/19 supplementing earlier coverage. Stored-storage credentials and internal CRM/LMS are separate targets. | Revoke affected credentials and investigate access. Distinguish the Genesys service itself from the scope of internal business data. | Existing incident context |
| Tailworm / Tailscale / headscale | Check researchers' exploit conditions, including SSH, connection permissions, conn25, and Serve. | Reduce unnecessary permissions and features. Do not assume 1.104.2 or 0.29.6 is a Tailworm fix. | Research report: minimum fixed version unconfirmed |
| Authentication, management and AI / MCP | Snipe-IT / Parse / rclone / vLLM / Firecrawl / Dokploy and others. Distinguish later inclusion in overall GHSA data from developer announcements. | Check affected configurations, version boundaries, and unresolved points in the previous night's table. Updating vLLM to 0.24.0 alone does not address every issue. | Technical advisories and research |
| Images / Wasm / packages | Specific processing in Pillow FPX + olefile, Wasmtime Cranelift, Laravel/Echo, and others. | Pillow 13.0.0, Wasmtime 36.0.19 or 43.0.0, and others. Also check the release series, inputs, and supported Python versions. | Technical advisories and research |
| Japanese business / browsers / devices / OT | Pleasanter, LIFF, Mitsubishi Electric, HPE, Lenovo, Firefox, and domestic Web/API alerts. | For Japanese updates, consult JVN/JPCERT; for devices, return to affected models and distributed versions. Do not assert CAPCOM/GMO incidents share PHP's cause. | Distinguish incident reports from advisories |
| OpenCode Console | Earlier user reports. No public primary vendor report could be verified this time. | Do not upgrade existing user reports to confirmed compromises. Affected users should check provider keys, usage logs, and individual notifications. | Still unconfirmed in primary sources |
New CVE inclusion and rechecking previously published research. None of the entries below are treated as confirmation of actual harm.
CVE inclusion and code cross-check · NVD inclusion at 10:17:15 JST, not attack start time.
An MCP server by QuantGeekDev, separate from Docker's official products. CNA-listed versions are 0.1.0 / 0.2.0. A path embedding project_name in a shell string on Windows was confirmed. The Unix argument-array path does not have the same conditions.
What to check The minimum fixed version remains unconfirmed in this investigation. Restrict paths passing untrusted input to the affected Windows tool, and check exposure and execution privileges.
CVE inclusion and official code cross-check · 2 entries included at 10:17:15 JST; original reports predate this.
CVE-2026-116103 / -116104 concern input evaluation paths in encode_param and the NNP converter. The CNA lists versions through 1.39.0 and describes the product as unsupported. Do not infer unconditional network RCE in every inference API.
What to check The minimum fixed version is undetermined. Do not convert suspicious parameters or NNP files; isolate processing environments, credentials, and outbound communications.
Official encode/decode code / Official converter code / CNA record
CVE inclusion / checking existing fixes · NVD inclusion at 08:17:41 JST; fixes predate this
JPEG memory allocation in smg CVE-2026-116095 is fixed in official 1.11.0. llama.cpp CVE-2026-116096 concerns malicious mmproj processing in Pocket-TTS. Distinguish the CNA's b11796 remediation, detection through assertion failure, and fundamental prevention.
What to check Check smg 1.11.0 and image resource limits. In llama.cpp, do not load mmproj files of unknown origin; treat the overall minimum version that safely rejects malformed models as unconfirmed.
Official smg 1.11.0 / Official llama.cpp fix PR / Researcher's reproduction and unfinished PR
Confirmed through renewed reporting of 10/22 research · Secondary article at 00:49 JST; primary research dated 10/22 (date only)
Researchers report detecting and blocking an attempted malicious npm installation originating from an instruction file in Downloads on a customer's device. How the file actually arrived is unknown. Do not imply that the web-to-agent path and credential transfer experiments were all observed on that same physical device.
What to check Do not launch agents in Downloads or other locations containing untrusted files. Check unfamiliar instruction files, MCP/API destinations, and changes to approval settings. Do not publish experimental success rates as victim proportions.
Fixed window: 10/25 23:18–10/26 10:27 JST. All 28 new NVD records are included in the 4,276 updated records. Of 93 GHSAs, 73 already appeared in the previous new-NVD set. Do not add them as new incident counts. Absence from KEV also does not prove a lack of exploitation.
Cross-checked NVD at all severity levels, the GitHub Advisory API, CISA's official mirror, domestic alerts, developers, researchers, and official feeds. Verified post-decompression SHA-256 hashes of 45 original responses. Events outside feed coverage, undisclosed incidents, and undocumented changes after retrieval cannot be covered comprehensively. Recorded the old IPA URL404 and Reddit API403; retrieval failures were not reinterpreted as “no issues.”
Collection scope, overlaps and failures / Additional primary-source research / Originals, URLs, retrieval timestamps and hashes
Previous: 10/25 23:18 overnight investigation / 10/25 16:34 broad review