AI translation. Check versions, conditions and actions against the Japanese original and primary sources.
NIGHT SECURITY REVIEW · 2026-10-25
23:18。
Tonight's checks and actions.
Check prerequisites of new reports while continuing ongoing compromise response.
As of: 2026-10-25 23:18 JST / 14:18 UTC. Actual retrieval occurred after the cutoff.
This is not an immutable reproduction of the content at that time. Unspecified edit times remain undetermined.
Tonight's priorities
- Continue addressing active exploitation and public services.For PHP, GitLab, CODE, Plex, and others, update and investigate compromise in parallel. Do not stop existing work because of Tailworm discussion.
- Inventory Tailscale features.Check whether SSH, headscale, conn25, and Serve are enabled and their permissions. Reduce unnecessary permissions.
- ConnectWise's 23:00 update.Phased onboarding on 10/26 is a target. Keep connections disabled until individual procedures arrive.
- Authentication, management and AI execution infrastructure.Match applicable conditions and fixes in the table below. Do not reinterpret NVD inclusion as new occurrence or actual exploitation.
- Fortinet, certificates, Brotli, and DNS.Verify mitigations through bundled copies, containers, and running processes.
23:00 update: recovery targets and reconnection authorization
ConnectWise updated at 10/25 14:00 UTC. It plans to provide access to restore existing backups first, followed by partner re-enrollment guidance. Infrastructure recovery does not mean all functions are restored; 10/26 is the target for phased resumption. Separately from statements about stored backups, investigate unauthorized authentication, added keys, permissions, and mail operations in customer M365 environments.
Additional checks: authentication and execution infrastructure
Many items below were already disclosed by developers on 10/8–10; 10/25 is their NVD listing date. This material does not confirm actual exploitation. Check authentication requirements, enabled features, and bundled products.
| Products and CVEs | Affected conditions | Fixes and temporary mitigations | Primary sources and caveats |
|---|---|---|---|
Snipe-IT CVE-2026-116199 | 8.6.2 and earlier. Requires Google SSO, email-format usernames, and a valid Google identity remaining for a disabled local user. | 8.6.3. Complete offboarding at the IdP too, and check for re-login with former privileges. | Developer. The default username format does not have the same conditions. Developer rating Moderate; NVD score 9.2 |
Snipe-IT CVE-2026-116200 | 8.6.2 and earlier, LDAP StartTLS usage, attacker on the network path | 8.6.3. Do not continue binding after encryption fails. If suspicious, investigate and rotate service/user credentials. | Developer. Not simply a Google SSO-only issue |
Parse Server CVE-2026-116163 | AuthAdapterThe validation method of a custom adapter inheriting from it is not called. Built-ins and plain objects differ | 8.6.102 / 9.10.5-alpha.2. Check the series and verify custom authentication and additional factors. | Developer. Not unconditional authentication bypass for all apps |
Parse Server CVE-2026-116165 | MongoDB deployments. Class schemas can be deleted without a master key, losing CLP/protected fields. PostgreSQL is excluded. | 8.6.101 / 9.10.4-alpha.4or later. If also affected by the adapter issue above, meet its fixed-version requirement too. Updating alone does not restore deleted schemas/permissions. | Developer. Object ACLs still apply |
YesWiki CVE-2026-116207 | SQL injection in the unauthenticated Bazar search API. Developer scope: 4.6.7–below 4.7.0 / 5alpha1–below alpha4. | 4.7.0 / 5.0.0-alpha4. Check credential impact and exposed APIs | Developer. NVD text says from 4.6.0, an inconsistent starting version. Do not declare 4.6.0–6 safe. |
rclone CVE-2026-116191 | 1.75.1 and earlier,serve webdavwrite path outside its root | 1.75.2. Restrict exposure and backend permissions, and investigate writes outside the root. | Developer. Do not treat allserveformats as the same issue |
rclone CVE-2026-116192 | rcd --rc-serve and existing http/netstorage remotes. Destination substitution and leakage of headers, temporary signatures, and other data | Stop unnecessary exposure and restrict remote/backend access and egress.A definite minimum fixed version remains unconfirmed | Developer. The structured field says fixed in 1.74.2, while the text inconsistently says it reproduces in 1.75.1. Do not consider 1.74.2 alone sufficient. |
vLLM CVE-2026-116176 | At least 0.9.2 and below 0.24.0, prefill workers using P2pNcclConnector and API calls. SSRF and KV-cache transmission | This fix is 0.24.0. Restrict connector paths, destinations, and API permissions | Developer. Do not infer unconditional leakage on all LLM servers |
vLLM CVE-2026-116172 | At least 0.22.0 and below 0.24.0, EngineCore shutdown through candidate-count validation bypass in the Rust gRPC frontend | This fix is 0.24.0. REST validation alone does not establish protection for gRPC. | Developer |
vLLM CVE-2026-116179 / -116180 | Shared engine DoS via request overrides of video frame counts (from 0.18.0) or logprobs for prefixes cached by a connector | 0.31.0 and later. Check conditions involving video APIs, KV connectors, and shared tenants | Video / logprobs. Updating to 0.24.0 alone does not address every vLLM issue. |
Firecrawl / CVE-2026-116066 | SSRF proxy in the Playwright service. Because DNS is resolved separately during validation and the actual connection, a party controlling DNS for the scrape destination can switch it to an internal address. Not all scraping engines use the same implementation | The CNA lists Below 2.11.586. The primary Issue explains the vulnerable commit and independent DNS resolution. Verify that the deployed image and Playwright service include the fixing commit, and restrict egress to internal and metadata destinations. Version boundaries are stated by the CNA; release notes have not been independently confirmed in this retrieval. | Developer issue #5256、Fix commit、GHSA NVD listing: 10/25 12:16:27.370 UTC. |
Paisa / CVE-2026-116067 | Path escape in ledger / sheet APIs, retrieval of server-readable files, and backup deletion.Default user_accounts No authentication required when unset. When configured, authenticated users are affected | 0.7.8. The developer release explicitly fixes reads outside the directory and backup deletion. Restrict API exposure and check access evidence and deleted backups. | Official release、Developer issue #420、GHSA NVD inclusion: 10/25 12:16:28.997 UTC. |
Dokploy / CVE-2026-116068 | An owner/admin in their own organization can specify another organization's applicationId to reach operations involving environment variables, deployment, shutdown, and more.owner/admin does not mean administrator privileges over the entire affected instance | The CNA lists Through 0.30.10. The official 10/22 PR #5752 merged the organization-boundary validation fix into canary. The minimum stable version is not established here. Verify that the distribution used contains the commit, and investigate operations against other organizations' IDs and changes to environment variables or build settings. | Official PR、Developer issue、GHSA NVD listing: 10/25 12:16:29.153 UTC. |
rotki / CVE-2026-116071 | If a premium synchronized backup was obtained, weak key derivation in the old format may allow offline guessing. Exchange API keys and other data in the backup are affected. This does not mean key leakage has been confirmed for all users | The CNA lists Below 1.44.2. Developer PR #13401 explains migration to Argon2id and authenticated chunk encryption, compatibility for restoring the old format, and older devices' inability to use the new format. Update all synchronized devices and generate backups in the new format. Updates cannot erase previously obtained old backups; revoke embedded credentials if acquisition is suspected. | Official PR、Official 1.44.2、GHSA NVD listing: 10/25 12:16:29.623 UTC. |
The vLLM Nemotron-VL entry has conflicting affected starting versions.Check the processors and input paths in use, image limits, and additional distributor guidance. Updating to 0.24.0 alone does not mean all vLLM issues are addressed.Developer
Maintain ongoing responses
| Responsible area | Actions to continue tonight | Details |
|---|---|---|
| Public PHP / GitLab | Fixes for 4 PHP series and mitigation of the separate upload progress issue; investigate back to at least 10/17. Compare GitLab series-specific fixed versions with running versions | PHP / Subsequent PHP releases / GitLab |
| Actively exploited devices and services | Arista VCO / Nextcloud Built-in CODE / Plex / SiteGuard and others. Restrict public access and investigate compromise after updating. Do not treat KEV's US federal deadlines as legal deadlines for everyone. | 10/24 broad review / Plex |
| Fortinet | Do not postpone hardening until individual CVE details are published. Check update targets for 5 products including FortiOS by model, branch, and upgrade path. | Branch-specific table |
| Java / Python / Certificates | Check eMudhra mitigations through application-bundled JREs, certifi, OS stores, and actual TLS usage. Do not mislabel affected versions in public tables as fixed versions | Previous / CA |
| Brotli / Node / Bun / Envoy / Istio | Check malicious-input decompression paths, automatic response decompression, static linking, wheels, and containers. Changing Accept-Encoding alone is insufficient. | HTTP2Shell details |
| DNS / proxy / OT | Product-specific fixes for BIND, Unbound, PowerDNS, and Knot. Unfixed exceptions in ATS 9.2.16. open62541 also affects clients | 16 product groups |
| CI / AI / cloud credentials | Affected LiteLLM wheels and containers, Railway environment variables, and added M365 permissions. Redistribution or deletion does not constitute key revocation. | LiteLLM / One week |
| kernel / container | Verify distribution fixes, host restarts, and the running kernel. Application updates cannot fix a shared kernel. | Infinity Core |
| Japanese business operations / APIs | JPCERT10/23 update, Pleasanter LDAP, public management interfaces, payment APIs, leaked keys, and more. Do not infer attribution or compromise solely from IPs or headlines. | JPCERT / JVN |
Counts and the scope visible to us
| Source | Scope retrieved this time |
|---|---|
| NVD published | 10/25 07:34:00–14:18:00 UTC, 87 entries. Verify all severities, returned total and counts, and date/time ranges across all rows |
| NVD modified | Within the same fixed window,87 records. The CVE set matches this run's published set.Do not count them as 174 records |
| GitHub Advisory API | New publications in the same window16 records, all unreviewed, package fields empty. Not a complete list of developer advisory updates. |
| Developer GHSA | Separately retrieved 12 existing advisories for Snipe-IT, Parse Server, YesWiki, rclone, and vLLM from NVD references. They were readable through repository-specific APIs even when the overall API returned 404. Do not infer withdrawal |
| CISA KEV | CISA official GitHub mirror 2026.10.23 edition, 1,756 entries. Supplement restricted retrieval from CISA itself with the official mirror. Not listed ≠ not exploited. |
| Feeds | Of 14 primary/research sources, 2 secondary news sources, and 1 JVN source,17 successful retrievals. Does not cover items outside short feed display ranges or undated articles. Secondary sources are entry points for finding primary sources |
| IPA / Reddit API | IPA's old URL returned 404 and Reddit JSON returned 403; both recorded. IPA isOfficial indexto reconfirm the PHP10/22 listing. Reddit text checked through a separate web retrieval. Retrieval failure does not mean “no issues.” |
The 87 new and 87 updated entries are the same CVE set this time. They cannot be added as 174 entries. Absence from a database is not proof of no harm. Record later-retrieved text, feed coverage, and uncertainties; treat secondary reporting as a starting point for finding primary information.