# CVE-2026-50006: Anyquery: Arbitrary File Write (AFW) which could lead to Remote Code Execution (RCE) via Unrestricted ATTACH DATABASE in Server Mode

> Remote attackers can write arbitrary files via unrestricted SQL ATTACH commands, potentially leading to code execution or denial of service.

- **Severity:** Critical 9.1 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 14 Sep 2026
- **Updated:** 15 Sep 2026
- **Also known as:** GHSA-xrcf-6jh3-ggvx, GO-2026-5979

## What is CVE-2026-50006?

CVE-2026-50006 is a critical path traversal vulnerability in julien040 anyquery, published on 14 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Anyquery is an SQL query engine built on top of SQLite. Prior to 0.4.5, anyquery server forwards unauthenticated SQL from its MySQL-compatible server port to SQLite without restricting ATTACH DATABASE filesystem targets. A remote attacker can select any path writable by the Anyquery server process, cause SQLite to create a database file there, and place attacker-controlled table content in that file. This permits arbitrary file creation or overwrite, causing filesystem integrity loss and denial of service; remote code execution is possible only when another service interprets the written file or the process has a suitably privileged writable target. This issue is fixed in version 0.4.5.

Weakness: CWE-862 (Missing Authorization), CWE-434 (Unrestricted Upload of File with Dangerous Type), CWE-284 (Improper Access Control), CWE-73 (External Control of File Name or Path), CWE-22 (Improper Limitation of a Pathname to a Restricted Directory)

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

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 | None |
| `github.com/julien040/anyquery` | Go | All versions | None |

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

Upgrade to a fixed version.

## Is CVE-2026-50006 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-50006 is a critical path traversal vulnerability in julien040 anyquery, published on 14 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-50006 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; no fix listed
- github.com/julien040/anyquery (Go): affected all versions; no fix listed

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

## Sources

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

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