Skip to main content
VulnerabilityPublished Updated

CVE-2024-23731: Embedchain · Argument Injection

Source CVE Database V5

0

Not known to be exploited · CVSS 9.8 Critical : upgrade to 0.1.57 as a priority.

Data as of 26 Oct 2026, 11:07 UTC

CVSS 3.1 base score
9.8Critical
How severe the flaw is on the 0–10 CVSS scale.
EPSS
1.0% chance of exploitation in 30 days – higher than 64% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 0.1.57
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 21 Jan 2024

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

What to do

Upgrade embedchain/embedchain to 0.1.57.

Affected software

ProductAffectedFixed in
GitHubembedchain/embedchainpkg:github/embedchain/embedchainOther threatsAffected
  • <0.1.57
Fixed in
  • 0.1.57

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

  1. Immediate upgrade: Organizations should promptly update Embedchain to version 0.1.57 or later, where the unsafe use of yaml.load has been addressed, likely replaced with safe_load or equivalent secure parsing methods.
  2. Input validation: Implement strict validation and sanitization of all OpenAPI specification inputs before processing to reduce the risk of malicious payloads.
  3. Network controls: Restrict access to services using Embedchain to trusted networks and authenticated users to reduce exposure.
  4. Monitoring and detection: Deploy monitoring for unusual process behavior or network activity indicative of exploitation attempts, including unexpected code execution or outbound connections.
  5. Incident response readiness: Prepare response plans for potential exploitation scenarios, including system isolation and forensic analysis.
  6. Dependency management: Regularly audit and track third-party components like Embedchain for vulnerabilities and updates.
  7. Use of sandboxing: Run Embedchain processes in isolated environments or containers with minimal privileges to limit impact if exploited.

Description

The OpenAPI loader in Embedchain before 0.1.57 allows attackers to execute arbitrary code, related to the openapi.py yaml.load function argument.

References

Community reviews

Loading reviews…