Skip to main content
VulnerabilityPublished

CVE-2026-105148: SciPhi-AI R2R · Server-Side Request Forgery

Source GCVE Database

0
Compare
Authoritative record:CVE-2026-105148· Medium 6.9

Public exploit available · CVSS 6.9 Medium.

Data as of 16 Nov 2026, 20:25 UTC

CVSS 4.0 base score
6.9Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.2% chance of exploitation in 30 days – higher than 20% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:P

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 4 Oct 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: evidence found.

    CVSS exploit maturity: proof of concept public

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), CVSS vector, the Metasploit, Exploit-DB and nuclei-templates index as of 16 Nov 2026.

What to do

Affected software

ProductAffectedFixed in
SciPhi-AIR2RAffected
  • 3.6.0 – 3.6.6
7 affected builds
Fixed in–

AI-suggested

Users should monitor vendor communications for updates. Until a fix is provided, consider restricting network access to the vulnerable API endpoint and applying network-level controls to limit outbound requests from the affected server. Avoid exposing the vulnerable component to untrusted networks.

Description

A server-side request forgery (SSRF) vulnerability exists in SciPhi-AI R2R versions up to 3.6.6 in the Retrieval Completion API Endpoint component. The flaw is due to manipulation of the argument generation_config.api_base in the file py/shared/abstractions/llm.py. The vulnerability can be exploited remotely and public exploit code is available. The vendor has not responded to the disclosure. No patch or fixed version is currently known.

References

Community reviews

Loading reviews…