CVE-2026-74893Network attack vectorHinoki check available

Authentication bypass via hardcoded JWT secrets

Published Aug 17, 2026 · Updated Aug 17, 2026

Authentication bypass in jahlives OpenSSL Encrypt before 1.4.0 allows attackers to access APIs by presenting forged JWTs. In the unified server's config.py, KEYSERVER_TOKEN_SECRET and TELEMETRY_TOKEN_SECRET default to known strings that satisfy validate_config() because it checks only secret length, not whether the deployed value is still the shipped default. Exposure requires a deployment that leaves those environment variables unset and an attacker who can read the source code or otherwise learn the defaults; either secret lets forged tokens impersonate any client_id to the keyserver or telemetry APIs.

CVSS severity8.8
High
EPSS probability0.26%
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 attackers to access APIs by presenting forged JWTs. In the unified server's config.py, KEYSERVER_TOKEN_SECRET and TELEMETRY_TOKEN_SECRET default to known strings that satisfy validate_config() because it checks only secret length, not whether the deployed value is still the shipped default. Exposure requires a deployment that leaves those environment variables unset and an attacker who can read the source code or otherwise learn the defaults; either secret lets forged tokens impersonate any client_id to the keyserver or telemetry APIs.

The record

CVE
CVE-2026-74893
Published
Aug 17, 2026
Updated
Aug 17, 2026
Vendor
jahlives
Product
OpenSSL Encrypt
Classifications
CWE-798, T1550.001
Attack vector
network
Privileges
Unavailable

Timeline

How it unfolded

  1. Aug 17, 2026CVE publishedPublication date reported by the CVE source.
  2. Aug 17, 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 privilegesUnavailable in this record.

What is affected?

jahlives · OpenSSL Encryptversion=0 <1.4.0

Published CVSS scores

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

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
PrivilegesUnavailable
Known exploitationUnconfirmed
Public exploitUnconfirmed

Weakness, pattern, technique

CWE-798Use of Hard-coded Credentials
T1550.001Application Access Token

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