CVE-2026-74880

CRITICALPre-NVD 9.89.8—
EchelonGraph scoreHIGH confidence

Score 9.8 from GitHub Security Advisory (severity: CRITICAL) published 2026-08-17. a secondary CVSS source baseline 9.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 4 sources updated this week
9.8EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 9.8Exploit: None knownExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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.

CVSS v3
9.8
EG Score
9.8(high)
EG Risk
59(Track)
EG Risk 59/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity98% × 45%
Exploitation0% × 40%
Automatability100% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
24%
KEV
Not listed

Published

August 17, 2026

Last Modified

August 17, 2026

Advisory Details (2)

Auto-updated Aug 17, 2026
🔬 Proof of concept available. Patch available. Sources: github.
generic

openssl_encrypt before 1.4.0 Token Leakage via Query Parameters | Advisories | VulnCheck

https://www.vulncheck.com/advisories/openssl-encrypt-before-token-leakage-via-query-parameters
github Patch Available🟡 PoC Available

Refresh tokens accepted as URL query parameters causing token leakage · Advisory · jahlives/openssl_encrypt · GitHub

https://github.com/jahlives/openssl_encrypt/security/advisories/GHSA-4rh7-jwg9-m28m

Vendor Advisories for CVE-2026-74880(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Affected Packages

(1 across 1 ecosystem)
PyPI(1)
PackageVulnerable rangeFixed inDependents
openssl-encrypt0.2.2 ... 1.4.0b8 (44 versions)1.4.0—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 34× in last 7d / 34× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-08-21 03:38 UTCGHSA enrichment
  2. 2026-08-20 23:29 UTCEG score recompute
  3. 2026-08-20 23:29 UTCGHSA enrichment
  4. 2026-08-20 22:56 UTCEPSS rescore
  5. 2026-08-20 19:21 UTCGHSA enrichment
  6. 2026-08-20 15:13 UTCGHSA enrichment
  7. 2026-08-20 11:04 UTCGHSA enrichment
  8. 2026-08-20 06:55 UTCGHSA enrichment
  9. 2026-08-20 02:46 UTCGHSA enrichment
  10. 2026-08-19 22:37 UTCGHSA enrichment
  11. 2026-08-19 18:28 UTCEG score recompute
  12. 2026-08-19 18:28 UTCGHSA enrichment
  13. 2026-08-19 17:04 UTCEPSS rescore
  14. 2026-08-19 14:18 UTCGHSA enrichment
  15. 2026-08-19 10:08 UTCGHSA enrichment
  16. 2026-08-19 05:57 UTCGHSA enrichment
  17. 2026-08-19 01:46 UTCGHSA enrichment
  18. 2026-08-18 21:37 UTCGHSA enrichment
  19. 2026-08-18 16:59 UTCEG score recompute
  20. 2026-08-18 16:59 UTCGHSA enrichment
  21. 2026-08-18 13:49 UTCEPSS rescore
  22. 2026-08-18 13:49 UTCEPSS rescore
  23. 2026-08-18 12:07 UTCGHSA enrichment
  24. 2026-08-18 07:55 UTCGHSA enrichment
  25. 2026-08-18 03:46 UTCGHSA enrichment
Show 9 more
  1. 2026-08-17 23:38 UTCGHSA enrichment
  2. 2026-08-17 19:29 UTCGHSA enrichment
  3. 2026-08-17 15:20 UTCEG score recompute
  4. 2026-08-17 15:20 UTCGHSA enrichment
  5. 2026-08-17 14:44 UTCEG score recompute
  6. 2026-08-17 14:44 UTCGHSA enrichment
  7. 2026-08-17 11:39 UTCEG score recompute
  8. 2026-08-17 11:13 UTCEG score recompute
  9. 2026-08-17 11:12 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-74880?
CVE-2026-74880 is a critical vulnerability published on August 17, 2026. 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.
When was CVE-2026-74880 disclosed?
CVE-2026-74880 was first published in the National Vulnerability Database on August 17, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-74880 actively exploited?
CVE-2026-74880 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 76.5% of all scored CVEs.
What is the CVSS score of CVE-2026-74880?
CVE-2026-74880 has a CVSS v3 base score of 9.8 (NVD).
How do I remediate CVE-2026-74880?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-74880, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-74880

Explore →

Is Your Infrastructure Affected by CVE-2026-74880?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs