# CVE-2026-82527: R2R 3.6.6 SQL Injection via Retrieval Search Filter Key

> Unauthenticated attackers can inject SQL into the retrieval search filter key to exfiltrate data from the R2R application database.

- **Severity:** High 8.7 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/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:** 3 Sep 2026
- **Updated:** 4 Sep 2026
- **Also known as:** GHSA-j3pv-p6h2-grgg

## What is CVE-2026-82527?

CVE-2026-82527 is a high-severity SQL injection vulnerability in SciPhi-AI R2R, published on 3 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

R2R through 3.6.6 contains a SQL injection vulnerability that allows unauthenticated attackers to inject SQL predicates into the chunks search query by manipulating the filter key parameter in the retrieval search endpoint. Attackers can exploit the direct interpolation of filter keys into the SQL WHERE clause without parameterization or escaping to perform time-based and boolean-based data exfiltration from the application database.

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

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


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

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

## Is CVE-2026-82527 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-82527 is a high-severity SQL injection vulnerability in SciPhi-AI R2R, published on 3 Sep 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-82527 exists.

Affected product: SciPhi-AI R2R. 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-82527/ (Markdown: https://insights.sbomify.com/CVE-2026-82527/index.md)
```

## Sources

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

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