# CVE-2025-45691: RAGAS has an Arbitrary File Read vulnerability

> Attackers can read arbitrary files via improper URL validation in the ImageTextPromptValue class of the RAGAS library.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 5 Mar 2026
- **Updated:** 15 Jul 2026
- **Also known as:** GHSA-v2xr-wvrv-p969, PYSEC-2026-3047

## What is CVE-2025-45691?

CVE-2025-45691 is a high-severity path traversal vulnerability in n/a, published on 5 Mar 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

An Arbitrary File Read vulnerability exists in the ImageTextPromptValue class in Exploding Gradients RAGAS v0.2.3 to v0.2.14. The vulnerability stems from improper validation and sanitization of URLs supplied in the retrieved_contexts parameter when handling multimodal inputs.

Weakness: CWE-918 (Server-Side Request Forgery), CWE-22 (Improper Limitation of a Pathname to a Restricted Directory)

## Which versions are affected by CVE-2025-45691?

3 open source packages ship an affected version, including ragas. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `ragas` | PyPI | From 0.2.3 | 0.3.0-rc1 |
| `ragas` | PyPI | From 0.2.3 | 0.3.0-rc1 |
| `ragas` | PyPI | From 0.2.3 | 0.3.0-rc1 |

Products: Vibrantlabsai Ragas.

## How do I fix CVE-2025-45691?

Upgrade ragas to 0.3.0-rc1 or later.

## Is CVE-2025-45691 being exploited?

There is no known exploitation of CVE-2025-45691 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-45691 and fix it if it is affected.

What it is: CVE-2025-45691 is a high-severity path traversal vulnerability in n/a, published on 5 Mar 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-45691 in the wild and no public exploit code.

Affected packages and fixed versions:
- ragas (PyPI): affected from 0.2.3; fixed in 0.3.0-rc1
- ragas (PyPI): affected from 0.2.3; fixed in 0.3.0-rc1
- ragas (PyPI): affected from 0.2.3; fixed in 0.3.0-rc1

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-2025-45691/ (Markdown: https://insights.sbomify.com/CVE-2025-45691/index.md)
```

## Sources

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

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