# 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...

Advisory record · `GHSA-v4vm-4xf2-fhqj`

- **Identifiers:** `GHSA-v4vm-4xf2-fhqj` · `CVE-2026-74891` · `PYSEC-2026-3767`
- **State:** Confirmed
- **Severity:** CVSS 8.7 High
- **Critical:** No
- **Weakness (CWE):** [CWE-798](https://cwe.mitre.org/data/definitions/798.html)
- **Tags:** [Hard-coded credentials](https://agentprime.io/advisories/tag/hard-coded-credentials.md)
- **Published:** 17 Aug 2026
- **Updated:** 2 Sept 2026
- **Reviewed by a person:** No

Published by the GitHub Advisory Database at 17 Aug 2026, 11:16 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

## Affected packages

- `openssl-encrypt` (PyPI): affected `<1.4.0`; fixed in `1.4.0`

## Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

> openssl-encrypt versions before 1.4.0 ship standalone server configuration files with hardcoded database credentials. An attacker on the same network can use these well-known default credentials to access PostgreSQL databases and retrieve sensitive data. Upgrade to openssl-encrypt 1.4.0 or later.

Written 5 Nov 2026.

## Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

## Severity and exploitation

- 8.7 High, CVSS 4.0: `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`, from CNA (VulnCheck)

- **CISA KEV:** Not listed.
- **EPSS:** 0.0052, the 44th percentile, on 8 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

## Timeline

- 31 Oct 2026, 14:38 UTC: First seen by agentprime
- 31 Oct 2026, 14:38 UTC: [Confirmed by OSV](https://osv.dev/vulnerability/PYSEC-2026-3767)

## Sources

- [GitHub Advisory Database: GHSA-v4vm-4xf2-fhqj](https://github.com/advisories/GHSA-v4vm-4xf2-fhqj)
- [OSV: GHSA-v4vm-4xf2-fhqj](https://osv.dev/vulnerability/GHSA-v4vm-4xf2-fhqj)
- <https://github.com/jahlives/openssl_encrypt/security/advisories/GHSA-v4vm-4xf2-fhqj>
- <https://www.vulncheck.com/advisories/openssl-encrypt-before-hardcoded-database-credentials>

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.

## Check whether this affects you

A Match means an installed version is in the affected range above. Most don’t affect the app; agentprime hasn’t analysed this one yet.

- With the agentprime MCP server (<https://api.agentprime.io/mcp>), ask your agent to check the project: `check_lockfile` sends a lockfile, `check_packages` a list of installed packages, and both return the Matches and the upgrades that clear them. `get_advisory` returns this record. Setup: <https://agentprime.io/mcp.md>
- In a browser: <https://agentprime.io/check/> reads your lockfile in the browser, never uploading it.
- Whether it touches your code, with file and line: the Claude Code plugin, <https://agentprime.io/plugin.md>
- As JSON: <https://api.agentprime.io/v1/advisories/GHSA-v4vm-4xf2-fhqj>, or `POST https://api.agentprime.io/v1/match` with your packages (<https://agentprime.io/api.md>)

---

The web page: <https://agentprime.io/advisories/GHSA-v4vm-4xf2-fhqj/>. Everything for agents: <https://agentprime.io/llms.txt>.