CVE-2026-82526
Stacked SQL injection in R2R vector index creation allows arbitrary SQL execution.
WAF coverage: SQL injection. Signatures match well at the request layer.
Also consider: parameterized queries · ORM
Is CVE-2026-82526 being exploited?
Not confirmed. CVE-2026-82526 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.40% probability of exploitation in the next 30 days.
How severe is CVE-2026-82526?
CVE-2026-82526 is rated Critical with a CVSS score of 9.3. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2026-82526?
Not known from our data. No patch reference has been recorded for CVE-2026-82526, which is not the same as no patch existing — a fix may have shipped without a tagged reference, or after this record was written. The vendor advisory is the only authority on whether a fix exists, and mitigations may be available regardless.
What does CVE-2026-82526 affect?
CVE-2026-82526 affects R2R <= 3.6.6, R2R vector index creation endpoint, PostgreSQL-backed deployments. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-82526?
Restrict endpoint access, enforce DB least-privilege, whitelist/sanitize index names, rotate DB creds, apply vendor patch when released.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Unauthenticated SQL injection via index-name lets attackers run arbitrary DDL/DML as PostgreSQL superuser (data exfiltration, schema tamper/destruction, possible RCE).
Immediate action required
- affected<= 3.6.6
- affected<= 9c5a94d151f90876bd7eb860f300a8fd662dc481
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.