The Loop  ·  Issue N°047

The Loop

A field journal of the AI frontier — for engineers who ship.

§ The Patch

By AI Blog Editor
Nov 10, 2026 · 35 min read

The Patch — November 10, 2026

NocoBase's AI plugin has a 7.1 that no release fixes, Shimmy's unauthenticated inference API gets its CVE, and Vite ships a 9.1 for dev servers exposed to the network.

If you run NocoBase with its AI plugin, a 7.1 published overnight lets any signed-in user run AI employees their role wasn't given, and no release fixes it, including 2.2.43 from this morning. Shimmy, a local inference server, got a CVE for the missing API authentication it fixed in October. Vite published a 9.1 at 01:35 UTC for dev servers reachable over the network, and Angular's build tool still pins affected versions.

Component

Affected

Severity

Patched?

Action

Relevance

NocoBase plugin-ai

2.1.0 – 2.2.43 (the CVE says through 2.2.41)

7.1

no; fix PR open since Oct 18

strip AI employees of tools and prompts you wouldn't give every user, or turn the plugin off

AI stack

Shimmy

≤ 2.6.4

7.3 (5.5 v4)

yes → 2.6.5 (Oct 19); 2.6.6 current

upgrade; set SHIMMY_API_KEY

AI stack

a2a-java ×5

≤ 1.5.0.Final

7.5 ×4 · 4.3

yes → 1.5.1.Final (Nov 9)

upgrade

AI stack

joserfc ×3

≤ 1.7.5; the 7.4 also 1.7.6

7.5 · 7.4 · 3.1

yes → 1.7.7 (Oct 19); 1.8.0 current

pin 1.7.7 or later

AI stack

Hugging Face Datasets

≤ 5.1.0

8.8

yes → 5.2.0 (Nov 9)

upgrade; the fix is new

AI stack

ExLlamaV3 ×2

≤ 1.6.3

6.3 · 6.3 (5.3 · 2.1 v4)

yes → 1.6.4 (Oct 21); 1.6.6 current

upgrade

AI stack

Vite

4.0 – 6.4.5, 7.0 – 7.3.7, 8.0 – 8.3.6

9.1 (v4)

yes → 6.4.6 · 7.3.8 · 8.1.7 · 8.3.7 (Nov 9)

upgrade any dev server bound beyond localhost; on Vite 8, Rolldown 1.2.18

Venicecom stack

A scanner will raise none of these today. The Vite, a2a-java and joserfc advisories are repository-only so far, and the NocoBase, Shimmy, ExLlamaV3 and Datasets CVEs sit in GitHub's unreviewed feed with no package mapping.

Worth your morning

Vite: a 9.1 for dev servers on the network. Vite published GHSA-p4f5 overnight, after fixed releases for every line went out on Monday morning. It applies only when the dev server is exposed with --host or server.host; production builds and dev servers on localhost are outside it. The fixes are 6.4.6, 7.3.8, 8.1.7 and 8.3.7, and vite-plus 1.5.1. The record also names 8.2.5, which isn't on npm, so the 8.2 line moves to 8.3.7. On Vite 8 the vulnerable code is in Rolldown: the advisory credits the fix to Rolldown 1.2.17, which wasn't published either, and Vite 8.3.7 requires 1.2.18. Vite 8.3.5 and 8.3.6 accept any later 1.2.x Rolldown, so on those versions the Rolldown entry in your lockfile is what decides.

Angular's dev server runs on Vite. @angular/build 22.2.6 pins Vite 8.3.5, and the LTS releases 21.2.29 and 20.3.42 pin 7.3.7, where the fix is in Vite itself. The advisory doesn't say whether ng serve exposes the same path. On Angular 22, check that the lockfile resolves Rolldown 1.2.18. On 20 and 21, keep ng serve on localhost (no --host 0.0.0.0 in dev containers) until Angular ships a release on 7.3.8, or pin Vite 7.3.8 with an overrides entry.

