# CVE-2026-51773: Server-side request forgery in n/a

> An authenticated attacker can trigger Server-Side Request Forgery in OpenStack glance_store to access external servers and leak sensitive authentication headers.

- **Severity:** High 8.1 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 25 Sep 2026
- **Updated:** 25 Sep 2026
- **Also known as:** DEBIAN-CVE-2026-51773, GHSA-p93m-62q2-q66v, UBUNTU-CVE-2026-51773

## What is CVE-2026-51773?

CVE-2026-51773 is a high-severity server-side request forgery vulnerability in n/a, published on 25 Sep 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

An issue in the VMware datastore driver of OpenStack glance_store. When an authenticated attacker provides a maliciously crafted image location URI pointing to an external server, the _retry_request function fails to validate the destination host before attaching sensitive authentication headers.

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

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


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

Apply the vendor's patch.

## Is CVE-2026-51773 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-51773 is a high-severity server-side request forgery vulnerability in n/a, published on 25 Sep 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-51773 exists.

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

## Sources

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

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