# CVE-2026-116000: Zylon PrivateGPT URI Artifact Loader uri_loader.py load_file_from_uri server-side request forgery


- **Severity:** Medium 6.9 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:P`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 25 Oct 2026
- **Updated:** 26 Oct 2026
- **Also known as:** GHSA-5gf5-vm4r-r6j6, GHSA-8294-hj7x-42g2

## What is CVE-2026-116000?

CVE-2026-116000 is a medium-severity vulnerability in Zylon PrivateGPT, published on 25 Oct 2026. 

### Official description

A security flaw has been discovered in Zylon PrivateGPT 1.0.0/1.0.1. This vulnerability affects the function load_file_from_uri of the file private_gpt/server/ingest/uri_loader.py of the component URI Artifact Loader. Performing a manipulation of the argument Value results in server-side request forgery. It is possible to initiate the attack remotely. The exploit has been released to the public and may be used for attacks. 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-116000?


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

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

## Is CVE-2026-116000 being exploited?

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

Public exploit code:

- Safe PoC and technical analysis for CVE-2026-116000 (github_poc): https://github.com/capivara-research/CVE-2026-116000

## Fix prompt for AI coding agents

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

What it is: CVE-2026-116000 is a medium-severity vulnerability in Zylon PrivateGPT, published on 25 Oct 2026. 
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-116000 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-2026-116000/ (Markdown: https://insights.sbomify.com/CVE-2026-116000/index.md)
```

## Sources

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

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