# CVE-2026-47253: Anyquery: Path Traversal in `clear_plugin_cache` Allows Arbitrary Directory Deletion

> A path traversal vulnerability in Anyquery allows attackers to delete arbitrary directories via the clear_plugin_cache function, causing data loss and denial of service.

- **Severity:** High 7.3 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:N/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 14 Sep 2026
- **Updated:** 14 Sep 2026
- **Also known as:** GHSA-j9rx-rppg-6hh4, GO-2026-5459

## What is CVE-2026-47253?

CVE-2026-47253 is a high-severity path traversal vulnerability in julien040 anyquery, published on 14 Sep 2026. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.

### Official description

Anyquery is an SQL query engine built on top of SQLite. Prior to 0.4.5, the clear_plugin_cache(plugin) SQL scalar function in namespace/other_functions.go passes the caller-controlled plugin parameter through path.Join to os.RemoveAll without rejecting traversal segments. A low-privileged bearer-token holder can invoke the function through the /v1/query HTTP endpoint, causing path.Join to resolve .. segments outside $XDG_CACHE_HOME/anyquery/plugins/ and os.RemoveAll to recursively delete any reachable directory writable by the Anyquery server process. This causes permanent data loss and denial of service without disclosing file contents. This issue is fixed in version 0.4.5.

Weakness: CWE-22 (Improper Limitation of a Pathname to a Restricted Directory)

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

3 open source packages ship an affected version, including github.com/julien040/anyquery.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `github.com/julien040/anyquery` | Go | All versions | None |
| `github.com/julien040/anyquery` | Go | All versions | 0.4.5 |
| `github.com/julien040/anyquery` | Go | All versions | 0.4.5 |

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

Upgrade github.com/julien040/anyquery to 0.4.5 or later.

## Is CVE-2026-47253 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-47253 is a high-severity path traversal vulnerability in julien040 anyquery, published on 14 Sep 2026. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-47253 exists.

Affected packages and fixed versions:
- github.com/julien040/anyquery (Go): affected all versions; no fix listed
- github.com/julien040/anyquery (Go): affected all versions; fixed in 0.4.5
- github.com/julien040/anyquery (Go): affected all versions; fixed in 0.4.5

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-47253/ (Markdown: https://insights.sbomify.com/CVE-2026-47253/index.md)
```

## Sources

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

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