CVE-2026-74892: Use of Hard-coded Credentials in jahlives openssl_encrypt
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.
AI Analysis
Technical Summary
CVE-2026-74892 describes a security vulnerability in the jahlives project's openssl_encrypt component prior to version 1.4.0. The vulnerability arises from the use of a hardcoded default secret key in the telemetry server configuration, which is used for hashing API keys. An attacker aware of this default key can generate or predict valid API key hashes, thereby bypassing authentication controls for the telemetry API. The CVSS 4.0 base score is 8.7, indicating a high severity with network attack vector, low attack complexity, no privileges required, no user interaction, and high impact on confidentiality.
Potential Impact
The vulnerability enables attackers to compromise telemetry API authentication by forging or predicting API key hashes due to the hardcoded secret key. This can lead to unauthorized access to telemetry data or functionality protected by the API keys. There is no indication of privilege escalation or impact on integrity or availability. No known exploits in the wild have been reported.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Since no official fix or patch is indicated, users should monitor the vendor's announcements for updates. Until a fix is available, avoid deploying vulnerable versions in sensitive environments or consider mitigating exposure by restricting access to the telemetry API.
CVE-2026-74892: Use of Hard-coded Credentials in jahlives 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
Affected software
jahlives
openssl_encrypt
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
CVE-2026-74892 describes a security vulnerability in the jahlives project's openssl_encrypt component prior to version 1.4.0. The vulnerability arises from the use of a hardcoded default secret key in the telemetry server configuration, which is used for hashing API keys. An attacker aware of this default key can generate or predict valid API key hashes, thereby bypassing authentication controls for the telemetry API. The CVSS 4.0 base score is 8.7, indicating a high severity with network attack vector, low attack complexity, no privileges required, no user interaction, and high impact on confidentiality.
Potential Impact
The vulnerability enables attackers to compromise telemetry API authentication by forging or predicting API key hashes due to the hardcoded secret key. This can lead to unauthorized access to telemetry data or functionality protected by the API keys. There is no indication of privilege escalation or impact on integrity or availability. No known exploits in the wild have been reported.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Since no official fix or patch is indicated, users should monitor the vendor's announcements for updates. Until a fix is available, avoid deploying vulnerable versions in sensitive environments or consider mitigating exposure by restricting access to the telemetry API.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- VulnCheck
- Date Reserved
- 2026-08-17T10:42:40.455Z
- Cvss Version
- 4.0
- State
- PUBLISHED
Threat ID: 6a82f006bf8831d539c483d6
Added to database: 08/17/2026, 11:27:02 UTC
Last enriched: 08/24/2026, 13:10:39 UTC
Last updated: 10/01/2026, 15:31:50 UTC
Views: 65
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
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
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.