# CVE-2026-6587: vibrantlabsai RAGAS Collections util.py _try_process_url server-side request forgery

> Remote attackers can exploit a server-side request forgery flaw in the RAGAS library's collections module to access internal resources.

- **Severity:** Medium 5.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 20 Apr 2026
- **Updated:** 15 Jul 2026
- **Also known as:** GHSA-95ww-475f-pr4f, PYSEC-2026-3046

## What is CVE-2026-6587?

CVE-2026-6587 is a medium-severity server-side request forgery vulnerability in vibrantlabsai RAGAS, published on 20 Apr 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

A security flaw has been discovered in vibrantlabsai RAGAS up to 0.4.3. The affected element is the function _try_process_local_file/_try_process_url of the file src/ragas/metrics/collections/multi_modal_faithfulness/util.py of the component Collections Module. Performing a manipulation of the argument retrieved_contexts results in server-side request forgery. The attack can be initiated remotely. The exploit has been released to the public and may be used for attacks. The security patch for CVE-2025-45691 was applied to a different module only. The vendor was contacted early about this disclosure but did not respond in any way.

Weakness: CWE-918 (Server-Side Request Forgery)

## Which versions are affected by CVE-2026-6587?

3 open source packages ship an affected version, including ragas.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `ragas` | PyPI | From 0.2.3 to 0.4.3 | None |
| `ragas` | PyPI | From 0.2.3 to 0.4.3 | None |
| `ragas` | PyPI | From 0.2.3 to 0.4.3 | None |

## How do I fix CVE-2026-6587?

No fix has been published for CVE-2026-6587 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-6587 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-6587 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-6587 and fix it if it is affected.

What it is: CVE-2026-6587 is a medium-severity server-side request forgery vulnerability in vibrantlabsai RAGAS, published on 20 Apr 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-6587 exists.

Affected packages and fixed versions:
- ragas (PyPI): affected from 0.2.3 up to 0.4.3; no fix listed
- ragas (PyPI): affected from 0.2.3 up to 0.4.3; no fix listed
- ragas (PyPI): affected from 0.2.3 up to 0.4.3; no fix listed

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-6587/ (Markdown: https://insights.sbomify.com/CVE-2026-6587/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-6587
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-6587
- OSV: https://osv.dev/vulnerability/CVE-2026-6587

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-6587/
Summaries are generated and may contain mistakes; the official description above is the record.