By AI Blog Editor
Nov 19, 2026 · 32 min read
The Patch — November 19, 2026
LMCache published a 9.8 for its multiprocess mode and Kubeflow Pipelines five fixes headed by a 9.8 in 2.18.1, while nginx 1.31.9 and 1.30.7 close ten CVEs, three rated major.
Two pieces of AI serving infrastructure published fixes overnight. LMCache, the KV-cache layer many vLLM and SGLang deployments run beside the engine, disclosed an unauthenticated 9.8 in its multiprocess mode. Kubeflow Pipelines 2.18.1 fixes five flaws, the worst a 9.8 that lets a caller run code in the shared visualization service. And if anything you run sits behind nginx, which is most things, nginx 1.31.9 and 1.30.7 fix ten CVEs.
Component | Affected | Severity | Patched? | Action | Relevance |
|---|---|---|---|---|---|
LMCache ×4 | 9.8 · 2 high · medium | yes → 0.5.7.post1 (Nov 12) | upgrade; keep the cache ports off shared networks | AI stack | |
Kubeflow Pipelines ×5 | 9.8 · 8.8 · 8.1 · 7.8 · 6.5 | yes → 2.18.1 (Nov 18) | upgrade server images and the | AI stack | |
nginx ×10 | 3 major · 8.1 (9.2 v4) | yes → 1.31.9 / 1.30.7 (Nov 18) | upgrade; check what your distro and images ship | both | |
SiYuan ×5 | 9.0 · 8.8 · 3 medium | no; 3.8.11 is at rc.3 | don't import | AI stack | |
OpenClaw | 8.8 | yes → 2026.10.33 / 2026.11.4 | upgrade; current is 2026.11.5 | AI stack | |
soupsieve | 7.5 | yes → 4.1.2 (Nov 18) | refresh lockfiles | AI stack | |
Supergateway (2nd CVE) | 8.1 · 8.6 (v4) | no; 4.2.2 is the newest | don't run WebSocket mode where a browser can reach it | AI stack | |
SGLang | 7.5 · 8.7 (v4) | on | keep the HTTP server off untrusted networks | AI stack | |
@pnpm/exe | medium (GitHub) · 9.8 (VulnCheck) | yes → 10.34.8 / 11.28.8 (Oct 22) | upgrade; | Venicecom stack |
None of these rows is in GitHub's reviewed database yet, so pip-audit and npm audit won't raise them this morning. nginx isn't a package-manager dependency, so no scanner raises it.
Worth your morning
LMCache: a 9.8 in multiprocess mode. GHSA-qr43 says the ZeroMQ socket that distributed and multiprocess deployments open has no authentication, and one operation on it deserializes whatever bytes it receives. A peer that can reach the port can run code on the cache host. It covers 0.4.6 to before 0.5.7, and the advisory notes the fix for an earlier, similar record (CVE-2026-105192) doesn't close this one. The other three are in the legacy in-process server: unauthenticated clients can overwrite cached KV entries and change other users' model output (high), a crafted message length can exhaust server threads (high), and a hostile resp:// endpoint can exhaust client memory (medium). PyPI has no plain 0.5.7; the fixed build is 0.5.7.post1 from November 12, which pip install -U lmcache picks up. Bind the cache to localhost or a private interface either way, since the advisory's fix for the legacy server is to move to multiprocess mode.
Kubeflow Pipelines 2.18.1: upgrade the cluster and the SDK separately. In multi-user installs through 2.18.0, a request with an empty namespace skipped authorization and could run supplied Python in the shared visualization service (GHSA-w9j6, 9.8). A related 8.8 lets a signed-in user do the same through the source parameter. In 2.18.0, the frontend's ML Metadata proxy and the supplied gateway route let one tenant read and change other namespaces' metadata (8.1). The upgrade has to cover the API server, frontend and visualization images on every replica, plus the updated multi-user gateway manifests. Two more fixes are in the kfp Python SDK, which a server upgrade doesn't touch: the local condition evaluator could run code from a task's output (7.8, 2.16.0 onward), and the SDK could send a Google access token to an endpoint that only looked like a Google inverse proxy (6.5). Upgrade kfp to 2.18.1 wherever pipelines are compiled or run locally.
nginx: ten CVEs, three of them major. nginx 1.31.9 (mainline) and 1.30.7 (stable) shipped yesterday. The three nginx rates major are memory corruption in HTTP/2 flow control (CVE-2026-123007), an infinite loop reading a request body over TLS 1.3 (CVE-2026-118899) and a use-after-free in the mail proxy (CVE-2026-113425). F5 scores its five CVEs 8.1 on v3.1 and 9.2 on v4. The others cover HTTP/2 and HTTP/3 use-after-frees when worker connections run short, the resolver directive, alias with try_files, and the stream module. Nearly every self-hosted model server, gateway and Angular front end runs behind nginx, so this is the row with the widest reach. Distribution packages and base images will lag the upstream release: one MCP gateway's release notes say outright that its image still ships the unfixed Debian build. Check the version inside each container, not only on the host.
SiYuan: a 9.0 and an 8.8 with no stable fix. Two stored-XSS records published yesterday name 3.8.10 and 3.8.11-beta.3, and 3.8.11 is still a pre-release (rc.3, last night). The 9.0 runs script from an asset filename in the asset picker; the 8.8 does it from a custom attribute name carried in an imported .sy.zip. The desktop client runs with Node integration, so script there reaches the machine. Until 3.8.11 ships, import notebooks and sync only from sources you control. Separately, VulnCheck filed six CVEs for fixes that 3.8.10 already carries.
OpenClaw: a restricted agent could turn on command execution. GHSA-pw3x (8.8, published at 02:01 UTC today) covers OpenClaw's delegation tool. An agent whose tool policy denied execution and file writes could still apply persistent configuration changes without approval, including ones that enable host commands. Fixed in 2026.10.33 on the extended-stable line (yesterday) and 2026.11.4 on the current line. OpenClaw sees about 3.1 million npm downloads a week.
Supergateway: a second CVE and still no release. Yesterday's row was a denial of service in SSE mode. CVE-2026-132121 (8.1) adds the WebSocket flaw that issue 378 described: stdio-to-WebSocket mode doesn't check the Origin header, so a web page open in your browser can connect to a gateway bound to localhost. It covers 2.4.0 through 4.2.2, the newest release, and the issue has no maintainer reply. Don't run WebSocket mode on a machine where you browse, or put an authenticating proxy that checks Origin in front of it.
Also on the AI stack.
- SGLang (CVE-2026-127222, 7.5): the endpoint that loads LoRA adapters from tensors didn't require admin authorization, unlike its sibling admin endpoints. The fix makes those endpoints require
--admin-api-keyand is onmainsince November 14; 0.5.23 (November 2) is the newest release and doesn't have it. - @pnpm/exe, the standalone pnpm binary (about 9.2 million npm downloads a week): GHSA-w8f5 from October 30 says the bundled Node.js still trusted the compromised eMudhra intermediates covered on October 21. This digest missed it; VulnCheck's CVE (CVE-2026-130756) arrived yesterday. The npm
latest-10tag still resolves to 10.34.6, so pin 10.34.8 or later explicitly. pnpm installed through Corepack or npm uses your own Node and isn't in scope. - mssql-mcp-core 0.6.0 (GHSA-2m9m, 8.8): SQL injection through table names in the write tools. It reached GitHub's reviewed feed overnight, so
npm auditflags it from today; reader and writer 0.5.0 carry the fix. - MONAI (GHSA-x4pc, high): bundle downloads could write files outside the bundle directory. The record says "≤ 1.5.2, fixed after 1.6.1", but 1.6.0 also lacks the check and 1.6.1 (September 27) already has it. 1.6.2 shipped yesterday.
- pypdf 7.1.1 fixes five medium memory-exhaustion records on crafted PDFs, relevant wherever a RAG pipeline ingests uploaded documents. Trigger.dev 4.8.2 and 4.8.6 fix four mediums, one of which stored the CLI's personal access token world-readable on Linux and macOS.
- Ray 2.58.2 and Bifrost 2.6.0 are dependency-only security releases: aiohttp, Brotli and idna for Ray; Go 1.27.4 and
golang.org/x/netfor Bifrost.
Venicecom stack. @azure/msal-browser 5.30.0 adds a version 2 of its popup-relay protocol and deprecates version 1 "due to security concerns", with no advisory. It's opt-in, so Angular apps on msal-angular keep the old behaviour until you turn it on. Angular 22.3.0 makes i18n attributes use your custom Sanitizer for URLs, also without an advisory; 22.2.7 lists no security fixes. MSRC's only changes were revisions to two QUIC entries.
Paperwork. VulnCheck and GitHub filed CVEs for fixes already covered here: vLLM's three for 0.33.0 (November 3), Obot's four for 0.27.0, Heym, Network-AI, n8n's two from November 15 and A2A Java's three, fixed in 1.5.1.Final. AutoGPT's hardcoded-JWT 10.0 from October 5 now has CVE-2026-130169. GitHub assigned CVEs to old repository advisories this digest never tabled: Todoist's official MCP server (9.3, fixed in 10.3.3 in June; 14.0.5 is current), obsidian-sync-mcp (fixed 0.5.7), k8s-mcp-server (1.1.0), Gortex (0.55.0) and StacklokLabs' sqlite-mcp (0.1.2). If you're on a current release of any of them, there's nothing to do.
Standing items. Dify's PR 44192, LMDeploy's PR 4964, DeepInfer's PR 242 and AgentScope's PR 3448 are still open. ExcelJS, VoAPI and DeepAudit still have no fixed release. MongoDB's Node.js driver still has no 6.x release with the SRV fix.
* * *
Thanks for reading. If a line here was useful — or plainly wrong — the comments are below and the newsletter has your back.
Elsewhere in this issue
3 moreLetters
Arguments, corrections, questions. Anonymous comments allowed; be kind, be specific.