high CVSS 7.5

CVE-2026-48116·Docker vulnerability

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.

Severity: high
Software: Docker
Fixed in: 1.13.0
Published: 2026-05-28

Affected versions

Until: 1.13.0

Fixed in: 1.13.0

How to fix this CVE

Update Docker to the latest version to address this vulnerability. The issue involves improper argument handling in the filesystem-search-files agent skill that could allow command injection. Upgrade to Docker version 1.13.0 or later, which includes proper sanitization of parameters passed to ripgrep and prevents option injection attacks.

sudo dnf upgrade docker-ce

Defensia detects this vulnerability

How to check if you are affected

Step 1: Run 'docker --version' to check the current Docker version installed on your system
Step 2: If using AnythingLLM in Docker, verify the image tag with 'docker images | grep anythingllm' and check if it's below version 1.13.0
Step 3: Review container logs for unusual ripgrep invocations using 'docker logs <container_id> | grep -i ripgrep' or 'docker logs <container_id> | grep -i "--pre='
Step 4: Confirm the patch by pulling the latest image and comparing: 'docker pull mintplexlabs/anythingllm:latest' and verifying the build date is after the fix commit date

FAQ

What is CVE-2026-48116?

This vulnerability affects AnythingLLM's filesystem-search-files agent skill, which fails to properly escape user-supplied pattern parameters before passing them to ripgrep. An attacker can inject ripgrep options (like --pre) to execute arbitrary commands within the container.

Is CVE-2026-48116 being actively exploited?

No, this vulnerability is not currently listed on the CISA Known Exploited Vulnerabilities (KEV) catalog, and no public exploits have been released. However, the attack vector is straightforward for authenticated users.

What versions of Docker are affected by CVE-2026-48116?

All versions of AnythingLLM prior to 1.13.0 are affected. Since the vulnerability is in the AnythingLLM application running inside Docker containers (not Docker itself), ensure your AnythingLLM container image is updated to version 1.13.0 or later.

How do I check if my server is vulnerable to CVE-2026-48116?

Run 'docker images | grep anythingllm' and check the tag version. If the version is below 1.13.0, your deployment is vulnerable. Also verify that the filesystem plugin is enabled in your AnythingLLM configuration (it is enabled by default in the official Docker image).

Does Defensia detect CVE-2026-48116?

Yes — Defensia's CVE advisory scanner compares installed package versions and container images against the NVD database. If AnythingLLM or Docker is deployed on a monitored server, CVE-2026-48116 will appear in your dashboard with remediation steps.

Related Docker CVEs

CVE-2026-44329CVSS 10free5GC is an open-source implementation of the 5G core network. Prior to 4.2.2, free5GC's SMF mounts the UPI management route group without OAuth2/bearer-token authorization middleware. A network attacker who can reach SMF on the SBI can hit UPI endpoints with no Authorization header at all, and the requests reach the SMF business handlers. In the running Docker lab this was directly demonstrated for read (GET /upi/v1/upNodesLinks), write (POST /upi/v1/upNodesLinks with attacker-controlled UP-node and link payload), and delete (DELETE /upi/v1/upNodesLinks/{nodeID}) operations. This vulnerability is fixed in 4.2.2.

CVE-2026-40281CVSS 10Gotenberg is a Docker-powered stateless API for PDF files. In versions 8.30.1 and earlier, the metadata write endpoint validates metadata keys for control characters but leaves metadata values unsanitized. A newline character in a metadata value splits the ExifTool stdin line into two separate arguments, allowing injection of arbitrary ExifTool pseudo-tags such as -FileName, -Directory, -SymLink, and -HardLink. This is a bypass of the incomplete key-sanitization fix introduced in v8.30.1. An unauthenticated attacker can rename or move any PDF being processed to an arbitrary path in the container filesystem, overwrite arbitrary files, or create symlinks and hard links at arbitrary paths.

CVE-2026-57572CVSS 10Crawl4AI is an open-source LLM-friendly web crawler and scraper. Prior to 0.9.0, the Docker API server accepted request-supplied browser_config.extra_args, which flowed into Chromium's launch arguments. An attacker could inject Chromium switches that replace a child-process launch command together with --no-zygote, causing Chromium to fork or exec an attacker-controlled command as the container's runtime user. The Docker API is unauthenticated by default, so a single request yields arbitrary command execution. This issue is fixed in version 0.9.0.

CVE-2026-53576CVSS 10Kestra is an open-source, event-driven orchestration platform. Prior to 1.0.45 and 1.3.21, the authentication filter for the REST API (@Filter("/api/v1/**")) treats any request whose path ends in /configs as the public instance-config endpoint and forwards it without a credential check. kestra addresses its resources by URL path segments that the caller chooses (/api/v1/{tenant}/flows/{namespace}, /api/v1/{tenant}/executions/{namespace}/{id}, /api/v1/{tenant}/namespaces/{namespace}/kv/{key}). An anonymous caller picks the literal configs as the final segment, and the request bypasses Basic-Auth entirely. Because the bypass reaches the flow-create and execution-trigger routes, an unauthenticated caller creates a flow containing a Shell or Process task and runs it. The task executes as root inside the kestra container. The official docker-compose.yml mounts /var/run/docker.sock, so root in the container reaches the host Docker daemon. This vulnerability is fixed in 1.0.45 and 1.3.21.

CVE-2026-33587CVSS 10Lack of user input sanitisation in Open Notebook v1.8.3 allows the application user to execute Python code (and subsequently OS commands) on the docker container via Server-Side Template Injection (SSTI) for user-created transformations.

References

Track CVEs across your fleet automatically

Defensia scans your Linux servers and tells you exactly which ones are running vulnerable versions — including CVE-2026-48116. Free for 1 server.

Get started free