# CVE-2026-85471: Quay: quay: webhook notification ssrf -- hostname-string blocklist trivially bypassable

> An authenticated repository administrator can bypass hostname blocklists in webhook notifications to perform SSRF, potentially exposing sensitive internal service data.

- **Severity:** Medium 6.4 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/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:** No
- **Published:** 12 Oct 2026
- **Updated:** 14 Oct 2026
- **Also known as:** GHSA-f2g8-c8v2-qmmr

## What is CVE-2026-85471?

CVE-2026-85471 is a medium-severity server-side request forgery vulnerability in Red Hat Quay 3, published on 12 Oct 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

A flaw was found in Quay. An authenticated repository administrator could bypass the hostname blacklist in webhook notifications, leading to a Server-Side Request Forgery (SSRF) vulnerability. This allows the Quay application to be tricked into sending requests to internal network resources, such as cloud metadata services or other services within the cluster. Consequently, this could lead to the disclosure of sensitive information from these internal services.

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

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


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

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

## Is CVE-2026-85471 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-85471 is a medium-severity server-side request forgery vulnerability in Red Hat Quay 3, published on 12 Oct 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-85471 in the wild and no public exploit code.

Affected product: Red Hat Quay 3. 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-85471/ (Markdown: https://insights.sbomify.com/CVE-2026-85471/index.md)
```

## Sources

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

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