CVE-2026-74880: openssl-encrypt accepts refresh tokens as URL query parameters causing token leakage

CVE-2026-74880 · Severity: critical · CVSS 9.8 · Published 2026-08-17

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.

Technologies: Jahlives Openssl Encrypt, openssl-encrypt (PyPI). Vendors: Jahlives, PyPI.

Quick answers

Is CVE-2026-74880 exploited in the wild?
No. Junglewise Threat Intelligence has no report of CVE-2026-74880 being exploited in the wild.
How severe is CVE-2026-74880?
Critical severity, with a CVSS score of 9.8, published 17 August 2026.
Which products and versions are affected?
openssl-encrypt (PyPI) ECOSYSTEM:introduced=0,fixed=1.4.0.
Is there a fix for CVE-2026-74880?
Yes. openssl-encrypt (PyPI): upgrade to 1.4.0 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
Am I affected by CVE-2026-74880?
Check whether you run Jahlives Openssl Encrypt or openssl-encrypt (PyPI) 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.

How to fix

  • openssl-encrypt (PyPI): upgrade to 1.4.0 or later
    pip install "openssl-encrypt>=1.4.0"

Affected products

  • Jahlives Openssl Encrypt
  • openssl-encrypt (PyPI) ECOSYSTEM:introduced=0,fixed=1.4.0

Identifiers

  • CVE-2026-74880
  • GHSA-4rh7-jwg9-m28m
  • PYSEC-2026-3759

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.