Skip to main content
Press slash or control plus K to focus the search. Use the arrow keys to navigate results and press enter to open a threat.
Reconnecting to live updates…

CVE-2026-74892: Use of Hard-coded Credentials in jahlives openssl_encrypt

0
High
VulnerabilityCVE-2026-74892cvecve-2026-74892
Published: 08/17/2026 (08/17/2026, 11:04:55 UTC)
Source: CVE Database V5
Vendor/Project: jahlives
Product: openssl_encrypt

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.

CVSS v4.0

Score 8.7high

Attack Vector
Network
Attack Complexity
Low
Attack Requirements
None
Privileges Required
None
User Interaction
None
Vuln. Confidentiality
High
Vuln. Integrity
None
Vuln. Availability
None
Subsq. Confidentiality
None
Subsq. Integrity
None
Subsq. Availability
None
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

AI-Powered Analysis

Machine-generated threat intelligence

AILast updated: 08/17/2026, 11:41:56 UTC

Technical Analysis

The vulnerability CVE-2026-74892 affects versions of jahlives' openssl_encrypt prior to 1.4.0. A hardcoded default secret key is embedded in the standalone telemetry server configuration and is used for hashing API keys. This predictable secret allows attackers to forge or predict valid API key hashes, thereby bypassing authentication controls on the telemetry API. The CVSS 4.0 score is 8.7, indicating high severity with network attack vector, low attack complexity, no privileges or user interaction required, and high impact on confidentiality.

Potential Impact

Successful exploitation allows attackers to compromise telemetry API authentication by predicting or forging API key hashes. This can lead to unauthorized access to telemetry data or functionality protected by the API keys. The vulnerability does not require privileges or user interaction and can be exploited remotely over the network.

Mitigation Recommendations

Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Since no official fix or patch links are provided, users should monitor the vendor's announcements for updates. Until a fix is available, avoid using the vulnerable versions in sensitive environments or consider mitigating exposure by restricting network access to the telemetry API.

Pro Console: star threats, build custom feeds, automate alerts via Slack, email & webhooks.Upgrade to Pro

Technical Details

Data Version
5.2
Assigner Short Name
VulnCheck
Date Reserved
2026-08-17T10:42:40.455Z
Cvss Version
4.0
State
PUBLISHED
Remediation Level
null

Threat ID: 6a82f006bf8831d539c483d6

Added to database: 08/17/2026, 11:27:02 UTC

Last enriched: 08/17/2026, 11:41:56 UTC

Last updated: 08/17/2026, 13:23:06 UTC

Views: 4

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.

Please log in to the Console to use AI analysis features.

Need more coverage?

Upgrade to Pro Console for AI refresh and higher limits.

For incident response and remediation, OffSeq services can help resolve threats faster.

Latest Threats

Breach by OffSeqOFFSEQFRIENDS — 25% OFF

Check if your credentials are on the dark web

Instant breach scanning across billions of leaked records. Free tier available.

Scan now
OffSeq TrainingCredly Certified

Lead Pen Test Professional

Technical5-day eLearningPECB Accredited
View courses