# CVE-2026-65170: Server-side request forgery in AIStore framework

> An unauthenticated remote attacker can cause server-side request forgery in the experimental HT backend, leading to information disclosure.

- **Severity:** High 8.6 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 13 Oct 2026
- **Updated:** 13 Oct 2026
- **Also known as:** GHSA-m3j9-p9ff-mc4v

## What is CVE-2026-65170?

CVE-2026-65170 is a high-severity server-side request forgery vulnerability in NVIDIA AIStore framework, published on 13 Oct 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

NVIDIA AIStore for Linux contains a vulnerability in the experimental HT backend where an unauthenticated remote attacker may cause server-side request forgery by supplying a crafted original URL. A successful exploit of this vulnerability may lead to information disclosure.

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

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


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

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

## Is CVE-2026-65170 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-65170 is a high-severity server-side request forgery vulnerability in NVIDIA AIStore framework, published on 13 Oct 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-65170 in the wild and no public exploit code.

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

## Sources

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

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