# CVE-2026-10078: Quay/config-tool: quay/config-tool: gitlab oauth client_secret exposed in url querystring

> Quay config-tool exposes GitLab OAuth credentials in URL query strings, allowing attackers with log access to steal sensitive client secrets.

- **Severity:** Low 2.7 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:L/I:N/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:** 29 May 2026
- **Updated:** 29 May 2026
- **Also known as:** GHSA-f2q6-8fx7-gjf8

## What is CVE-2026-10078?

CVE-2026-10078 is a low-severity vulnerability in Red Hat Quay 3, published on 29 May 2026. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

A flaw was found in the Quay config-tool's GitLab OAuth validator. This vulnerability causes sensitive credentials, specifically client_id and client_secret, to be transmitted as plaintext in URL query parameters during POST requests to the GitLab endpoint. This insecure transmission can lead to the disclosure of these credentials in various system logs, such as server access logs, reverse proxy logs, and other monitoring systems. An attacker with access to these logs could potentially obtain these credentials, leading to unauthorized information disclosure.

Weakness: CWE-598 (Use of HTTP Request With Sensitive Query String)

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


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

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

## Is CVE-2026-10078 being exploited?

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

## Fix prompt for AI coding agents

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

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

## Sources

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

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