CVE-2026-74892

openssl_encrypt before 1.4.0 Hardcoded Secret Key

Published Aug 17, 2026 CVSS 4.0 · 8.7 High EPSS < 1% KEV · Not listed
Description
openssl_encrypt versions before 1.4.0 contain a hardcoded default secret key in the standalone telemetry server configuration that is used for API key hashing. Attackers who know this default value can predict or forge API key hashes to compromise telemetry API authentication.

Analysis

AI-generated

Technical impact

The vulnerability exposes a hardcoded default secret key in the openssl_encrypt telemetry server configuration. This key is used to hash API keys, and having the value allows attackers to predict or forge valid API hashes, thereby compromising authentication to the telemetry service. The flaw represents a severe confidentiality and integrity risk for systems that rely on this service and is classified as a CWE‑798 Hardcoded Credentials weakness.

Affected Systems

Affected products are versions of openssl_encrypt produced by jahlives that are older than 1.4.0. The hardcoded key resides in the standalone telemetry server configuration and is present in every release prior to the 1.4.0 update.

Risk and Exploitability

The CVSS score of 8.7 indicates high severity. With the EPSS score not available, the precise prevalence of exploitation is uncertain, but the lack of a KEV listing suggests it has not been widely observed as a known exploit. A likely attack vector involves an attacker who can communicate with the telemetry API; knowing the hardcoded key, the attacker can generate valid hashed API keys and gain unauthorized access. If the telemetry service is exposed to untrusted networks, remote attackers could readily exploit the flaw, whereas internal actors who have configuration access are also at risk.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Upgrade openssl_encrypt to version 1.4.0 or later where the hardcoded secret key has been removed.
  • Verify the telemetry server configuration and, if an upgrade is not yet possible, replace the hardcoded key with a unique, random secret.
  • Rotate all existing API keys and regenerate the corresponding hashes in the telemetry service to invalidate any keys forged with the default secret.

Generated by OpenCVE AI on August 17, 2026 at 12:54 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': 'partial'}, 'version': '2.0.3'}

Type Values Removed Values Added
Description openssl_encrypt versions before 1.4.0 contain a hardcoded default secret key in the standalone telemetry server configuration that is used for API key hashing. Attackers who know this default value can predict or forge API key hashes to compromise telemetry API authentication.
Title openssl_encrypt before 1.4.0 Hardcoded Secret Key
Weaknesses CWE-798
References
Metrics cvssV3_1

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

cvssV4_0

{'score': 8.7, 'vector': 'CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N'}

Weaknesses
  • CWE-798

    Use of Hard-coded Credentials

Sources

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