How severe is GHSA-425g-fjhq-5h92?

No CVSS score has been assigned to GHSA-425g-fjhq-5h92 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-425g-fjhq-5h92?

GHSA-425g-fjhq-5h92 affects the following packages: openssl-encrypt (PyPI). Ecosystems affected: PyPI.

How do I fix GHSA-425g-fjhq-5h92?

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

How do I detect GHSA-425g-fjhq-5h92 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-425g-fjhq-5h92 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-425g-fjhq-5h92?

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

Is GHSA-425g-fjhq-5h92 actively exploited in the wild?

No public exploit code has been indexed for GHSA-425g-fjhq-5h92 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-425g-fjhq-5h92?

GHSA-425g-fjhq-5h92 has an EPSS (Exploit Prediction Scoring System) score of 0.2%, placing it in the 8th 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-425g-fjhq-5h92?

GHSA-425g-fjhq-5h92 is classified as CWE-345 (CWE-345). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was GHSA-425g-fjhq-5h92 published, and has it been updated?

GHSA-425g-fjhq-5h92 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-425g-fjhq-5h92 — openssl-encrypt

Fix: jahlives/openssl_encrypt@6e7f938

GHSA-425g-fjhq-5h92 is a CWE-345 vulnerability in openssl-encrypt. A fix is available for openssl-encrypt — see the affected versions and patch details below.

openssl-encrypt silently skips schema validation when jsonschema library is not installed

Also known asCVE-2026-74875PYSEC-2026-3755

Published

Mar 31, 2026

Updated

Sep 2, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Sep 18, 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.
A successful exploit gives an attacker total control of the affected component, not partial access.
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-425g-fjhq-5h92.

EPSS Exploitation Probability

via FIRST.org ↗

0.2%probability of exploitation in next 30 days

Lower Risk0.00%

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

In openssl_encrypt/modules/json_validator.py at lines 234-238, when the jsonschema library is not installed, all schema validation is silently skipped with only a print warning.

Affected Code

if not JSONSCHEMA_AVAILABLE:
    print(f"Warning: Cannot validate against schema '{schema_name}' - jsonschema library not available")
    return

Additionally, unknown metadata format versions (line 288-293) bypass schema validation entirely, and all schemas use additionalProperties: true allowing arbitrary extra fields.

Impact

An attacker who can influence the Python environment (remove the jsonschema package) or craft metadata with an unknown version number can bypass all schema checks. Malformed or malicious metadata will be accepted without validation.

Recommended Fix

Make jsonschema a required dependency, not optional
Or fail-closed: refuse to process metadata when validation cannot be performed
Reject unknown format versions instead of silently skipping validation
Consider using additionalProperties: false in schemas

Fix

Fixed in commit 6e7f938 on branch releases/1.4.x — validate_against_schema() now raises JSONValidationError when jsonschema is unavailable instead of silently passing; changed print() warning to logging.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-425g-fjhq-5h92 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-425g-fjhq-5h92 can be triaged on real exposure rather than presence alone.

Tailored to GHSA-425g-fjhq-5h92. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

### Summary In `openssl_encrypt/modules/json_validator.py` at **lines 234-238**, when the `jsonschema` library is not installed, all schema validation is silently skipped with only a print warning. ### Affected Code ```python if not JSONSCHEMA_AVAILABLE: print(f"Warning: Cannot validate against schema '{schema_name}' - jsonschema library not available") return ``` Additionally, unknown metadata format versions (line 288-293) bypass schema validation entirely, and all schemas use `additionalProperties: true` allowing arbitrary extra fields. ### Impact An attacker who can influence

O3 Security · Impact-Aware SCA

Is GHSA-425g-fjhq-5h92 in your dependencies?

O3 Security finds GHSA-425g-fjhq-5h92 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