Skip to main content
EPSS 0.4%top 63%

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

0
High
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 hardcoded default JWT signing secrets in config.py that pass validation checks. Attackers with access to source code can forge valid JWT tokens for any client_id to gain authenticated access to keyserver and telemetry APIs.

CVSS v4.0

Score 8.7high

Attack Vector
Network
Attack Complexity
Low
Attack Requirements
None
Privileges Required
Low
User Interaction
None
Vuln. Confidentiality
High
Vuln. Integrity
High
Vuln. Availability
High
Subsq. Confidentiality
None
Subsq. Integrity
None
Subsq. Availability
None
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N

Affected software

jahlives

openssl_encrypt

Affected versions
>=0 <1.4.0
GitHub Actionsmore threats →ai
jahlives/openssl_encrypt
pkg:github/jahlives/openssl_encrypt
Affected versions
<1.4.0

Run on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.

AI-Powered Analysis

Machine-generated threat intelligence

AILast updated: 08/24/2026, 13:34:18 UTC

Technical Analysis

The vulnerability CVE-2026-74893 affects jahlives openssl_encrypt versions prior to 1.4.0. It arises from the presence of hardcoded default JWT signing secrets in the config.py file that pass validation checks. An attacker who can access the source code can exploit this by forging valid JWT tokens for arbitrary client_ids, thereby gaining authenticated access to keyserver and telemetry APIs. This flaw compromises authentication mechanisms relying on JWT tokens.

Potential Impact

Exploitation of this vulnerability allows an attacker with source code access to generate valid JWT tokens for any client_id, resulting in unauthorized authenticated access to keyserver and telemetry APIs. This can lead to unauthorized data access and potential manipulation of telemetry data or keyserver operations.

Mitigation Recommendations

Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. No official fix or patch has been documented as of the published date. Until a patch is available, restrict access to the source code to prevent attackers from obtaining the hardcoded secrets and consider implementing additional authentication controls or rotating JWT signing secrets if possible.

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

Threat ID: 6a82f006bf8831d539c483da

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

Last enriched: 08/24/2026, 13:34:18 UTC

Last updated: 10/01/2026, 15:31:50 UTC

Views: 78

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