How severe is GHSA-h3m5-p59h-x88p?

No CVSS score has been assigned to GHSA-h3m5-p59h-x88p yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-h3m5-p59h-x88p?

GHSA-h3m5-p59h-x88p affects the following packages: openssl-encrypt (PyPI). Ecosystems affected: PyPI.

How do I fix GHSA-h3m5-p59h-x88p?

Update openssl-encrypt to 1.4.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-h3m5-p59h-x88p is resolved across your whole dependency graph.

How do I detect GHSA-h3m5-p59h-x88p in my PyPI dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for openssl-encrypt, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate GHSA-h3m5-p59h-x88p if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

How does O3 Security protect against GHSA-h3m5-p59h-x88p?

O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-h3m5-p59h-x88p can be triaged on real exposure rather than presence alone.

Is GHSA-h3m5-p59h-x88p actively exploited in the wild?

No public exploit code has been indexed for GHSA-h3m5-p59h-x88p yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for GHSA-h3m5-p59h-x88p?

GHSA-h3m5-p59h-x88p has an EPSS (Exploit Prediction Scoring System) score of 0.2%, placing it in the 14th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is GHSA-h3m5-p59h-x88p?

GHSA-h3m5-p59h-x88p is classified as CWE-214 (CWE-214). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was GHSA-h3m5-p59h-x88p published, and has it been updated?

GHSA-h3m5-p59h-x88p was published on March 31, 2026 and was last updated on September 2, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐍 PyPI

Not in CISA KEV

GHSA-h3m5-p59h-x88p — openssl-encrypt

Fix: jahlives/openssl_encrypt@e78a366

GHSA-h3m5-p59h-x88p is a CWE-214 vulnerability in openssl-encrypt. A fix is available for openssl-encrypt — see the affected versions and patch details below.

openssl-encrypt has visible password in process list via --password CLI argument

Also known asCVE-2026-74873PYSEC-2026-3753

Published

Mar 31, 2026

Updated

Sep 2, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Sep 19, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

No confirmed exploitation observed yet

CISA assesses this as automatable — exploitation doesn’t require manual, per-target effort, which raises the odds of mass scanning and opportunistic attacks.
CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for GHSA-h3m5-p59h-x88p.

EPSS Exploitation Probability

via FIRST.org ↗

0.2%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs14th percentile — riskier than 14% of all scored CVEsHighest risk

EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.

Real-World Exposure

1 pkg affected

🐍openssl-encrypt

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects PyPI packages — download data is not available via public APIs for these ecosystems.

Description

Summary

Passwords passed via the --password / -p CLI argument in openssl_encrypt/modules/crypt_cli_subparser.py at lines 150-154 are visible to any user on the system via ps aux or /proc/[pid]/cmdline.

Affected Code

subparser.add_argument(
    "--password", "-p",
    help="Password (will prompt if not provided, or use CRYPT_PASSWORD environment variable)",
)

Similarly, --keystore-password exposes the keystore password.

Impact

On multi-user systems, any user can observe the encryption password by listing processes. The CRYPT_PASSWORD environment variable alternative is also visible via /proc/[pid]/environ (though with slightly restricted access).

Recommended Fix

Document the security implications prominently
Recommend interactive prompting (already supported) as the secure default
Consider supporting password file descriptors (--password-fd) or reading from stdin
Consider marking the argument as deprecated in favor of interactive prompting

Fix

Fixed in commit e78a366 on branch releases/1.4.x — added --password-file and --password-fd arguments; added OPENSSL_ENCRYPT_PASSWORD env var support; --password now emits deprecation warning.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🐍PyPI	`openssl-encrypt`	all versions	1.4.0`pip install --upgrade 'openssl-encrypt==1.4.0'`

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for openssl-encrypt, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update openssl-encrypt to 1.4.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-h3m5-p59h-x88p is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-h3m5-p59h-x88p can be triaged on real exposure rather than presence alone.

Tailored to GHSA-h3m5-p59h-x88p. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

### Summary Passwords passed via the `--password` / `-p` CLI argument in `openssl_encrypt/modules/crypt_cli_subparser.py` at **lines 150-154** are visible to any user on the system via `ps aux` or `/proc/[pid]/cmdline`. ### Affected Code ```python subparser.add_argument( "--password", "-p", help="Password (will prompt if not provided, or use CRYPT_PASSWORD environment variable)", ) ``` Similarly, `--keystore-password` exposes the keystore password. ### Impact On multi-user systems, any user can observe the encryption password by listing processes. The `CRYPT_PASSWORD` environment

O3 Security · Impact-Aware SCA

Is GHSA-h3m5-p59h-x88p in your dependencies?

O3 Security finds GHSA-h3m5-p59h-x88p across PyPI dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.

Scan my dependencies How O3 SCA works