# CVE-2025-71316: SQLite sqldiff remote code execution via argument injection

> Attackers can execute arbitrary code via DLL injection in SQLite sqldiff due to unsafe Unicode-to-ANSI conversion handling.

- **Severity:** Critical 9.2 (`CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 4 Jun 2026
- **Updated:** 15 Oct 2026
- **Also known as:** GHSA-gxv8-whj6-g59f

## What is CVE-2025-71316?

CVE-2025-71316 is a critical command injection vulnerability in SQLite sqldiff, published on 4 Jun 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

SQLite 'sqldiff.exe' does not securely handle the way the Microsoft Windows C runtime converts Unicode characters to ANSI codepages.  An attacker could use the '-L' option to load an arbitrary DLL with a crafted command line argument string that results in command line file arguments being misinterpreted as command line options. Fixed on or around 2025-12-26.

Weakness: CWE-176 (Improper Handling of Unicode Encoding)

## Which versions are affected by CVE-2025-71316?


## How do I fix CVE-2025-71316?

No fix has been published for CVE-2025-71316 yet. Limit exposure of the affected software until one is available.

## Is CVE-2025-71316 being exploited?

There is no known exploitation of CVE-2025-71316 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-71316 and fix it if it is affected.

What it is: CVE-2025-71316 is a critical command injection vulnerability in SQLite sqldiff, published on 4 Jun 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-71316 in the wild and no public exploit code.

Affected product: SQLite sqldiff. 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-2025-71316/ (Markdown: https://insights.sbomify.com/CVE-2025-71316/index.md)
```

## Sources

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

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