CVE-2026-74880

Public PoC

Published

17 August 2026

Modified

17 August 2026

CVSS Score v4 9.3

Click a component to see what it means

Raw vector

CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

EPSS Score 0.0031 24th percentile

Risk Priority 45 floored blend · peak EPSS

Summary

CVE-2026-74880 is a critical-severity Use of HTTP Request With Sensitive Query String (CWE-598) vulnerability. Its CVSS base score is 9.3 (Critical).

Operationally, exploitation aligns with the MITRE ATT&CK technique Network Sniffing (T1040); ranked at the 24th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog; a public proof-of-concept is referenced.

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

OWASP Top 10 for Web (2025)

EU & UK References

🇪🇺 ENISA EUVD: EUVD-2026-60099

Vulnerability Data

openssl_encrypt versions before 1.4.0 accept refresh tokens as URL query parameters in keyserver and telemetry server routes. Attackers can extract tokens from server logs, proxy logs, browser history, and HTTP Referer headers to gain unauthorized access.

CWE(s): CWE-598

Related Threats

MITRE ATT&CK Enterprise Techniques

T1040 Network Sniffing Credential Access

Adversaries may passively sniff network traffic to capture information about an environment, including authentication material passed over the network.

attack.mitre.org →

Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2024-38863Shared CWE-598

CVE-2024-41738Shared CWE-598

CVE-2025-24948Shared CWE-598

CVE-2026-31381Shared CWE-598

CVE-2026-34020Shared CWE-598

CVE-2025-36371Shared CWE-598

CVE-2026-37504Shared CWE-598

CVE-2025-1738Shared CWE-598

CVE-2026-14838Shared CWE-598

CVE-2025-41772Shared CWE-598

Affected Assets

Mitigating Controls

Control response

Prevent

Stop it (NIST 800-53)

—

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

SC-8 Transmission Confidentiality and Integrity partial match

Requiring confidentiality and integrity protection for transmitted data reduces exposure of sensitive query parameters even though the control does not forbid placing secrets in 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.

A.8.29 Security testing in development and acceptance mostly match

finds

Security testing can detect sensitive data leakage via query strings.

A.8.12 Data leakage prevention partial match

mitigates

DLP solutions can detect and block sensitive data in URLs.

A.8.20 Networks security partial match

degrades

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

A.8.26 Application security requirements partial match

prevents

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