# CVE-2026-56221: Cap-go - SQL Injection in Cloudflare Analytics Engine Queries via cloudflare.ts

> Authenticated users can inject SQL into Cap-go analytics queries to access other users' data via unsanitized API parameters.

- **Severity:** High 7.1 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:N/VA:N/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:** No
- **Published:** 22 Jun 2026
- **Updated:** 23 Jun 2026
- **Also known as:** GHSA-f83x-p28r-pf74

## What is CVE-2026-56221?

CVE-2026-56221 is a high-severity SQL injection vulnerability in Cap-go capgo, published on 22 Jun 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Cap-go before 12.128.2 contains multiple SQL injection vulnerabilities in cloudflare.ts where user-controlled values from API request bodies are interpolated directly into SQL query strings without sanitization or parameterization. Authenticated users with read-level API key permissions can inject arbitrary SQL through deviceIds, search, version_name, cursor, and actions parameters to access analytics data belonging to other users or applications.

Weakness: CWE-89 (Improper Neutralization of Special Elements used in an SQL Command)

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


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

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

## Is CVE-2026-56221 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-56221 is a high-severity SQL injection vulnerability in Cap-go capgo, published on 22 Jun 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-56221 exists.

Affected product: Cap-go capgo. 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-56221/ (Markdown: https://insights.sbomify.com/CVE-2026-56221/index.md)
```

## Sources

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

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