How severe is GHSA-r67w-f99w-mgxj?

No CVSS score has been assigned to GHSA-r67w-f99w-mgxj yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-r67w-f99w-mgxj?

GHSA-r67w-f99w-mgxj affects the following packages: embedchain (PyPI). Ecosystems affected: PyPI.

How do I fix GHSA-r67w-f99w-mgxj?

Update embedchain to 0.1.57 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-r67w-f99w-mgxj is resolved across your whole dependency graph.

How do I detect GHSA-r67w-f99w-mgxj in my PyPI dependencies?

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

How do I mitigate GHSA-r67w-f99w-mgxj if there is no patch (or I can't update yet)?

Cap what an attacker can consume: apply request size, rate and timeout limits in front of the affected component, and run it with memory and CPU limits so exhaustion degrades one worker rather than the whole service.

How does O3 Security protect against GHSA-r67w-f99w-mgxj?

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

Is GHSA-r67w-f99w-mgxj actively exploited in the wild?

No public exploit code has been indexed for GHSA-r67w-f99w-mgxj 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-r67w-f99w-mgxj?

GHSA-r67w-f99w-mgxj has an EPSS (Exploit Prediction Scoring System) score of 0.8%, placing it in the 54th 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-r67w-f99w-mgxj?

GHSA-r67w-f99w-mgxj is classified as CWE-1333 (CWE-1333). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was GHSA-r67w-f99w-mgxj published, and has it been updated?

GHSA-r67w-f99w-mgxj was published on January 21, 2024 and was last updated on December 6, 2024. 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-r67w-f99w-mgxj — embedchain

Fix: embedchain/embedchain#1122

GHSA-r67w-f99w-mgxj is a CWE-1333 vulnerability in embedchain. A fix is available for embedchain — see the affected versions and patch details below.

ReDoS in Embedchain

Also known asCVE-2024-23732PYSEC-2024-8

Published

Jan 21, 2024

Updated

Dec 6, 2024

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

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

Exploitation Status

No confirmed exploitation observed yet

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-r67w-f99w-mgxj.

EPSS Exploitation Probability

via FIRST.org ↗

0.8%probability of exploitation in next 30 days

Lower Risk0.00%

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

🐍embedchain

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

The JSON loader in Embedchain before 0.1.57 allows a ReDoS (regular expression denial of service) via a long string to json.py.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🐍PyPI	`embedchain`	all versions	0.1.57`pip install --upgrade 'embedchain==0.1.57'`

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for embedchain, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update embedchain to 0.1.57 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-r67w-f99w-mgxj is resolved across your whole dependency graph.
Workarounds
Cap what an attacker can consume: apply request size, rate and timeout limits in front of the affected component, and run it with memory and CPU limits so exhaustion degrades one worker rather than the whole service.
How O3 protects you
O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-r67w-f99w-mgxj can be triaged on real exposure rather than presence alone.

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

Frequently Asked Questions

The JSON loader in Embedchain before 0.1.57 allows a ReDoS (regular expression denial of service) via a long string to json.py.

O3 Security · Impact-Aware SCA

Is GHSA-r67w-f99w-mgxj in your dependencies?

O3 Security finds GHSA-r67w-f99w-mgxj 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