CVE-2026-82527
Received Received - Intake

SQL Injection in R2R through 3.6.6

Publication date: 2026-09-03

Last updated on: 2026-09-03

Assigner: VulnCheck

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.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published
2026-09-03
Last Modified
2026-09-03
Generated
2026-09-04
AI Q&A
2026-09-03
EPSS Evaluated
N/A
NVD
CVE-2026-82527
EUVD
EUVD-2026-70701

Affected Vendors & Products

Currently, no data is known.

Helpful Resources

Exploitability

CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-89 The product constructs all or part of an SQL command using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the intended SQL command when it is sent to a downstream component. Without sufficient removal or quoting of SQL syntax in user-controllable inputs, the generated SQL query can cause those inputs to be interpreted as SQL instead of ordinary user data.

Attack-Flow Graph

AI Quick Actions

Instant insights powered by AI
Executive Summary

This vulnerability is a SQL injection flaw in R2R versions up to 3.6.6. It allows unauthenticated attackers to inject malicious SQL code into the filter key parameter of the retrieval search endpoint. The application directly inserts this input into the SQL WHERE clause without proper escaping or parameterization, enabling attackers to manipulate database queries.

Detection Guidance

To detect this SQL injection vulnerability in R2R versions up to 3.6.6, monitor network traffic for suspicious requests to the retrieval search endpoint. Look for filter key parameters containing SQL syntax like 'OR 1=1', time delays, or boolean expressions. Use tools like SQLmap to test endpoints for injection points.

Impact Analysis

Attackers could exploit this to extract sensitive data from the application database through time-based or boolean-based techniques. This may lead to unauthorized access to confidential information, data breaches, or potential system compromise depending on the database contents and application context.

Compliance Impact

This vulnerability could lead to violations of data protection regulations like GDPR or HIPAA by enabling unauthorized access to personal or health data. Organizations may face legal penalties, reputational damage, and increased scrutiny from regulators due to potential data exposure resulting from this flaw.

Mitigation Strategies

Immediately upgrade R2R to a version beyond 3.6.6 if available. If not, apply input validation to sanitize the filter key parameter. Use parameterized queries instead of direct SQL interpolation. Restrict database user permissions to limit potential data exfiltration.

Chat Assistant

Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-82527. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70

EPSS Chart