Credential disclosure via OAuth query parameters
Published May 29, 2026 · Updated May 29, 2026
Information disclosure in Red Hat Quay 3's config-tool allows remote authenticated users to read GitLab OAuth credentials from request logs. The GitLab OAuth validator places client_id and client_secret in a POST request's URL query string rather than its request body. Administrative config-tool access and access to server, proxy, or monitoring logs are required; disclosure is limited to credentials recorded there.
Summary
What happened
Information disclosure in Red Hat Quay 3's config-tool allows remote authenticated users to read GitLab OAuth credentials from request logs. The GitLab OAuth validator places client_id and client_secret in a POST request's URL query string rather than its request body. Administrative config-tool access and access to server, proxy, or monitoring logs are required; disclosure is limited to credentials recorded there.
The record
- CVE
- CVE-2026-10078
- Published
- May 29, 2026
- Updated
- May 29, 2026
- Vendor
- 389 Directory Server
- Product
- Red Hat Quay
- Classifications
- CWE-598, T1552.001
- Attack vector
- network
- Privileges
- admin
Timeline
How it unfolded
- May 29, 2026CVE publishedPublication date reported by the CVE source.
- May 29, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Affected versions are unavailable in this record. Check the vendor advisory for version and patch details.
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo