# CVE-2025-27937: Path traversal in Quick Agent V2

> Remote authenticated attackers can read arbitrary files via path traversal in Quick Agent V2 and V3.

- **Severity:** High 7.1 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N`)
- **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:** 27 Apr 2025
- **Updated:** 28 Apr 2025
- **Also known as:** GHSA-g9hr-8mwc-g7m7

## What is CVE-2025-27937?

CVE-2025-27937 is a high-severity path traversal vulnerability in SIOS Technology, Inc. Quick Agent V2, published on 27 Apr 2025. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Quick Agent V3 and Quick Agent V2 contain an issue with improper limitation of a pathname to a restricted directory ('Path Traversal'). If exploited, an arbitrary file in the affected product may be obtained by a remote attacker who can log in to the product.

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

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


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

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

## Is CVE-2025-27937 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-27937 is a high-severity path traversal vulnerability in SIOS Technology, Inc. Quick Agent V2, published on 27 Apr 2025. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-27937 in the wild and no public exploit code.

Affected product: SIOS Technology, Inc. Quick Agent V2. 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-27937/ (Markdown: https://insights.sbomify.com/CVE-2025-27937/index.md)
```

## Sources

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

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