How severe is GHSA-vfgx-5q85-58q3?

No CVSS score has been assigned to GHSA-vfgx-5q85-58q3 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-vfgx-5q85-58q3?

GHSA-vfgx-5q85-58q3 affects the following packages: openssl-encrypt (PyPI). Ecosystems affected: PyPI.

How do I fix GHSA-vfgx-5q85-58q3?

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

How do I detect GHSA-vfgx-5q85-58q3 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-vfgx-5q85-58q3 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-vfgx-5q85-58q3?

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

Is GHSA-vfgx-5q85-58q3 actively exploited in the wild?

No public exploit code has been indexed for GHSA-vfgx-5q85-58q3 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-vfgx-5q85-58q3?

GHSA-vfgx-5q85-58q3 has an EPSS (Exploit Prediction Scoring System) score of 0.3%, placing it in the 17th 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-vfgx-5q85-58q3?

GHSA-vfgx-5q85-58q3 is classified as CWE-338 (CWE-338). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was GHSA-vfgx-5q85-58q3 published, and has it been updated?

GHSA-vfgx-5q85-58q3 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-vfgx-5q85-58q3 — openssl-encrypt

Fix: jahlives/openssl_encrypt@09e96e0

GHSA-vfgx-5q85-58q3 is a CWE-338 vulnerability in openssl-encrypt. A fix is available for openssl-encrypt — see the affected versions and patch details below.

openssl-encrypt has non-cryptographic PRNG used for steganography pixel selection

Also known asCVE-2026-74874PYSEC-2026-3754

Published

Mar 31, 2026

Updated

Sep 2, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

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

EPSS Exploitation Probability

via FIRST.org ↗

0.3%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs17th percentile — riskier than 17% 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

The generate_pseudorandom_sequence() function in openssl_encrypt/plugins/steganography/core/utils.py at lines 89-91 uses Python's random module (Mersenne Twister) for steganographic pixel/sample selection.

Affected Code

random.seed(seed)
sequence = random.sample(range(max_value), min(length, max_value))
return sequence

Additionally, the steganography password is stored as a plain Python string (not SecureBytes) and only 8 bytes (64 bits) of the SHA-256 hash are used for the seed, reducing effective security to 64 bits.

Impact

The Mersenne Twister's state can be recovered from approximately 624 outputs. An attacker who knows or guesses the password can predict the PRNG sequence and determine exactly which pixels contain hidden data, potentially extracting the hidden data without the password.

Recommended Fix

Use HMAC-DRBG or secrets module for cryptographically secure pixel selection
Use full 32-byte SHA-256 output as seed material
Store the password in SecureBytes instead of a plain string

Fix

Fixed in commit 09e96e0 on branch releases/1.4.x — replaced random.seed(hash(password)) with HMAC-SHA256 based CSPRNG (Fisher-Yates shuffle) and numpy Generator with HMAC-derived seeds across all steganography format modules.

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-vfgx-5q85-58q3 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-vfgx-5q85-58q3 can be triaged on real exposure rather than presence alone.

Tailored to GHSA-vfgx-5q85-58q3. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

### Summary The `generate_pseudorandom_sequence()` function in `openssl_encrypt/plugins/steganography/core/utils.py` at **lines 89-91** uses Python's `random` module (Mersenne Twister) for steganographic pixel/sample selection. ### Affected Code ```python random.seed(seed) sequence = random.sample(range(max_value), min(length, max_value)) return sequence ``` Additionally, the steganography password is stored as a plain Python string (not `SecureBytes`) and only 8 bytes (64 bits) of the SHA-256 hash are used for the seed, reducing effective security to 64 bits. ### Impact The Mersenne Twi

O3 Security · Impact-Aware SCA

Is GHSA-vfgx-5q85-58q3 in your dependencies?

O3 Security finds GHSA-vfgx-5q85-58q3 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