# CVE-2025-4515: Zylon PrivateGPT settings.yaml cross-domain policy

> Attackers can bypass cross-origin restrictions in PrivateGPT by exploiting permissive CORS settings in the configuration file.

- **Severity:** Medium 5.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:P/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 10 May 2025
- **Updated:** 12 May 2025
- **Also known as:** GHSA-6j6m-gqwx-34j8

## What is CVE-2025-4515?

CVE-2025-4515 is a medium-severity vulnerability in Zylon PrivateGPT, published on 10 May 2025. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

A vulnerability, which was classified as problematic, was found in Zylon PrivateGPT up to 0.6.2. This affects an unknown part of the file settings.yaml. The manipulation of the argument allow_origins leads to permissive cross-domain policy with untrusted domains. It is possible to initiate the attack remotely. The exploit has been disclosed to the public and may be used. The vendor was contacted early about this disclosure but did not respond in any way.

Weakness: CWE-697 (Incorrect Comparison), CWE-942 (Permissive Cross-domain Security Policy with Untrusted Domains), CWE-346 (Origin Validation Error)

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

It affects 1 product.


Products: Pribai Privategpt.

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

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

## Is CVE-2025-4515 being exploited?

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

## Other vulnerabilities in Zylon PrivateGPT

- [CVE-2024-4343](https://insights.sbomify.com/CVE-2024-4343/): Python Command Injection in imartinez/privategpt (critical 9.8)
- [CVE-2024-5186](https://insights.sbomify.com/CVE-2024-5186/): Server Side Request Forgery (SSRF) in imartinez/privategpt (high 8.3)
- [CVE-2024-12063](https://insights.sbomify.com/CVE-2024-12063/): Denial of Service in imartinez/privategpt (high 7.5)
- [CVE-2024-8018](https://insights.sbomify.com/CVE-2024-8018/): Denial of Service (DOS) in imartinez/privategpt (high 7.5)
- [CVE-2024-3403](https://insights.sbomify.com/CVE-2024-3403/): Local File Inclusion in imartinez/privategpt (high 7.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2025-4515 is a medium-severity vulnerability in Zylon PrivateGPT, published on 10 May 2025. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-4515 exists.

Affected product: Zylon PrivateGPT. 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-4515/ (Markdown: https://insights.sbomify.com/CVE-2025-4515/index.md)
```

## Sources

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

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