# CVE-2026-7206: dubydu sqlite-mcp entry.py extract_to_json sql injection

> SQL injection in dubydu sqlite-mcp allows remote attackers to manipulate database queries via the output_filename argument.

- **Severity:** Medium 6.9 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 28 Apr 2026
- **Updated:** 28 Apr 2026
- **Also known as:** GHSA-4j28-22qp-rjcf, PYSEC-2026-3074

## What is CVE-2026-7206?

CVE-2026-7206 is a medium-severity SQL injection vulnerability in dubydu sqlite-mcp, published on 28 Apr 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A security flaw has been discovered in dubydu sqlite-mcp up to 0.1.0. The affected element is the function extract_to_json of the file src/entry.py. Performing a manipulation of the argument output_filename results in sql injection. Remote exploitation of the attack is possible. The exploit has been released to the public and may be used for attacks. The patch is named a5580cb992f4f6c308c9ffe6442b2e76709db548. Applying a patch is the recommended action to fix this issue.

Weakness: CWE-89 (Improper Neutralization of Special Elements used in an SQL Command), CWE-74 (Improper Neutralization of Special Elements in Output Used by a Downstream Component)

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

3 open source packages ship an affected version, including sqlite-mcp.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `sqlite-mcp` | PyPI | All versions to 0.1.0 | None |
| `sqlite-mcp` | PyPI | All versions to 0.1.0 | None |
| `sqlite-mcp` | PyPI | All versions to 0.1.0 | None |

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

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

## Is CVE-2026-7206 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-7206 is a medium-severity SQL injection vulnerability in dubydu sqlite-mcp, published on 28 Apr 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-7206 exists.

Affected packages and fixed versions:
- sqlite-mcp (PyPI): affected all versions up to 0.1.0; no fix listed
- sqlite-mcp (PyPI): affected all versions up to 0.1.0; no fix listed
- sqlite-mcp (PyPI): affected all versions up to 0.1.0; 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-7206/ (Markdown: https://insights.sbomify.com/CVE-2026-7206/index.md)
```

## Sources

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

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