# CVE-2026-122008: Oqtane Framework before 10.3.0 SSRF via File Upload From URL


- **Severity:** Medium 5.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:N/VA:N/SC:L/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 4 Nov 2026
- **Updated:** 8 Nov 2026
- **Also known as:** GHSA-p838-xx56-rf99

## What is CVE-2026-122008?

CVE-2026-122008 is a medium-severity vulnerability in oqtane.framework, published on 4 Nov 2026. 

### Official description

Oqtane Framework before 10.3.0 contains a server-side request forgery vulnerability in the UploadFile endpoint of FileController.cs that allows authenticated registered users to make the server fetch arbitrary URLs by supplying a caller-controlled url parameter to HttpClient.GetStreamAsync without validating the scheme, host, or IP address. Attackers can request internal resources such as cloud instance metadata services or localhost-bound management interfaces, save the fetched response as a file in their own user folder, and retrieve it via the download endpoint to exfiltrate sensitive internal data or enumerate internal network hosts and ports.

Weakness: CWE-918 (Server-Side Request Forgery)

## Which versions are affected by CVE-2026-122008?


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

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

## Is CVE-2026-122008 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-122008 is a medium-severity vulnerability in oqtane.framework, published on 4 Nov 2026. 
Exploitation: There is no known exploitation of CVE-2026-122008 in the wild and no public exploit code.

Affected product: oqtane.framework. 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-122008/ (Markdown: https://insights.sbomify.com/CVE-2026-122008/index.md)
```

## Sources

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

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