CVE-2026-74892Network attack vectorHinoki check available

Telemetry API authentication bypass via default secret

Published Aug 17, 2026 · Updated Aug 18, 2026

Authentication bypass in jahlives openssl_encrypt before 1.4.0 allows remote attackers to forge telemetry API authentication via a default secret key. In server/telemetry-server/app/config.py, the standalone telemetry server sets secret_key from the SECRET_KEY environment variable but falls back to the literal string CHANGE_THIS_IN_PRODUCTION, and that value is used for API key hashing. Exposure requires the standalone telemetry server to run with the shipped default instead of an override; the published impact is limited to impersonating API clients against that service.

CVSS severity8.7
High
EPSS probability0.31%
Next 30 days · Sep 16, 2026
Known exploitationUnconfirmed
Based on sourced intelligence
Hinoki checkAvailable
Coverage for this vulnerability

See if you're affected

Explore vulnerability checks for your environment with Hinoki.

Book a demo

Summary

What happened

Authentication bypass in jahlives openssl_encrypt before 1.4.0 allows remote attackers to forge telemetry API authentication via a default secret key. In server/telemetry-server/app/config.py, the standalone telemetry server sets secret_key from the SECRET_KEY environment variable but falls back to the literal string CHANGE_THIS_IN_PRODUCTION, and that value is used for API key hashing. Exposure requires the standalone telemetry server to run with the shipped default instead of an override; the published impact is limited to impersonating API clients against that service.

The record

CVE
CVE-2026-74892
Published
Aug 17, 2026
Updated
Aug 18, 2026
Vendor
jahlives
Product
OpenSSL Encrypt
Classifications
CWE-798
Attack vector
network
Privileges
unauthenticated

Timeline

How it unfolded

  1. Aug 17, 2026CVE publishedPublication date reported by the CVE source.
  2. Aug 18, 2026Record updatedLatest update available in the CVE record.

Exploitability

Present is not the same as exploitable

Compare your product and version with the public record. A matching version still requires validation against your environment.

Is a vulnerable build present?

Compare these published version ranges with your installed build and any vendor patches.

  1. Affected versionversion=0 <1.4.0

What conditions does exploitation require?

Attack vectornetwork
Required privilegesunauthenticated

What is affected?

jahlives · OpenSSL Encryptversion=0 <1.4.0

Published CVSS scores

8.7VulnCheckCVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N
7.5VulnCheckCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

CVSS describes severity. EPSS estimates exploitation probability.

Attacks

What attackers are doing with it

Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.

Daily unique IPsNo honeypot observations are available for this CVE in the selected window.

No observations available

Sep 10, 2026Sep 16, 2026
Latest reporting daySep 16, 2026
Latest daily unique IPsUnavailable
Prior 30-day averageUnavailable
SourceShadowserver honeypots (KEV)
Vectornetwork
Privilegesunauthenticated
Known exploitationUnconfirmed
Public exploitUnconfirmed

Weakness, pattern, technique

CWE-798Use of Hard-coded Credentials

Public exploit references

No public exploit references are available in this record.

Labels summarize the accepted research assessment. They do not indicate a test against your environment.

Technologies

Your stack

See the directory against your own environment.

Your stack

Check the software in your environment

Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.

Book a demo