CVE-2026-5079 Affecting anythingllm package, versions *


Severity

Recommended
low

Based on default assessment until relevant scores are available.

Threat Intelligence

EPSS
0.28% (20th percentile)

Do your applications use this vulnerable package?

In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.

Test your applications
  • Snyk IDSNYK-MINIMOSLATEST-ANYTHINGLLM-17393438
  • published22 Jun 2026
  • disclosed15 Jun 2026

Introduced: 15 Jun 2026

NewCVE-2026-5079  (opens in a new tab)

How to fix?

There is no fixed version for Minimos:latest anythingllm.

NVD Description

Note: Versions mentioned in the description apply only to the upstream anythingllm package and not the anythingllm package as distributed by Minimos. See How to fix? for Minimos:latest relevant fixed versions and status.

Impact: multer versions 1.0.0 through 2.1.1 and 3.0.0-alpha.1 are vulnerable to a Denial of Service via deeply nested field names in multipart form data. The append-field dependency parses bracket notation in field names with no limit on nesting depth, allowing an attacker to force allocation of deeply nested object structures that consume CPU and memory. A single HTTP request with a crafted multipart body is sufficient to exploit this.

Patches: Users should upgrade to multer 2.2.0 (2.x line) or 3.0.0-alpha.2 (3.x prerelease) and configure the new limits.fieldNestingDepth option to the minimum depth their application requires.

Workarounds: Set limits.fields to a reasonable value to reduce the number of fields an attacker can send per request. This does not fully mitigate the issue but limits the impact.