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 13, 2026 · 38 min read

The Patch — November 13, 2026

LiteLLM's advisory for Wednesday's proxy backports says a signed-in user could read the master key, and MongoDB's Node.js driver fixed a 9.1 only on its 7.x line.

If you run the LiteLLM proxy with Azure models, the backports this digest flagged yesterday without an advisory now have one: a 7.7 in which any signed-in user could read the proxy's environment, master key included. Teams using MongoDB as a vector store should check which driver line they're on: the 9.1 fix exists only in 7.8.0 and later, and LangChain's MongoDB integration still requires 6.x.

Component

Affected

Severity

Patched?

Action

Relevance

LiteLLM proxy

< 1.109.1, with Azure models

7.7

yes → 1.109.1 · 1.108.6 · 1.106.9 (Nov 12)

upgrade; rotate master key, database and provider credentials if untrusted users could reach an Azure model

AI stack

MongoDB Node.js driver ×3

SRV 3.3.3 – < 7.8.0, all of 6.x · OIDC 6.7.0 – < 7.9.0 · timeoutMS 6.11.0 – < 6.22.0, 7.x < 7.8.0

9.1 · 8.3 · 5.9 (all v4)

yes → 7.8.0 (Oct 30) · 7.9.0 (Nov 12); timeoutMS also 6.22.0; no 6.x fix for the 9.1

move to 7.9.0 (Node 20.19+); on 6.x, use a mongodb:// host list instead of mongodb+srv://

AI stack

MLflow ×2

< 3.18.0

8.2 · 6.3 (v4)

yes → 3.18.0 (Nov 3)

upgrade; 3.17.x leaves a bypass of the SSRF fix

AI stack

soupsieve ×7

≤ 4.0.1

7.5 ×2 · 6.3 (v4) · 5.3 ×3 · 1 medium

yes → 4.1 (Nov 10); needs Python 3.11.5+

refresh lockfiles where Beautiful Soup selects over fetched or uploaded HTML

AI stack

PapaParse

< 5.7.1

8.7 (v4) · 7.5

yes → 5.7.1 (Nov 11)

upgrade, first where a server parses uploaded CSV

Venicecom stack

Telerik UI for ASP.NET Core / MVC ×2; Kendo UI for jQuery ×5

Core 2015.1.318 – 2026.3.1015 · MVC 2012.2.710 – 2026.3.1015 · Kendo ≤ 2026.3.1015

8.6 ×2 · 7.1 ×5

yes → 2026.4.1111 (Nov 11)

2026.3.1015 is no longer enough: move the NuGet package and the Kendo scripts to 2026.4.1111

Venicecom stack

None of the LiteLLM, MongoDB or MLflow advisories above is in GitHub's reviewed database this morning. It holds two of the seven soupsieve records, which name 4.0.0 and 2.10.0 as fixed, so a scanner reading them clears releases that lack the later fixes. PapaParse's record is in the unreviewed feed only, so npm audit won't raise it yet.

Worth your morning

LiteLLM: the advisory behind Wednesday's backports. Yesterday this digest noted a fix labelled security(proxy) in LiteLLM 1.109.1, 1.108.6 and 1.106.9 with no advisory behind it. GHSA-2rwg (7.7) went up at 09:50 UTC yesterday. The proxy's request-body blocklist didn't cover the Azure Entra ID credential parameters, so a caller's values replaced the credential an Azure deployment would otherwise use. Through that, a low-privilege user could read the proxy's environment variables and the contents of files an environment variable points to: on a typical deployment the database URL, provider API keys and LITELLM_MASTER_KEY, which gives full admin control. It applies only to proxies with at least one azure/ or azure_ai/ model and neither AZURE_API_KEY nor AZURE_OPENAI_API_KEY set. Upgrade, and if users you don't fully trust held keys with access to an Azure model, rotate the master key, the database credentials and the provider keys. Until you can upgrade, the advisory says to block tenant_id, client_id, client_secret, azure_username, azure_password and azure_scope in request bodies at a gateway in front of the proxy.

MongoDB's Node.js driver: a 9.1 with no 6.x fix. MongoDB published two advisories yesterday afternoon alongside 7.9.0. In GHSA-qmhq (9.1 on v4, 7.4 on v3.1), a forged or altered DNS SRV response for a mongodb+srv:// connection string could send the driver's traffic to a host outside the connection string's domain, and TLS doesn't stop it, because the driver checks the certificate against the redirected name. Every release from 3.3.3 to before 7.8.0 is affected, 6.x included, and the only fix is 7.8.0 (October 30). The workaround is a mongodb:// string that lists the hosts, which skips the SRV lookup. The 7.x line needs Node 20.19 or later.