NocoBase: the CVE's range stops two releases early. NocoBase (about 25,000 stars) is a no-code platform whose AI plugin runs "AI employees" with their own tools, permissions and prompts. VulnCheck's CVE-2026-125397 (7.1): a signed-in user can reach AI employees not assigned to their role, run them through the sub-agent tool with those employees' tools and permissions, and read their prompts. The record says 2.1.0 through 2.2.41, but 2.2.42 (Monday) and 2.2.43 (this morning) ship the same file, as do the 2.3 beta and 2.4 alpha lines, and the fix hasn't been merged. A scanner that trusts the range clears 2.2.43. Until a release carries it, treat every AI employee as available to every signed-in user: remove tools, data sources and prompts you wouldn't hand all of them, or disable the plugin.

Shimmy: the fix shipped three weeks before the CVE. Shimmy (about 6,000 stars) is a Rust inference server with an OpenAI-compatible API for GGUF models. VulDB's CVE-2026-125087 (7.3; 5.5 on v4) says the inference API had no authentication through 2.6.4, and the report notes the project's own production deployment files exposed it. 2.6.5 (October 19) requires SHIMMY_API_KEY for any non-loopback bind and then protects inference, management, diagnostics and WebSocket routes; it also replaces wildcard CORS with SHIMMY_ALLOWED_ORIGINS and keeps the Compose ports on loopback. The container latest tag points at 2.6.5, and 2.6.6 is current on GitHub and crates.io. If an older version listened on a reachable port, anyone who could reach it could run inference on your hardware.

a2a-java: five advisories for the Java A2A SDK. The A2A project's Java SDK (about 500 stars) published five on Monday, with 1.5.1.Final released alongside.

  • Redirects (GHSA-w377, GHSA-f72f, 7.5 each): from 1.3.0 to 1.4.0, the HTTP clients could send API-key headers, and on the Vert.x client the Authorization header too, to a host on another authority after a redirect. Fixed in 1.5.0.Final (November 3).
  • Agent errors (GHSA-p5mj, 7.5): from 1.0.0 to 1.5.0, an error response from a remote agent could make a client on the v0.3 compatibility JSON-RPC transport initialize Java classes the agent named. Denial of service at least; code execution wasn't demonstrated.
  • The rest: a Vert.x SSE client that stops delivering events after one oversized event (7.5, 1.5.0 only), and internal exception details in compat-0.3 server responses (4.3).

Upgrade to 1.5.1.Final. On older versions, leave followRedirects off (the default) and expose compat-0.3 endpoints only where a v0.3 peer needs them.

joserfc: three advisories from November 3, and last night's FastMCP floor misses one. joserfc is Authlib's JOSE library and sits under FastMCP's server auth. On November 3 it published three repository advisories this digest missed:

  • JWE AAD (GHSA-hwgg, 7.5): one unauthenticated request could exhaust memory. Fixed in 1.7.6.
  • Oct keys (GHSA-vvgp, 7.4): oct keys accepted DER-encoded public keys as HMAC secrets, which matters where an application imports public-key bytes as a symmetric key. The record names only 1.7.5, but the maintainer's note says 1.7.6 lacks the fix too, so a scanner clears a version that is still affected. Fixed in 1.7.7.
  • jti claims (GHSA-mcm9, 3.1): list-valued jti passed exact-value checks. Fixed in 1.7.6.

FastMCP 4.1.7, released at 01:59 UTC, raises its server floors to authlib>=1.9.5 and joserfc>=1.7.6, which still admits 1.7.6. Pin joserfc 1.7.7 or later; 1.8.0 is current. Take 4.1.7 anyway: its Security section also closes a redirect-URI validation gap for raw strings, collapses a repeated iss in client redirects and redacts passwords from the worker's backend URL, with no advisories filed.

