# CVE-2026-105447: Quay: quay: global read-only superuser can access build trigger write credentials

> Read-only admins can retrieve write tokens via build trigger API, allowing unauthorized image pushes to private repositories.

- **Severity:** Medium 5.5 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:L/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 5 Oct 2026
- **Updated:** 8 Oct 2026
- **Also known as:** GHSA-wr22-68gv-32xw

## What is CVE-2026-105447?

CVE-2026-105447 is a medium-severity missing authorization vulnerability in Red Hat Quay 3, published on 5 Oct 2026. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

A flaw was found in Quay. When handling build trigger requests, the application incorrectly exposes trigger configuration details containing repository write tokens to global read-only administrative users. An authenticated user with read-only privileges can exploit this flaw by querying the build trigger API to retrieve these delegate tokens. This issue allows a restricted user to bypass read-only limitations and push arbitrary container images to private repositories, leading to privilege escalation.

Weakness: CWE-863 (Incorrect Authorization)

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


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

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

## Is CVE-2026-105447 being exploited?

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

## Fix prompt for AI coding agents

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

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

## Sources

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

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