# CVE-2026-85469: Supply chain in Red Hat Quay 3

> Attackers can compromise the build pipeline via a mutable third-party action to steal registry credentials or publish malicious images.

- **Severity:** High 8.0 (`CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:C/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 16 Sep 2026
- **Updated:** 7 Oct 2026
- **Also known as:** GHSA-8ghx-8455-hgv5

## What is CVE-2026-85469?

CVE-2026-85469 is a high-severity vulnerability in Red Hat Quay 3, published on 16 Sep 2026. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

A flaw was found in quay-builder-qemu. A remote attacker could exploit this by compromising the upstream `Noelware/docker-manifest-action` used in the release workflow, which is pinned to a mutable branch. This allows the attacker to inject arbitrary code, leading to the exfiltration of sensitive registry credentials or the publication of malicious images. The workflow also exposes the default GitHub token, increasing the severity of the compromise.

Weakness: CWE-1357 (Reliance on Insufficiently Trustworthy Component)

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


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

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

## Is CVE-2026-85469 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-85469 is a high-severity vulnerability in Red Hat Quay 3, published on 16 Sep 2026. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-85469 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-85469/ (Markdown: https://insights.sbomify.com/CVE-2026-85469/index.md)
```

## Sources

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

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