AI translation. Check versions, conditions and actions against the Japanese original and primary sources.
DAILY RECORD · 2026-10-26
Added Windows .NET, Perl HTTP handling, Siemens, and withdrawal of the attribution to PHP.
Review as of 10/26 10:27 JST. Exact JST dates remain unconfirmed for items whose original sources provide only dates.
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.
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.