R2R through 3.6.5 fails to properly validate user ownership in conversation update and message handlers, allowing authenticated users to modify other users' conversations. Attackers can supply arbitrary conversation identifiers to rename conversations and append messages to other users' conversation histories, corrupting state and injecting malicious content.
CVE-2026-82271
Score 6.5 from GitHub Security Advisory (severity: HIGH) published 2026-08-28. a secondary CVSS source baseline 6.5; sources differ by 0.0.
- Lower severity and no public exploit yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 6.5
- EG Score
- 6.5(high)
- EG Risk
- 34(Track)EG Risk 34/100SSVC: Track
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computedSeverity65% × 45%Exploitation0% × 40%Automatability30% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- 0%
- EPSS %ILE
- 12%
- KEV
- Not listed
Published
August 28, 2026
Last Modified
August 28, 2026
Advisory Details (4)
Auto-updated Aug 28, 2026R2R Missing Ownership Check Allows Modifying Other Users' Conversations | Advisories | VulnCheck
https://www.vulncheck.com/advisories/r2r-missing-ownership-check-allows-modifying-other-users-conversationsR2R/py/core/main/api/v3/conversations_router.py at 9c5a94d151f90876bd7eb860f300a8fd662dc481 · SciPhi-AI/R2R · GitHub
https://github.com/SciPhi-AI/R2R/blob/9c5a94d151f90876bd7eb860f300a8fd662dc481/py/core/main/api/v3/conversations_router.pyGitHub - SciPhi-AI/R2R: SoTA production-ready AI retrieval system. Agentic Retrieval-Augmented Generation (RAG) with a RESTful API. · GitHub
https://github.com/SciPhi-AI/R2R[Security] Cross-user conversation IDOR · Issue #2292 · SciPhi-AI/R2R · GitHub
https://github.com/SciPhi-AI/R2R/issues/2292Vendor Advisories for CVE-2026-82271(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 6× in last 7d / 6× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
- 2026-08-30 01:22 UTCEPSS rescore
- 2026-08-29 19:29 UTCEG score recompute
- 2026-08-29 19:29 UTCGHSA enrichment
- 2026-08-28 20:26 UTCEG score recompute
- 2026-08-28 19:40 UTCEG score recompute
- 2026-08-28 19:36 UTCMITRE cvelistV5first tracked
Frequently asked(5)
What is CVE-2026-82271?
When was CVE-2026-82271 disclosed?
Is CVE-2026-82271 actively exploited?
What is the CVSS score of CVE-2026-82271?
How do I remediate CVE-2026-82271?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-82271
Is Your Infrastructure Affected by CVE-2026-82271?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.