Cyber Resilience

CVE-2026-10078

Published
29 May 2026
Modified
21 July 2026
CVSS Score v3.1 2.7
Click a component to see what it means
Raw vectorCVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:L/I:N/A:N
EPSS Score 0.0020 10th percentile
Risk Priority 15 floored blend · peak EPSS

Summary

CVE-2026-10078 is a low-severity Use of HTTP Request With Sensitive Query String (CWE-598) vulnerability. Its CVSS base score is 2.7 (Low).

Operationally, exploitation aligns with the MITRE ATT&CK technique Unsecured Credentials (T1552); ranked at the 10th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.

The strongest mitigations our analysis identified map to SC-8 (Transmission Confidentiality and Integrity) and AU-9 (Protection of Audit Information) — see the control section below for these in your framework.

OWASP Top 10 for Web (2025)

EU & UK References

No EU or UK CSIRT advisories indexed for this CVE.

Vulnerability Data

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…

more

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.

CWE(s)

Related Threats

MITRE ATT&CK Enterprise TechniquesAI

T1552 Unsecured Credentials Credential Access
Adversaries may search compromised systems to find and obtain insecurely stored credentials.
T1552.001 Credentials In Files Credential Access
Adversaries may search local file systems and remote file shares for files containing insecurely stored credentials.
Why these techniques?

Credential disclosure via logs directly maps to unsecured credentials exposure (T1552); logs as files align with T1552.001.

Confidence: MEDIUM · MITRE ATT&CK Enterprise v19.0

CVEs Like This One

CVE-2026-16207Shared CWE-598
CVE-2026-26196Shared CWE-598
CVE-2025-13219Shared CWE-598
CVE-2026-44883Shared CWE-598
CVE-2026-34020Shared CWE-598
CVE-2025-0730Shared CWE-598
CVE-2026-62386Shared CWE-598
CVE-2026-26721Shared CWE-598
CVE-2026-37504Shared CWE-598
CVE-2026-23846Shared CWE-598

Affected Assets

Mitigating Controls

Control response

Prevent
Stop it (NIST 800-53)
  • SC-8 Transmission Confidentiality and Integrity
  • AU-9 Protection of Audit Information
  • IA-5 Authenticator Management
Detect
Catch it (NIST detect / respond)

Harden
Shrink the surface (DISA STIG)

Validate
Prove the fix (OWASP ASVS)
  • V3.4.5
  • V14.2.1

Mitigating Controls (NIST 800-53 r5) AI

prevent

Requires cryptographic protection for sensitive data (client_id/client_secret) during transmission, directly preventing placement in query strings that survive TLS.

prevent

Protects audit and access logs from unauthorized access, limiting disclosure of credentials inadvertently recorded from URL query parameters.

prevent

Mandates secure management and transmission of authenticators, addressing the mishandling of OAuth client secrets in request URLs.

Mitigating Controls (NIST CSF 2.0) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.

PR.PS-06 mostly match
prevents

Secure SDLC practices directly prevent embedding sensitive data in query strings as part of input-handling and data-flow design.

PR.DS-02 partial match
prevents

HTTPS encryption protects query strings in transit but does not address the root design flaw of placing sensitive data in URLs.

Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.

detects

Security testing can detect sensitive data leakage via query strings.

mitigates

DLP solutions can detect and block sensitive data in URLs.

degrades

Network security controls can enforce HTTPS and block sensitive data in URLs.

prevents

Application security requirements should mandate avoiding sensitive data in query strings.

prevents

Secure architecture principles discourage exposing sensitive data in URLs.

prevents

Secure coding standards directly prohibit placing secrets in query parameters.

References