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.
Published: 2026-08-17
Score: 8.7 High
EPSS: n/a
KEV: No
Impact: n/a
Action: n/a
AI Analysis

Impact

openssl_encrypt versions prior to 1.4.0 embed hard‑coded PostgreSQL credentials in server configuration files. An attacker who can reach the same network segment can use those predictable defaults to log in as a database user and read or modify stored data. The flaw primarily jeopardizes data confidentiality and, if the compromised account has higher privileges, could lead to broader system impact.

Affected Systems

The issue affects the jahlives:openssl_encrypt product and all its releases before the 1.4.0 update. Systems running any older version that deploys the bundled configuration files are vulnerable. No specific version range is listed beyond "before 1.4.0.",

Risk and Exploitability

The CVSS score of 8.7 classifies this vulnerability as High severity. Exploitation requires the attacker to be on the same local network where the bundled configuration files are used to connect to PostgreSQL. EPSS data is not available, and the vulnerability is currently not listed in the CISA KEV catalog, suggesting limited known exploitation. The attack path involves sending a standard login request to the PostgreSQL server using the exposed default credentials, which, if successful, grants read or write privileges according to the account’s configured rights.

Generated by OpenCVE AI on August 17, 2026 at 13:32 UTC.

Remediation

No vendor fix or workaround currently provided.

OpenCVE Recommended Actions

  • Apply the official patch by upgrading jahlives:openssl_encrypt to version 1.4.0 or newer. If the project is no longer maintained, consider replacing it with an actively maintained alternative or manually removing the hardcoded credentials.
  • After upgrading or if an upgrade is not immediately possible, locate the bundled configuration files and remove or replace the hard‑coded database credentials; then set strong, unique passwords for all PostgreSQL accounts.
  • Limit exposure of the PostgreSQL service to trusted hosts only by configuring firewalls, VPNs, or network segmentation so that the database is not reachable from public or untrusted network segments.

Generated by OpenCVE AI on August 17, 2026 at 13:32 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories yet.

History

Mon, 17 Aug 2026 11:15:00 +0000

Type Values Removed Values Added
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.
Title openssl_encrypt before 1.4.0 Hardcoded Database Credentials
Weaknesses CWE-798
References
Metrics cvssV3_1

{'score': 9.8, 'vector': 'CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H'}

cvssV4_0

{'score': 8.7, 'vector': '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'}


Subscriptions

No data.

cve-icon MITRE

Status: PUBLISHED

Assigner: VulnCheck

Published:

Updated: 2026-08-17T15:30:32.467Z

Reserved: 2026-08-17T10:42:40.455Z

Link: CVE-2026-74891

cve-icon Vulnrichment

No data.

cve-icon NVD

Status : Received

Published: 2026-08-17T11:16:44.120

Modified: 2026-08-17T11:16:44.120

Link: CVE-2026-74891

cve-icon Redhat

No data.

cve-icon OpenCVE Enrichment

Updated: 2026-08-17T13:45:04Z

Weaknesses
  • CWE-798

    Use of Hard-coded Credentials