CVE-2026-82527
Unauthenticated SQL injection in R2R retrieval search filter key (<=3.6.6).
Is CVE-2026-82527 being exploited?
Not confirmed. CVE-2026-82527 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.27% probability of exploitation in the next 30 days.
How severe is CVE-2026-82527?
CVE-2026-82527 is rated High. 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-82527?
Not known from our data. No patch reference has been recorded for CVE-2026-82527, 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-82527 affect?
CVE-2026-82527 affects SciPhi-AI R2R <= 3.6.6, R2R retrieval search endpoint, Applications using R2R retrieval. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-82527?
Restrict access, enable WAF/SQLi rules, sanitize filter keys, patch when vendor releases fix.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Unauthenticated SQL injection via filter key enables time/boolean-based DB exfiltration of application data.
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.