# CVE-2026-34968: Adminer before 5.4.3 Arbitrary File Deletion via SQLite Drop

> Authenticated attackers can delete arbitrary files via path traversal in SQLite mode, requiring Adminer to be configured for SQLite.

- **Severity:** High 7.2 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:H/VA:H/SC:N/SI:N/SA:N`)
- **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:** 25 Aug 2026
- **Updated:** 25 Aug 2026
- **Also known as:** DEBIAN-CVE-2026-34968, GHSA-6pg3-chwq-wgqc, GHSA-vfp8-hfj6-qmr2, UBUNTU-CVE-2026-34968

## What is CVE-2026-34968?

CVE-2026-34968 is a high-severity path traversal vulnerability in vrana adminer, published on 25 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Adminer before 5.4.3 contains an arbitrary file deletion vulnerability in SQLite mode where the database-list drop action fails to validate file extensions before deletion. An authenticated attacker can submit arbitrary relative file paths in the db[] parameter to delete any files writable by the PHP process.

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

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


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

Upgrade to a fixed version.

## Is CVE-2026-34968 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-34968 is a high-severity path traversal vulnerability in vrana adminer, published on 25 Aug 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-34968 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-34968/ (Markdown: https://insights.sbomify.com/CVE-2026-34968/index.md)
```

## Sources

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

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