# CVE-2025-6283: xataio Xata Agent route.ts GET path traversal

> An attacker can exploit a path traversal vulnerability in the Xata Agent API to read arbitrary files from the server.

- **Severity:** Medium 5.1 (`CVSS:4.0/AV:A/AC:L/AT:N/PR:L/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N/E:X`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 19 Jun 2025
- **Updated:** 23 Jun 2025
- **Also known as:** GHSA-5gmg-xg53-5783

## What is CVE-2025-6283?

CVE-2025-6283 is a medium-severity path traversal vulnerability in xataio Xata Agent, published on 19 Jun 2025. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

A vulnerability was found in xataio Xata Agent up to 0.3.0. It has been classified as problematic. This affects the function GET of the file apps/dbagent/src/app/api/evals/route.ts. The manipulation of the argument passed leads to path traversal. Upgrading to version 0.3.1 is able to address this issue. The patch is named 03f27055e0cf5d4fa7e874d34ce8c74c7b9086cc. It is recommended to upgrade the affected component.

Weakness: CWE-22 (Improper Limitation of a Pathname to a Restricted Directory)

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

It affects 1 product.


Products: Xata Agent.

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

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

## Is CVE-2025-6283 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-6283 is a medium-severity path traversal vulnerability in xataio Xata Agent, published on 19 Jun 2025. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-6283 exists.

Affected product: xataio Xata Agent. No package-level version data is available, so check the vendor advisory linked from the reference page.

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

## Sources

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

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