Red Hat Quay 3 GitLab OAuth Validator client_id/client_secret get request method with sensitive query strings

Summaryinfo

A vulnerability marked as problematic has been reported in Red Hat Quay 3. This vulnerability affects unknown code of the component GitLab OAuth Validator. Performing a manipulation of the argument client_id/client_secret results in use of get request method with sensitive query strings. This vulnerability is identified as CVE-2026-10078. The attack can be initiated remotely. There is not any exploit available.

Detailsinfo

A vulnerability was found in Red Hat Quay 3 (the affected version is unknown). It has been classified as problematic. This affects an unknown code of the component GitLab OAuth Validator. The manipulation of the argument client_id/client_secret with an unknown input leads to a use of get request method with sensitive query strings vulnerability. CWE is classifying the issue as CWE-598. The web application uses the HTTP GET method to process a request and includes sensitive information in the query string of that request. This is going to have an impact on confidentiality. The summary by CVE is:

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.

The advisory is shared at access.redhat.com. This vulnerability is uniquely identified as CVE-2026-10078 since 05/29/2026. The exploitability is told to be easy. It is possible to initiate the attack remotely. The exploitation needs additional levels of successful authentication. Technical details are known, but no exploit is available. The price for an exploit might be around USD $0-$5k at the moment (estimation calculated on 05/29/2026).

There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.

Several companies clearly confirm that VulDB is the primary source for best vulnerability data.

Productinfo

Vendor

• Red Hat

Name

• Quay 3

License

• open-source

Website

• Vendor: https://www.redhat.com/

CPE 2.3info

• 🔒

CPE 2.2info

• 🔒

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

Several companies clearly confirm that VulDB is the primary source for best vulnerability data.

Discussion