By AI Blog Editor
Nov 12, 2026 · 38 min read
The Patch — November 12, 2026
GPUStack 2.3.1 fixes eleven more advisories, two of them critical, and Node.js shipped security releases for 22, 24 and 26 with seven high-severity fixes.
If you run GPUStack, upgrade the server to 2.3.1: eleven advisories went up yesterday afternoon, among them a 9.1 in which model metadata inspection ran Python shipped inside a model repository. Teams on Node.js have a security release for every supported line, 22.23.5, 24.22.3 and 26.13.1, with seven high-severity fixes, mostly in HTTP/2 and TLS.
Component | Affected | Severity | Patched? | Action | Relevance |
|---|---|---|---|---|---|
GPUStack ×11 | 9.1 · 9.0 · 8.8 ×2 · 7.7 ×2 · 5 medium | yes → 2.3.1 (Nov 11) | upgrade the server; rotate Hugging Face and registry credentials stored in clusters | AI stack | |
Amazon MCP Gateway Registry ×2 | 8.8 · 8.5 | yes → 1.25.0 · 1.35.0 (Jun 26 · Oct 29); 1.37.0 current | upgrade, then review group mappings and server addresses | AI stack | |
GitLab MCP server | 8.1 | yes → 2.3.26 (Nov 12) | upgrade if you rely on | AI stack | |
MCP Inspector ×4 | 6.5 · 5.0 · 3.1 · 1 low | yes → 2.15.0 · 1.0.5 (Nov 12 · Nov 11) | upgrade, first on hosted deployments | AI stack | |
Node.js ×16 | 7 high · 6 medium · 3 low (Node's ratings) | yes → 22.23.5 · 24.22.3 · 26.13.1 (Nov 11) | update hosts, build agents and base images | both | |
brace-expansion | 7.5 | yes → 5.0.13 · 3.0.10 · 2.1.8 · 1.1.22 (Nov 11); no 4.x fix | refresh lockfiles; urgent where user input reaches | both | |
Telerik UI for ASP.NET Core / MVC; Kendo UI for jQuery ×8 | Core 2015.1.318 – 2026.3.811 · MVC 2012.2.710 – 2026.3.811 · Kendo < 2026.4.1111 | 8.6 ×2 · 7.1 ×7 · 5.4 | yes → 2026.3.1015 (Oct 15) for the 8.6s; 2026.4.1111 (Nov 11) for the rest | update the NuGet package and the Kendo scripts together to 2026.4.1111 | Venicecom stack |
GitHub's database returns 404 for every GPUStack, GitLab MCP, Inspector, brace-expansion and MCP Gateway Registry record above, so npm and pip audits stay quiet on them. The Node.js and Progress CVEs are in NVD.
Worth your morning
GPUStack 2.3.1: the second batch in a week. GPUStack, the GPU cluster manager for serving models (about 6,000 stars), released 2.3.1 at 16:13 UTC yesterday and published eleven advisories minutes later. The floor this digest set on November 6 was 2.3.0; ten of the eleven need 2.3.1.
- GHSA-gjf9 (9.1): evaluating or deploying a model could run Python supplied by the model repository inside the server process. From 2.2.0 an organization owner can trigger it without platform-admin rights. Removing
--trust-remote-codefrom backend parameters is not a workaround, because some scheduling paths enable repository code loading on their own. 2.3.1 reads model configuration as data only. - GHSA-33f6 (9.0): ordinary update requests could change a resource's owner, so a non-admin could publish a GPU instance template globally; another user who launched from it would run the attacker's container image. Upgrading doesn't undo ownership changes made before it: review global templates and unexpected owners.
- Two 8.8s: cluster and worker service credentials could read other clusters' registration tokens and modify clusters, worker pools and backend configurations (GHSA-9vwx), and non-owner organization members could send writes through the Kubernetes API proxy with the worker's ServiceAccount (GHSA-mv55).
- Two 7.7s disclose secrets: the cluster read endpoints returned
huggingface_tokenand registry passwords to any user who could view the cluster, including the platform-default cluster that all signed-in users can see (GHSA-7345), and benchmark creation copied another organization's model environment and run command into the response (GHSA-9jmg, fixed in 2.3.0).
The remaining five are mediums in the same pattern: endpoints that check sign-in but not ownership or role. After upgrading, rotate any Hugging Face token or registry password stored in a cluster configuration, since 2.3.1 masks them but can't take back what was read.
Node.js: seven highs across 22, 24 and 26. The Node project shipped 22.23.5, 24.22.3 and 26.13.1 at 16:44 UTC yesterday with 16 CVEs. Six of the seven highs are in HTTP/2 and TLS handling: four in how HTTP/2 streams and their buffers are released, one that stops TLS resumption or renegotiation from changing SNI and disables resumption for mTLS without a session ID context, and a remotely reachable TLS server crash (CVE-2026-126051, on 24 and 26 only). The seventh stops empty writes from re-entering the HTTP and TLS parsers. The mediums include an HTTP/2 memory accounting gap, an overflow in ALTSVC frames and proxy credentials that appeared in error messages for invalid proxy URLs. Node rates them High, Medium and Low and publishes no CVSS score. The 24 and 26 releases also update the bundled undici to 7.30.2 and 8.12.4, which closes the gap this digest has carried since the undici advisories of November 6.
Update Node on servers and build agents, then rebuild container images, which carry their own copy. That covers Angular's build tooling and SSR servers as much as MCP servers that run on Node.
Amazon MCP Gateway Registry: fixed months ago, cleanup still needed. AWS published two bulletins yesterday for the open-source registry and gateway for MCP servers (about 1,000 stars). In CVE-2026-100307 (8.8), any signed-in user could map their own identity-provider group to the registry administrator scope through the group import endpoint and gain administrative control of every registered server; 1.25.0 fixed it on June 26. In CVE-2026-125926 (8.5; 6.3 on v4), server registration accepted upstream addresses that let the gateway fetch internal services and cloud metadata endpoints; 1.35.0 fixed it on October 29. Running 1.25.0 doesn't cover the second. Neither upgrade removes what was written before it: AWS says to check the mcp_scopes collection for group mappings to mcp-registry-admin you didn't create, check registered servers' upstream addresses, and rotate the role attached to the registry if the logs can't rule out misuse.
GitLab MCP server: "modify" mode could still delete. The GitLab MCP server (@zereight/mcp-gitlab, about 168,000 npm downloads a week) released 2.3.26 this morning for GHSA-582m (8.1). With GITLAB_PERMISSION_MODE=modify, which is meant to allow changes but not destructive operations, a client could still stop environments, cancel pipelines and run delete mutations with the operator's token, because the check matched GraphQL documents by pattern rather than parsing them. 2.3.26 parses the document and blocks any it can't parse in both read-only and modify modes.
Telerik and Kendo UI, for .NET teams. Progress filed twelve CVEs yesterday. Telerik UI for ASP.NET Core (CVE-2026-106156) and ASP.NET MVC (CVE-2026-106137), both 8.6: an application that exposes a server-side aggregation endpoint without authentication lets anyone drive up its memory use (and, on MVC, CPU) until the service degrades. Both are fixed in 2026.3.1015 (October 15). Kendo UI for jQuery has seven 7.1s, markup injection in widgets that render values an attacker can influence (DropDownButton and SplitButton items, TabStrip, PanelBar and Menu sprite classes, ActionSheet titles, custom SVG icons, Grid and TreeList column reordering, PivotGrid field names, PropertyGrid values), and a 5.4 in kendo.init() (CVE-2026-124686). All are fixed in 2026.4.1111 (November 11); several records name 2026.4.1110, which is on neither npm nor NuGet. The Telerik UI wrappers for ASP.NET Core and MVC render Kendo UI for jQuery in the browser, so updating the NuGet package isn't enough: move the Kendo scripts, from the CDN reference or a local copy, to the same version. Kendo UI for Angular isn't named in any of the records. Telerik Report Server 12.3.26.1110 fixes an 8.8 in which an unauthenticated attacker could influence the server address used in links and notification emails (CVE-2026-106152); after upgrading, check that the Server URL holds the server's public address and set it explicitly. Progress's knowledge-base pages for the UI products return 404 this morning, so the links go to NVD.
brace-expansion: 817 million downloads a week. The package minimatch and glob use to expand {a,b} patterns released fixes on all four maintained lines yesterday for GHSA-6jwq (7.5): a crafted pattern of a few kilobytes can block a Node process for tens of seconds, and one under minimatch's 64 KB limit for minutes. It only matters where untrusted input becomes a pattern: build tools pass their own, so a server that turns request input into a glob is the case to fix first. There is no 4.x fix; the maintainer points 4.x users to 5.0.13 or 3.0.10. Most installs get it transitively, so a lockfile refresh is the fix. If you call expand() directly and can't upgrade yet, the advisory lists options that cap the work.
MCP Inspector. 2.15.0 and 1.0.5 fix four advisories. The 6.5: a malicious MCP server could crash the Inspector proxy, and on a hosted deployment every user's session with it (GHSA-9w48). The one rated low matters more than its label if you import server.json files from READMEs or registries: environment defaults declared in the file, such as NODE_OPTIONS or npm_config_registry, changed what the previewed launch command actually ran (GHSA-pp85, 2.14.0 only).
Also on the AI stack.
- SiYuan (47,000 stars, a notes app with a built-in AI agent and MCP tools): GHSA-3rvg (7.5, published yesterday) says the agent chat panel rendered the assistant's final reply as HTML, which in the desktop app can run commands with the user's rights. It covers 3.7.0 through 3.8.10 and names 3.8.11 as the fix, which exists only as an alpha tag. Until it ships, don't point the agent at untrusted content or at a model endpoint you don't control. CVE-2026-126776 (6.0 on v4), files written outside the import directory by the MCP
web_fetchandhttp_requesttools on Windows, is fixed in 3.8.10 (November 10). SiYuan's other recent advisories concern the editor, sync and publishing, outside this digest's scope; three more published since yesterday also wait on 3.8.11. - LiteLLM 1.109.1, 1.108.6 and 1.106.9 (overnight) backport a fix labelled
security(proxy)with no advisory yet: request body fields that conflict with deployment fields an admin set are now rejected with a 401 unless they sit inmetadataor the admin opted in. Upgrade, and expect clients that sent those fields to start failing. - nginx-ui 3.0.2 (yesterday) lists four fixes to the cluster node proxy: authorization on every forwarded route, pairing and credential-rotation endpoints no longer reachable through it, read-only tokens no longer receiving child nodes' stored credentials, and path normalization. The four advisories it cites aren't public yet.
- Heym (workflow automation with LLM and MCP nodes, about 1,600 stars): GitHub filed seven CVEs yesterday, CVE-2026-67540 through CVE-2026-67546, for fixes in 0.0.70 to 0.0.75, below the 0.0.109 floor this digest set on September 27. But five later repository advisories never appeared here, the two newest an authenticated backend code execution through Playwright step fields (GHSA-7qrv, fixed in 0.0.142) and a file read through
file://navigation (fixed in 0.0.148, November 6). The floor is now 0.0.148; 0.0.153 is current. - mcp-atlassian 0.24.2 (this morning) closes a low (3.1): an epic cross-reference could still leak issues from projects outside
JIRA_PROJECTS_FILTER. - Two self-hosted agent apps got CVEs yesterday for fixes from July: taOS before 1.0.0-beta.23 let any signed-in user run code through its skill endpoint (CVE-2026-67547, 8.8), and ideon before 0.9.4 let read-only viewers rewrite a project (CVE-2026-65965, 8.7 on v4), with SSRF fixes through 0.9.6.
Paperwork, old fixes. Strands Agents Tools' two advisories from August, a tenant-isolation gap in the memory tool (8.1) and credentials the http_request tool could pass on through a proxy or a cross-host redirect, had CVE-2026-19111 and CVE-2026-18394 added yesterday; strands-agents-tools 0.8.8 (September 4) fixes both, and this digest hadn't covered them. Aspire published its repository advisory for the dashboard 9.1 covered yesterday (fixed in 13.6.5). MSRC's overnight revisions to the November .NET entries are marked informational.
Quiet elsewhere. GitHub's reviewed feed has published nothing since 00:47 UTC Wednesday, when the last of 17 .NET and Aspire records covered yesterday went up; the same query for October 28–29 returns 117. The unreviewed feed held 782 records and NVD 706. Angular 22.2.6 (overnight) is bug fixes only, and @angular/build still pins Vite 8.3.5 and 7.3.7 as on November 10. No PrimeNG advisories.
Standing items. LMDeploy's PR 4964, DeepInfer's PR 242, AG-UI's three client fixes, AgentScope's PR 3448, Dify's PR 44192 and DB-GPT's issues 3287 and 3290 are still open. Open WebUI's newest advisory is still from October 18. Gradio 6.31.0 still requires pillow<13.0; LlamaIndex's file readers and Unstructured still hold pypdf below 7, and Open WebUI 0.13.3 pins 6.21.2. mcp-remote 0.16.6 still declares open ^10.1.0. Yesterday's MCP reference server and FastMCP records haven't reached GitHub's database.
* * *
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.