That matters for vector-store users. @langchain/mongodb 1.3.1 requires mongodb ^6.20.0, @llamaindex/mongodb pins 6.21.0 and Mongoose 8 (8.24.9, released yesterday) declares ~6.20.0, so none of them can resolve a fixed driver. Mongoose 9 (~7.8) gets the SRV fix but not 7.9.0. The second advisory, GHSA-c5cf (5.9 on v4, fixed in 7.9.0), affects applications that accept connection strings from less trusted sources and pass an OIDC callback: the callback's bearer token could go to a host outside the allowed list. Refusing connection strings whose authMechanismProperties include ENVIRONMENT avoids it. A third, from November 3, GHSA-77w5 (8.3 on v4), affects only applications that set the experimental timeoutMS: after a timed-out write, a pooled connection could hand one operation another user's data. 6.22.0 and 7.8.0 turn timeoutMS into a no-op.

MLflow: 3.17.0 isn't the floor for the SSRF. On November 4 this digest said 3.17.0 fixed ZDI's 8.2 server-side request forgery in the tracking server (CVE-2026-118628). MLflow's own advisory for it, GHSA-mr9f, published overnight, says 3.18.0 also closes a bypass of that fix through wasbs:// artifact locations, so the floor is 3.18.0 (November 3). A default mlflow server has no authentication, so no credentials are needed. VulnCheck also filed CVE-2026-127202 (6.3 on v4) yesterday, a FileStore path traversal in the log-outputs API that lets an unauthenticated caller write files outside the run directory, fixed in the same release. FileStore has been opt-in through MLFLOW_ALLOW_FILE_STORE since 3.7.0. Keep tracking servers off untrusted networks and turn on authentication.

soupsieve: seven advisories since November 4. soupsieve is the CSS selector engine behind Beautiful Soup's select(), which web loaders and scrapers in RAG pipelines run over pages they fetch. Its maintainer published six advisories on November 4 and one on November 10. They reached this digest only because GitHub reviewed two of them overnight. The one that matters most is GHSA-mmhr (7.5): selectors with a descendant combinator, among the most common there are, can tie up a worker for close to a minute on about 1 KB of HTML that an attacker controls. Two mediums cover :has() matching over untrusted documents. The other 7.5 (GHSA-6655) and three mediums need an attacker-supplied selector, which applies only if your service lets callers send one. 4.1 (November 10) fixes all seven, and needs Python 3.11.5 or later. On Python 3.10 the newest installable release is 2.10, which has neither 7.5 fix. Beautiful Soup requires only soupsieve>=1.6.1, so refreshing the lockfile is enough.

Telerik: 2026.3.1015 no longer covers the server-side 8.6s. Yesterday's row said 2026.3.1015 (October 15) fixes the two 8.6s in Telerik UI for ASP.NET Core and MVC. Progress filed two more 8.6s yesterday that affect 2026.3.1015 itself. On Core, deeply nested filter expressions sent to an endpoint that binds DataSourceRequest can exhaust the stack (CVE-2026-106154); on MVC, crafted filter parameters raise unhandled exceptions (CVE-2026-106146). Both need an endpoint reachable without authentication, and both are fixed in 2026.4.1111 (November 11). Five more Kendo UI for jQuery 7.1s, markup injection through Gantt task titles, Form item hints, Spreadsheet sheet names and Chart tooltips (CVE-2026-124691 and four more), are fixed in the same release, which makes 13 Kendo CVEs this week. Yesterday's action stands, now with no exception for the 8.6s: the NuGet package and the Kendo scripts together, to 2026.4.1111. Progress also fixed Telerik Reporting in 20.3.26.1110: an authenticated user who can put SVG content in a report could read files on the rendering host or make it send requests (CVE-2026-118975, 6.5), and the .NET Framework report designers had a local deserialization flaw (CVE-2026-106140, 7.3). UI for WinForms (2026.4.1111), WPF (2026.4.1110) and .NET MAUI (16.0.0) fix seven 7.8s in expression handling, deserialization and hyperlink handling.

