# CVE-2026-10078: Red Hat Quay credential disclosure in GitLab OAuth validator

Source: https://junglewise.ai/threats/cve-2026-10078-red-hat-quay-credential-disclosure-in-gitlab-oauth-validator  
Publisher: Junglewise Threat Intelligence, https://junglewise.ai/threats  
Published: 2026-05-29. Updated: 2026-05-29  
License: CC BY 4.0 with a link back

CVE-2026-10078 · Severity: low · CVSS 2.7 · Published 2026-05-29

Red Hat Quay is a platform for managing and storing container images. A security flaw in its configuration tool causes sensitive GitLab login credentials to be sent in a way that makes them visible in system logs. If an unauthorized person gains access to these logs, they could steal the credentials and potentially access the linked GitLab account.

Technologies: [Red Hat Quay config-tool](https://junglewise.ai/threats/technologies/quay-3-12). Vendors: [Red Hat](https://junglewise.ai/threats/vendors/red-hat).

## Quick answers

**Is CVE-2026-10078 exploited in the wild?** No. Junglewise Threat Intelligence has no report of CVE-2026-10078 being exploited in the wild.

**How severe is CVE-2026-10078?** Low severity, with a CVSS score of 2.7, published 29 May 2026.

**Which products and versions are affected?** Red Hat Quay config-tool unspecified.

**Is there a fix for CVE-2026-10078?** No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.

**How is CVE-2026-10078 attacked?** It is attacked over the network, in a network appliance.

**Am I affected by CVE-2026-10078?** Check whether you run Red Hat Quay config-tool at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

## Technical details

A flaw exists in the Quay config-tool's GitLab OAuth validator within 'pkg/lib/shared/validators.go'. When performing validation, the tool transmits 'client_id' and 'client_secret' as plaintext URL query parameters during POST requests to the GitLab endpoint instead of using secure HTTP headers. This behavior (CWE-598) results in sensitive credentials being recorded in server access logs, reverse proxy logs, WAF logs, and monitoring traces. An attacker with high privileges or access to these logging systems could retrieve the credentials to facilitate unauthorized information disclosure. The GitHub OAuth validator is reportedly unaffected as it correctly utilizes HTTP Basic Auth headers.

## Affected products

- Red Hat Quay config-tool unspecified

## Timeline

- 2026-05-29: disclosed: Initial disclosure and NVD publication

## References

- [https://access.redhat.com/security/cve/CVE-2026-10078](https://access.redhat.com/security/cve/CVE-2026-10078)
- [https://bugzilla.redhat.com/show_bug.cgi?id=2483168](https://bugzilla.redhat.com/show_bug.cgi?id=2483168)

## Related threats

- [Red Hat Quay SSRF in config-tool LDAP and SMTP validation](https://junglewise.ai/threats/cve-2026-10052-red-hat-quay-ssrf-in-config-tool-ldap-and-smtp-validation)