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-74891: Use of Hard-coded Credentials in jahlives openssl_encrypt

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

Description

openssl_encrypt versions before 1.4.0 contain hardcoded database credentials in standalone server configuration files. Attackers on the same network can access PostgreSQL databases using well-known default credentials to retrieve sensitive data.

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:42:02 UTC

Technical Analysis

CVE-2026-74891 identifies a vulnerability in the jahlives project’s openssl_encrypt component where versions before 1.4.0 include hardcoded database credentials within standalone server configuration files. This flaw enables attackers with network access to authenticate to PostgreSQL databases using these well-known default credentials, potentially leading to unauthorized data access. The vulnerability has a CVSS 4.0 base score of 8.7, indicating high severity due to network attack vector, no required privileges or user interaction, and high impact on confidentiality.

Potential Impact

Attackers on the same network can leverage the hardcoded credentials to connect to PostgreSQL databases and retrieve sensitive information without needing any privileges or user interaction. This compromises confidentiality of the database contents. There is no indication of impact on integrity or availability.

Mitigation Recommendations

Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Until an official fix is available, avoid deploying affected versions in environments where untrusted network access is possible. Consider restricting network access to the database and replacing default credentials if feasible.

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: 6a82f004bf8831d539c48372

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

Last enriched: 08/17/2026, 11:42:02 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