PapaParse. The CSV parser (25 million npm downloads a week) released 5.7.1 on November 11, and VulnCheck filed CVE-2026-127056 (8.7 on v4, 7.5 on v3.1) yesterday: a single-column quoted CSV with no delimiters makes parsing time grow with the square of the input, blocking the Node.js event loop or freezing a browser tab. In a browser, the user mostly freezes their own tab. On a server that runs Papa.parse() on uploads, one file stalls every request, so upgrade server-side code first.

Also on the AI stack.

  • Hono and @hono/node-server, both dependencies of the MCP TypeScript SDK (@modelcontextprotocol/sdk 1.32.2): nine Hono advisories from November 1 and 11, all medium or low, cover middleware that some route patterns, mount() paths and validator content types skip, plus gaps in csrf() and bodyLimit(). Four in the Node adapter cover backslash and // request paths, WebSocket upgrades and serveStatic. Floors: hono 4.13.18 and @hono/node-server 2.1.7, or 1.19.18 on the 1.x line. The SDK declares hono ^4.11.4 and @hono/node-server ^1.19.9 || ^2.0.5, so a lockfile refresh picks up the fixes.
  • pgEdge Postgres MCP Server (about 250 stars): NVD published four CVEs yesterday for fixes in 1.1.0 (September 4), the worst SQL injection through custom pl-do tool arguments (CVE-2026-126197, 8.8) and a bypass of read-only mode (CVE-2026-126196, 8.1). A newer 8.8, GHSA-jf8q (November 11), lets a caller run Perl code in the database through custom pl-do tools written in plperl or plperlu. The advisory says to upgrade to 1.1.1, which would be easier if 1.1.1 existed: the only release since 1.1.0 is 1.2.0-beta1. Until it ships, remove those tools or rewrite them as pl-func tools, which receive their arguments as bind parameters.
  • Heym 0.0.154 (yesterday) fixes two more: an anonymous workflow ran with the credentials of any signed-in user who opened its link, so its author could collect them from run history (GHSA-m2cg, rated low), and HTML output workflows served the author's script from the application's origin (GHSA-hhvf, medium). The floor set yesterday moves from 0.0.148 to 0.0.154.
  • taOS 1.0.0-beta.58: on multi-user installs, any member could read, overwrite and delete files in other users' agent workspaces and export an agent's configuration with its llm_key (GHSA-v258, 8.8), plus a medium on agent and archive ownership. Single-user installs aren't affected.
  • AutoGPT Platform 0.11.2: a crafted CSV referenced in AutoPilot could freeze the process serving that chat and every other chat on it for hours (GHSA-q2g2, medium). Running the backend on Python 3.13.15 or later also avoids it.
  • LobeHub 2.3.3 (yesterday) lists security fixes with no advisory: workflow callbacks now fail closed when unauthenticated, and a run woken by mail is scoped to its own mailbox.
  • nginx-ui published four advisories yesterday for fixes in 2.9.1, among them an unprotected change to the AI assistant's base URL that could send the stored OpenAI API key elsewhere (rated low). The four advisories that 3.0.2's notes cite are still not public.

Paperwork. GitHub reviewed the four Aspire dashboard records covered on November 11 (fixed in 13.6.5) and the two Pillow TIFF records covered on November 2 (fixed in 13.0.0). Gradio 6.32.0, released yesterday, allows pillow<14.0, which ends the Pillow cap this digest has carried since October 21. pgEdge RAG Server's three September records, a 7.5 and two mediums fixed in July, also reached the database.

Quiet elsewhere. GitHub's reviewed feed came back at 17:17 UTC yesterday after 40 quiet hours, with 50 records, most outside the tracked stack; the same query for October 28–29 returns 117. The unreviewed feed held 557 records and NVD 358. MSRC hasn't revised a .NET or Azure entry since yesterday morning. Angular CLI 22.2.7, 21.2.30 and 20.3.43 (yesterday) still pin Vite 8.3.5 and 7.3.7, as on November 10; 22.3.0-rc.0 moves to 8.3.8. 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. SiYuan 3.8.11, which carries the agent chat panel fix, is still an alpha. 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. None of this week's GPUStack, GitLab MCP, MCP Inspector, brace-expansion or MCP reference server records has 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 more
  1. 01

    The Patch

    The Patch — November 20, 2026

    Nov 20, 2026

  2. 02

    News

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

    Nov 19, 2026

  3. 03

    The Patch

    The Patch — November 19, 2026

    Nov 19, 2026

Letters

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