GMO / Railway users
GMO corrected the request date at 00:20. 12:00 is the attacker's announced time. Railway issued a recovery notice; continue revoking and reissuing old secrets.
Check first-party updates →AI translation. Check versions, conditions and actions against the Japanese original and primary sources.
SECURITY REVIEW · 2026-10-27 07:47 JST / 2026-10-26 22:47 UTC
Keys, public APIs, and device updates, starting with what you have installed.
Organized GMO's correction, Railway recovery updates, Apple's security releases, and remediation for Consul, OpenHands, MCP, and AI inference infrastructure using primary sources. Database inclusion is distinguished from new compromise.
As of: 2026-10-27 07:47 JST / 2026-10-26 22:47 UTC. Change window: 00:18–07:47 JST.
Actual retrieval from 07:50 JST onward. Same-day follow-ups with only dates are reference items.
Quick overview: check only what you use.
Consul / Kubernetes
Inspect cached leaf certificates and private keys, HTTP API DoS, mesh authorization, and namespace boundaries separately.
Consul conditions and fixes →OpenHands / MCP / AI infrastructure
Inventory public sandbox authentication, Cloud Run MCP buckets, and vLLM/ONNX input paths. Check reachability conditions as well as versions.
Check public APIs and AI infrastructure →Devices / SDKs / dependency packages
Check supported Apple series updates, native TLS, Go JOSE, compression decoders, and malicious packages. Do not count the 324 Apple CNA additions as new victims.
Check endpoints and dependencies →Database and advisory updates in the window · 17 groups
Organized by database inclusion/revision and advisory update times. These are not attack start times or counts of newly occurring harm.
00:20 JST (official correction) · Publication/update verified.
GMO: date correction at 00:20 verified; 12:00 is the attacker's announced time.
At 00:20 JST, report 7 corrected the date of the request for device investigation from 10/23 to 10/25. Report 7's content cutoff is 23:10 the previous day, and devices remain under analysis. The information disclosure and ransomware attack announced for 10/27 12:00 are threats from someone believed to be the attacker, not confirmed damage already inflicted.
What to checkContinue device inspection, backups, and account protection from report 6. Check official individual communications and do not respond to requests for authentication codes or money.
00:48–06:21 JST (GHSA updated) · Publication/update verified.
31 GHSA reviewed revisions: Airflow and CA bundles were previously published
There are 0 reviewed advisories in the publication window and 31 in the revision window. These include existing advisories for Airflow JWT logout / Hive / Edge3 / Google / Sqoop / Mongo providers, NASA AIT-Core, AgentScope, Aim, AutoGPT, certifi emSign CA, ImageSharp, and others. Some were published in 2022–2025; do not turn the 31 into new zero-days this morning.
What to checkCheck installed packages against each GHSA's current ranges and fixes. Do not confuse certifi CA distrust with other Tailworm or Brotli fixes.
01:17 JST (NVD published) · Caveats on CNA record and prerequisites
OpenHands SDK: unauthenticated command execution in publicly exposed sandbox agents.
The CNA record for CVE-2026-112346 describes unauthenticated sandbox command execution with empty session_api_keys in SDK versions below 1.52.0. If the exposed port is reachable, root inside the sandbox and mounted workspaces and secrets are affected. The reviewed PR #5209 restricts DockerWorkspace host-side port exposure to 127.0.0.1 while retaining the 0.0.0.0 listener inside the container. This PR does not establish that the same fix applies to Apptainer, which the CNA also lists.
What to checkCheck fixes in software-agent-sdk 1.52.0 or later, recreate workspaces, and verify host port exposure and session key settings. Do not judge whether the SDK launcher fix is applied solely from the agent-server image tag. Separately investigate logs and revoke/reissue secrets from workspaces that were reachable.
SDK 1.52.0 release / DockerWorkspace fix PR 5209 / CNA-origin NVD record
01:17 JST (NVD published) · Caveats on CNA record and prerequisites
Cloud Run MCP: build bucket squatting
CVE-2026-85297 affects Google Cloud Run MCP below 1.11.0. Google CNA describes source code access, code execution, and exfiltration through bucket squatting. This is separate from the previously included MCP Toolbox cloud-storage issue.
What to checkUpdate Cloud Run MCP to 1.11.0 or later. Do not assess Toolbox and Cloud Run MCP as a single product; check the build path used and exposure of sensitive information.
01:17 JST (NVD published) · Caveats on CNA record and prerequisites
Netty tcnative: native TLS buffers, tickets, and SNI
CVE-2026-116539–116542 have different prerequisites involving native TLS BIO buffers, bytes-consumed reporting, SNI, session ticket rotation, and other features. The official GHSA for 116540 specifies builds with OpenSSL 3.0 or later, handshakes concurrent with hot rotation, affected versions from 2.0.81.Final, and a fix in 2.0.84.Final. Because this differs from the lower bound of 2.0.66.Final in the CNA record, this investigation does not establish the earliest affected version. Updating Java alone does not establish that the native library has been replaced.
What to checkVerify the netty-tcnative 2.0.84.Final fix and the native artifact actually loaded. Check OpenSSL branches, ticket rotation, and SNI routing usage conditions separately.
Netty official UAF advisory / Developer and CNA reference 1 / Developer and CNA reference 2 / Developer and CNA reference 3 / Developer and CNA reference 4 / Developer and CNA reference 5
01:17 JST (NVD published) · Caveats on CNA record and prerequisites
Apache Vysper: all versions affected; do not wait for a fixed version
CVE-2026-115721 involves unlimited allocation in XML parsing; 115748 involves missing authentication checks in XEP-0077. The project is retired and all versions are affected; Apache says no fixed release is planned. The latter requires an authenticated user to compromise another account.
What to checkIf using Vysper, migrate to an alternative. Do not assign an unannounced fixed version; consider access and registration-feature restrictions until migration.
Developer and CNA reference 1 / Developer and CNA reference 2
01:17–05:42 JST (GHSA published) · Disclosure and updates checked
npm: separate 25 new malware entries from existing revisions
The 25 new entries include npm @greenlake/*, @ppa-web-components/*, @drone-js-ext/*, and ctf-agent 0.1.0. Publication was at 16:17–20:42 UTC. GHSA listing does not confirm compromise of organizations using them; do not generalize to other versions solely from package-name or scope matches.
What to checkCross-check each GHSA's package and version against lockfiles, SBOMs, and install logs. If executed, isolate the environment and revoke/reissue secrets held there from a separate safe device. Do not consider uninstalling alone sufficient.
ctf-agent GHSA / @greenlake/auth GHSA / GHSA publication-window API
02:17 JST (NVD published) · Qualifications on CNA record and exploit conditions
vLLM: multiple conditions involving templates, shared memory, OCR, CORS, and Responses.
The CNA states that CVE-2026-115911–115918 are fixed in 0.32.0. They include resource exhaustion via request chat templates, shared memory identifiers, audio encoders, OCR/image processing, token ID boundaries, CORS, and Responses paths. Do not group issues requiring authenticated callers, specific models, or settings as blanket unauthenticated RCE.
What to checkCheck vLLM 0.32.0, public API authentication, arbitrary templates, model sources, image/audio inputs, and CORS settings.
Developer and CNA reference 1 / Developer and CNA reference 2 / Developer and CNA reference 3 / Developer and CNA reference 4 / Developer and CNA reference 5
02:17 JST (NVD published) · Qualifications on CNA record and exploit conditions
Autobahn / Rust zip / snappy-java / Go compress: separate decoder issues.
Autobahn CVE-2026-116579 is a DoS caused by checking the output limit of opt-in permessage-brotli after decompression, fixed in 26.10.1. Rust zip 115905 concerns central/local header filename mismatches, fixed in 9.0.5; the concurrently included 115906–115909 concern separate boundaries. snappy-java 116590 is fixed in 1.1.10.9, and the zstd panic in Go compress 116591 in 1.20.2. These are separate from Brotli2Shell CVE-2026-111497.
What to checkInventory decoders actually used and untrusted-input paths, and apply each fix. A shared compression format does not establish remediation of separate CVEs.
Developer and CNA reference 1 / Developer and CNA reference 2 / Developer and CNA reference 3 / Developer and CNA reference 4 / Developer and CNA reference 5
03:17 JST (NVD published) · Caveats on CNA records and prerequisites.
Consul: authorization bypass for cached leaf certificates and private keys
CVE-2026-105765 affects Consul 1.17.0–2.0.4 with ACLs enabled. Cached service leaf responses from the agent HTTP API lack ACL token checks, allowing a reachable attacker to obtain already cached certificates and private keys under the applicable conditions. By default, the API listens only on loopback, limiting exposure to processes on the same host. This does not mean keys for every service can be obtained unconditionally.
What to checkCheck Consul Community 2.1.0 and Enterprise 2.1.0 / 1.21.19 by release branch. Investigate agent API access restrictions and service identities and certificates that may have been exposed. Consider blocking the leaf endpoint only if Connect-native applications and consul-template do not depend on it.
03:17 JST (NVD published) · Caveats on CNA records and prerequisites.
Consul: HTTP API DoS, mesh registration, and health-check authorization.
CVE-2026-105626 exhausts memory through an unauthenticated HTTP API. 105608 allows Envoy escape-hatch configuration with service write permission and without mesh write. 115804 bypasses authorization, allowing an authenticated user to change other services' health checks on the same node. These have different prerequisites from the leaf private-key issue.
What to checkUpgrade using official series-specific procedures to Community 2.1.0 or Enterprise 2.1.0 / 1.21.19. Inspect HTTP API exposure, service write privileges, and check registrations separately.
Developer and CNA reference 1 / Developer and CNA reference 2 / Developer and CNA reference 3
03:17 JST (NVD published) · Caveats on CNA records and prerequisites.
ONNX: shape inference and low-bit arrays in untrusted models
CVE-2026-115919–115922 affect versions below 1.22.0. These involve malformed model inputs concerning RNN/LSTM/GRU rank validation, ConvTranspose, Scan shape inference, and 2/4bit unpack array sizes. Passing the checker alone does not guarantee safe shape inference.
What to checkCheck ONNX 1.22.0 or later. Place external model validation in a restricted environment and set time and memory limits.
Developer and CNA reference 1 / Developer and CNA reference 2 / Developer and CNA reference 3 / Developer and CNA reference 4 / Developer and CNA reference 5
03:17 JST (NVD published) · Caveats on CNA records and prerequisites.
Backstage: canonicalization mismatch in catalog URL rules
The 3.9.2 / 4.0.2 boundaries for CVE-2026-115923 are versions of the @backstage/plugin-catalog-backend package. A user with catalog.location.create permission can exploit differences between raw URL rules and URL reader normalization to have out-of-scope entities treated as trusted. A canonical URL matching fix was also confirmed in Backstage release v1.54.10; distinguish the main product version from the package version.
What to checkCheck @backstage/plugin-catalog-backend 3.9.2 / 4.0.2 or later for each release series. Do not assess only the displayed Backstage or custom portal version; inspect actual dependency packages, registration permissions, catalog.rules, and fetch URLs.
Developer and CNA reference 1 / Developer and CNA reference 2 / Developer and CNA reference 3
04:12 / 05:46 JST (status 19:12 / 20:46 UTC) · Publication/update verified.
Railway: recovery channel opened; distinguish existing users from new registrations
Official status notices at 19:12 / 20:46 UTC say recovery continues and explicitly state this is not an additional security incident. The primary report's 20:41 UTC revision distinguishes restoration for existing users from suspended new registrations. Changes against the existing original are additions to Continuous Updates; do not recount the earlier estimate of about 10 ten-thousand workspaces as a new leak this time.
What to checkContinue revoking and reissuing sensitive environment variables, API keys, and other secrets stored before 10/21, and auditing GitHub and registries. Recovery does not guarantee the safety of old keys. Resumption of new registrations this week is planned.
Railway official status / Railway primary report and ongoing updates
04:16 JST (NVD published) · Caveats on CNA record and prerequisites
consul-k8s: component privileges from a ServiceAccount in another namespace
CVE-2026-110720 applies to configurations with global.acls.manageSystemACLs=true. A user who can create a ServiceAccount and obtain its token in another namespace, and can also reach the Consul API, can elevate privileges through ACL binding rules for components.
What to checkCheck consul-k8s 2.1.0 / 1.8.18 by series. Verify Kubernetes RBAC, API reachability, and whether system ACL management is enabled.
07:16 JST (NVD published) · Qualifications on CNA record and exploit conditions
Go JOSE: distinguish fix boundaries in 4.1.5 and 4.1.6.
CVE-2026-116585 concerns empty CBC-HMAC JWE ciphertext, and 116586 concerns panic/stack overflow from deeply nested JSON; both are fixed in 4.1.5. 116587 concerns validation load from malformed RSA JWKs, fixed in 4.1.6, with conditions involving Go 1.24 or later. Do not treat 4.1.5 alone as resolving everything.
What to checkCheck go-jose 4.1.6 or later and rebuild embedded binaries. Impose input limits at entry points that parse untrusted JWE / JSON / JWK.
Go JOSE v4.1.5 release / Go JOSE v4.1.6 release / CNA-origin NVD record
07:16 JST (NVD published) · Qualifications on CNA record and exploit conditions
Kener / Transmission: management entry points and browser-mediated RPC
Kener CVE-2026-116747 affects 3.0.0 to before 4.1.10: DUMMY_SECRET fallback when KENER_SECRET_KEY is empty/unset allows an attacker who knows the administrator email to forge tokens. Transmission 116748 involves CORS exposing the RPC anti-CSRF token to other origins in 4.0.0 to before 4.1.3.
What to checkUpdate to Kener 4.1.10, configure a unique secret, and invalidate old sessions. Check the Transmission 4.1.3 fix and RPC authentication/access restrictions. Prioritize only if both products are deployed.
Developer and CNA reference 1 / Developer and CNA reference 2
Existing incident response and conditions · 5 groups
Supplementing conditions, fix/deployment methods, and operational impacts in previously published material. These are not recounted as new compromises during this period.
10/26 release (official date), NVD inclusion within the fixed window · Supplement to existing issues and response scope
Apple: check OS/Safari security releases dated 10/26
Apple primary sources confirm the 10/26 releases of iOS/iPadOS 27.2 and 26.7.2, and macOS Golden Gate 27.2. Of 532 new NVD records in this window, 324 are Apple CNA records and also reference fixes in earlier releases. This does not mean all 324 were newly shipped or confirmed exploited in this window.
What to checkMatch each device's supported series against Software Update and the official security releases list, and update the OS and Safari. Do not universally require series 27 for older-series devices; check supported models.
Developer and CNA reference 1 / Developer and CNA reference 2 / Developer and CNA reference 3 / Developer and CNA reference 4 / Developer and CNA reference 5
Updated the previous day at 23:00 JST (content continues in this retrieval) · Supplement to existing issues and response scope.
ConnectWise: preparations continue; keep connections disabled until individual instructions.
The retrieved text still shows a last update of 10/26 14:00 UTC. It describes preparations for phased onboarding and notification when restoration can begin. Do not rewrite the 10/26 target as a report of achievement; refer to the same primary text as previously.
What to checkKeep affected connections disabled until individual procedures are provided; separately investigate M365 app consent, forwarding rules, sign-ins, and devices.
Continued checking of existing advisories · Supplement to existing issues and response scope
PHP / PAN-OS / IceWarp: continue checking series-specific hotfixes and deployment
The latest PAN JSON timeline entry is 10/26 05:45 UTC; release information for the 4 hotfixes in the 11.1 branch is unchanged. The official IceWarp API text is also unchanged, revised at 15:30 UTC. Configuration changes in old IceWarp versions are partial mitigation, not complete remediation.
What to checkRestrict exposed management interfaces and check PHP fixes, product hotfixes, restarts of all workers, and the actual bundled copies. Do not convert PAN ETAs into shipped releases or apply IceWarp's memory_limit=-1 and similar settings unconditionally to other environments.
Latest stable 10/21 (verified in this retrieval) · Supplement to existing issues and response scope
Tailscale / eMudhra: latest stable 1.104.2; Tailworm fixed version unconfirmed
The latest stable official release is 1.104.2 dated 10/21. Do not reinterpret the version addressing the eMudhra intermediate CA as the minimum fixed Tailworm version. Source merges or environment variables alone do not establish a distributed fix.
What to checkDistinguish eMudhra remediation from the reachability conditions for SSH forwarding / Serve / Funnel and similar features, and track official bulletins and releases. Secure an alternative management path before disabling unnecessary forwarding.
Existing incident identified 10/16 / scope supplement · Supplement to existing issues and response scope
Genesys: distinguish internal LMS/CRM from customer platforms
The affected party describes an internal business system incident identified on 10/16. It confirms access to/acquisition of business contact and account information in LMS/CRM, while denying compromise of Cloud / Engage / Engage Cloud or call recordings in customer platforms. Investigation continues. Do not count this as a new intrusion in the current window.
What to checkWatch for suspicious contacts claiming to be Genesys and citing business information; verify through official channels. Do not generalize an internal CRM leak into compromise of all customer contact centers.
Reference: same day, but publication time undetermined · 1 group
This is current content retrieved after the target time. The following information is excluded from confirmed changes before the cutoff.
Dated 10/26, publication time unconfirmed · Publication before the cutoff is unconfirmed.
Reference: Frontline Education notice of August (month 8) incident
The party's 10/26 disclosure describes the start of individual notifications about unauthorized activity on 8/14–15 in Frontline Central / School Health Management. Affected information varies by individual, including SSN, date of birth, government ID, and Medicaid / Student ID. This is not a new 10/26 intrusion; because the publication time has only a date, it is separated from confirmed changes within the fixed window.
What to checkCheck your affected information and relevant credit monitoring guidance through the affected school district and individual notifications. Do not generalize that the same information leaked for every child.
Collection scope, overlap and limitations
532NVD new records
4,815NVD revisions
540GHSA publication window
182Verified saved and referenced responses
All 532 new NVD entries overlap with the 4815 revised entries. GHSA has 540 newly published advisories (unreviewed515, malware25) and 748 revised advisories. Distinguish reviewed, unreviewed, and malware, and check publication/revision overlap in the ledger. KEV is the 2026.10.23 edition with 1,756 entries, unchanged from the previous original. Inclusion and changes in original records are separate from attack start times. Absence from the list is not proof of no exploitation. Of 182 responses, 78 reference earlier originals to avoid duplicate storage.
- Cutoff is 2026-10-27 07:47 JST. Retrieved versions are current revisions from 07:50 JST onward and do not fully reconstruct original publication text.
- All 532 new NVD entries overlap the 4,815 revisions. They include 20 Rejected entries; 324 are from Apple CNA.
- The 540 GHSA publications comprise 515 unreviewed / 25 malware / 0 reviewed. Of these, 437 overlap this run's NVD CVEs and 78 overlap the previous run's NVD CVEs.
- All 540 published advisories are included in the 748 revised GHSAs. Breakdown: unreviewed687 / reviewed31 / malware30. Do not add all sets together as an incident count.
- NVD Received / Awaiting Analysis / Deferred and GHSA unreviewed do not mean exploitation or damage is confirmed.
- API inclusion/revision times are separate from the initial shipment of product fixes and attack start times.
- An unchanged KEV original, absence from KEV, or no feed delivery is not proof of no exploitation.
- Some API references return 404/403, and 1 research page has a redirect loop. Save failures in the collection summary; do not reinterpret them as empty counts.
- Railway's recovery notice is not an additional incident. Separate planned reopening of registration from recovery for existing users.
- Do not add CVEs from Apple's old and new series as newly shipped fixes this morning.
- This is not a comprehensive list of worldwide incidents or harm. Undisclosed incidents and unverified attacker claims are excluded from counts.
data/2026-10-27-0747/incident-register.json / data/2026-10-27-0747/collection-summary.json / data/2026-10-27-0747-vendors/collection-summary.json / docs/research-collection-2026-10-27-0747.md / docs/research-2026-10-27-0747.md / data/latest.json