Deep Lake Kaggle command injection

published 2024-07-04 2 y ago modified 2026-06-17 4 mo ago also EUVD-2024-47985

cvss: 8.1; version 3.1, CNA
cisa kev: Not listed; not in CISA's catalog
epss: 1.3%; EPSS 1.3% chance of exploitation in 30 days, percentile 71%
public exploits: 0; none known

Command injection when ingesting a remote Kaggle dataset due to a lack of input sanitization in the ingest_kaggle() API

Patch / fix

links 1

github.com/activeloopai/deeplake#2876 pull request

CISA SSVC

Exploitation: Proof of concept is public
Automatable: no
Technical impact: total
Assessed: 2 y ago (2024-07-05)

Exploit prediction

1.32% chance of exploitation in the next 30 days, higher than 71% of all scored CVEs (FIRST EPSS, 2026-11-08).

CVSS scores

assigned by	version	score	vector
CNA	3.1	8.1	CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H

Affected products

deeplake deeplake

Classification

Weakness

CWE-78 Improper Neutralization of Special Elements used in an OS Command
CWE-94 Improper Control of Generation of Code

References

github.com /activeloopai/deeplake/pull/2876
patch
research.jfrog.com /vulnerabilities/deeplake-kaggle-command-injection-jfsa-2024-001035320/
third-party-advisory

Sources

CVE List CVE-2024-6507
NVD CVE-2024-6507

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.

Summary