CVE-2026-74880

openssl_encrypt before 1.4.0 Token Leakage via Query Parameters

Published Aug 17, 2026 CVSS 4.0 · 9.3 Critical EPSS < 1% KEV · Not listed
Description
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.

Analysis

AI-generated

Technical impact

The vulnerability in openssl_encrypt permits refresh tokens to be passed as query string values for keyserver and telemetry endpoints. These URL parameters are logged by the server, captured by proxy logs, stored in browser history, or transmitted via HTTP Referer headers, thereby revealing tokens to anyone who can read those artifacts. The practical result is that an attacker can acquire a valid refresh token and subsequently use it to gain elevated access or persistence within the system, constituting a severe information‑disclosure flaw (CWE‑598).

Affected Systems

The issue affects the openssl_encrypt package maintained by jahlives. All releases prior to version 1.4.0 are vulnerable, so any deployment using an older version is at risk.

Risk and Exploitability

The flaw carries a CVSS score of 9.3, indicating critical severity. EPSS data is not available, and the vulnerability is not currently listed in the KEV catalog, but the exploitation path remains straightforward: an attacker sends a crafted HTTP request that includes a legitimate refresh token in the query string to the keyserver or telemetry route, logs the response or monitors server logs, and later reads the token from those artifacts. Network access to the target service and the ability to observe logs or browsing history are the primary prerequisites for exploitation. Consequently, the risk of widespread accidental exploitation is high given the ubiquity of the components involved.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Upgrade openssl_encrypt to version 1.4.0 or newer to remove token acceptance via query parameters
  • If an upgrade is not immediately possible, modify the application to reject or strip refresh tokens from query strings on the keyserver and telemetry endpoints
  • Ensure that logging, telemetry, and referral data are sanitized or configured to exclude query parameters so that sensitive tokens are not recorded

Generated by OpenCVE AI on August 17, 2026 at 12:31 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories available
History
Type Values Removed Values Added
CPEs cpe:2.3:a:jahlives:openssl_encrypt:*:*:*:*:*:*:*:*
Type Values Removed Values Added
CPEs cpe:2.3:a:jahlives:openssl_encrypt:*:*:*:*:*:python:*:*
Type Values Removed Values Added
First Time appeared Jahlives
Jahlives openssl Encrypt
Vendors & Products Jahlives
Jahlives openssl Encrypt
Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'yes', 'Exploitation': 'none', 'Technical Impact': 'total'}, 'version': '2.0.3'}

Type Values Removed Values Added
Description 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.
Title openssl_encrypt before 1.4.0 Token Leakage via Query Parameters
Weaknesses CWE-598
References
Metrics cvssV3_1

{'score': 9.8, 'vector': 'CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H'}

cvssV4_0

{'score': 9.3, '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'}

Weaknesses
  • CWE-598

    Use of HTTP Request With Sensitive Query String

Sources

Status
PUBLISHED
Assigner
VulnCheck
Published
Updated
Oct 8, 2026, 3:24 PM
Reserved
Aug 17, 2026, 10:36 AM
Status
Analyzed
Published
Aug 17, 2026, 11:16 AM
Modified
Oct 24, 2026, 1:10 PM