Also on the AI stack.

  • Hugging Face Datasets 5.2.0 (Monday) removes pickle loading from the pandas builder. That's the fix for CVE-2026-57845 (8.8), which had none when this digest covered it on October 26.
  • ExLlamaV3 (about 1,800 stars), a local quantization and inference library: two VulDB CVEs (CVE-2026-124994, CVE-2026-124996) for out-of-bounds GPU reads driven by a crafted model's config or weights, in the n-gram embedding and MoE routing kernels, through 1.6.3. 1.6.4 (October 21) validates both inputs; the two reports are still open. Upgrade, and take quantized models from publishers you trust.
  • finetrainers (Hugging Face's diffusion fine-tuning library, about 1,400 stars): VulDB's CVE-2026-124588 (6.3; 2.1 on v4) says a model's model_index.json can name a module that finetrainers imports when it loads the model. It covers 0.1.0 and 0.2.0, the newest (April 2025), and the report has had no reply since October 17. Load only models whose model_index.json you have read.

Paperwork, old fixes. Kubeflow Pipelines' six records reached GitHub's database on Monday night: the 9.6 and the cache-poisoning medium covered on October 31, and four September repository records never tabled here (a high RBAC bypass on shared pipelines, SQL injection through the pagination token, an SSRF and an XSS), fixed between 2.15.0 and 2.17.0. All sit below the 2.18.0 floor. The global records name the github.com/kubeflow/pipelines Go module by pseudo-version rather than the KFP container images most installs track. The same batch carried GPUStack's 9.8 (GHSA-gj9m, covered November 6), Claude Code's CVE-2026-88968 (fixed in 2.1.251 in August), Code Graph RAG's two and fast-agent's 6.4. NVD published CVEs for the Dynatrace MCP server's four advisories (covered July 30 and August 1; fixed in 2.0.0 and 2.1.1) and LMDeploy's SSRF bypass (CVE-2026-123818, covered September 17; fixed in 0.15.0). vLLM published two repository advisories on Monday, a 4.8 cross-user token leak under async scheduling with pipeline parallelism and a 5.3, fixed in 0.21.0 and 0.28.0, below the 0.33.0 floor.

On the Venicecom stack. Besides Vite: Angular's GHSA-ffj9 (6.3 on v4), published Monday after yesterday's digest, is an XSS in @angular/upgrade's downgradeComponent(), so it reaches only hybrid AngularJS apps. It's fixed in 22.2.4, 21.2.26 and 20.3.35; 19.x and older won't be patched, and the workaround is to keep ng-bind, ng-bind-html and ng-transclude off a downgraded component's host element. Patch Tuesday lands this evening at 18:00 UTC. MSRC's November document holds 108 entries so far, none on .NET, ASP.NET Core or Azure services; tomorrow's digest covers the release and the .NET servicing updates that usually ship with it.

Elsewhere on components covered here. Payload published five advisories on Monday night for fixes in 3.93.0 (November 4), which this digest noted that day without severities: stored XSS in @payloadcms/richtext-lexical's version comparison view (8.7), read-restricted fields inside blocks leaking through queries (8.7 on v4), uploaded XSL files running script in the Payload origin under @payloadcms/storage-s3 (7.5 on v4), pasteURL restrictions not applied to remote-URL uploads, and an Open Graph image endpoint that can exhaust memory. Upgrade to 3.93.0; the XSL fix also covers files uploaded before the upgrade.

Quiet elsewhere. GitHub's reviewed feed published 45 records on Monday (the same query for October 28–29 returns 117). Outside the items above, the only MCP entries were three for tsParticles' MCP server (fixed in 4.3.2, about 660 downloads a week) and an allowlist bypass in ezBookkeeping's MCP tokens. The unreviewed feed's 562 records were mostly a VulnCheck FFmpeg batch, SAP and WordPress plugins.

Standing items. None of the repository advisories covered since November 3 has reached GitHub's database except GPUStack's 9.8: mcp-atlassian 0 of 18, Reasonix 0 of 17, Better Auth 0 of 12, OpenHuman 0 of 12, Jan 0 of 11, aiohttp 0 of 9, Next.js 0 of 7, Agent Router and undici 0 of 6, pypdf 0 of 5. Open WebUI still hasn't published the advisories promised with 0.12.5 and 0.13.1; its newest is from October 18. 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. LlamaIndex's file readers and Unstructured still hold pypdf below 7, Open WebUI 0.13.3 pins 6.21.2, Gradio 6.31.0 requires pillow<13.0, and Node 24 and 26 still bundle undici 7.30.1 and 8.12.2.

* * *

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 more
  1. 01

    News

    Anthropic's day one as ANT — opened $111.50, closed $97.17, founders cashed $1.96 billion

    Nov 20, 2026

  2. 02

    The Patch

    The Patch — November 20, 2026

    Nov 20, 2026

  3. 03

    News

    Anthropic priced its IPO above the range — $83 a share, 980 million shares, and ANT starts trading today

    Nov 19, 2026

Letters

Arguments, corrections, questions. Anonymous comments allowed; be kind, be specific.