# CVE-2026-48116: AnythingLLM: RCE via ripgrep --pre argument injection in filesystem-search-files agent skill

> Attackers can execute arbitrary commands in the AnythingLLM server container by injecting arguments into the ripgrep tool via the filesystem-search-files agent skill.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 28 May 2026
- **Updated:** 30 May 2026
- **Also known as:** GHSA-6hrp-7mw6-8v59, MINI-xxwv-hhmr-9v3c

## What is CVE-2026-48116?

CVE-2026-48116 is a high-severity command injection vulnerability in Mintplexlabs Anythingllm, published on 28 May 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

AnythingLLM is an application that turns pieces of content into context that any LLM can use as references during chatting. Prior to 1.13.0, the filesystem-search-files agent skill passes its LLM-controlled pattern parameter to ripgrep as a positional argument without a -- end-of-options separator. ripgrep parses any argument that starts with - as an option, so a pattern of --pre=/bin/sh turns ripgrep into a script executor: it runs /bin/sh <file> for every file it walks. An attacker who can chat with an agent on a deployment with the filesystem plugin enabled (the default in the official Docker image) can use this, together with the sibling filesystem-write-text-file skill, to run arbitrary commands inside the AnythingLLM server container. This vulnerability is fixed in 1.13.0.

Weakness: CWE-88 (Improper Neutralization of Argument Delimiters in a Command), CWE-77 (Improper Neutralization of Special Elements used in a Command)

## Which versions are affected by CVE-2026-48116?

It affects 1 product.


Products: Mintplexlabs Anythingllm.

## How do I fix CVE-2026-48116?

Upgrade to a fixed version.

## Is CVE-2026-48116 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-48116 exists.

## Other vulnerabilities in Mintplexlabs Anythingllm

- [CVE-2024-3025](https://insights.sbomify.com/CVE-2024-3025/): Path Traversal in mintplex-labs/anything-llm (critical 9.9)
- [CVE-2024-0455](https://insights.sbomify.com/CVE-2024-0455/): SSRF on AWS deployed instances of AnythingLLM via /metadata (critical 9.9)
- [CVE-2026-32626](https://insights.sbomify.com/CVE-2026-32626/): AnythingLLM has a Streaming Phase XSS to RCE via LLM Response Injection (critical 9.7)
- [CVE-2024-3104](https://insights.sbomify.com/CVE-2024-3104/): Remote Code Execution in mintplex-labs/anything-llm (critical 9.6)
- [CVE-2024-3149](https://insights.sbomify.com/CVE-2024-3149/): SSRF in mintplex-labs/anything-llm (critical 9.6)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-48116 and fix it if it is affected.

What it is: CVE-2026-48116 is a high-severity command injection vulnerability in Mintplexlabs Anythingllm, published on 28 May 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-48116 exists.

Affected product: Mintplexlabs Anythingllm. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-48116/ (Markdown: https://insights.sbomify.com/CVE-2026-48116/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-48116
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-48116
- OSV: https://osv.dev/vulnerability/CVE-2026-48116

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-48116/
Summaries are generated and may contain mistakes; the official description above is the record.