# CVE-2026-56703: Adminer before 5.4.3 Remote Code Execution via SQLite VACUUM INTO

> Authenticated attackers can exploit SQLite VACUUM INTO to write PHP code to arbitrary paths, achieving remote code execution on the server.

- **Severity:** High 8.6 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 25 Aug 2026
- **Updated:** 25 Aug 2026
- **Also known as:** DEBIAN-CVE-2026-56703, GHSA-gmx3-g29w-77wf, GHSA-j4fh-9p52-f987, UBUNTU-CVE-2026-56703

## What is CVE-2026-56703?

CVE-2026-56703 is a high-severity code injection vulnerability in vrana adminer, published on 25 Aug 2026. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

Adminer before 5.4.3 contains a remote code execution vulnerability in SQLite query handling where VACUUM INTO is not blocked despite ATTACH restrictions. Authenticated attackers can execute VACUUM INTO to write PHP code to arbitrary file paths and execute commands on the server.

Weakness: CWE-94 (Improper Control of Generation of Code)

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


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

Upgrade to a fixed version.

## Is CVE-2026-56703 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-56703 is a high-severity code injection vulnerability in vrana adminer, published on 25 Aug 2026. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-56703 exists.

Affected product: vrana adminer. 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-56703/ (Markdown: https://insights.sbomify.com/CVE-2026-56703/index.md)
```

## Sources

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

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