CVE-2024-10190: Horovod Vulnerable to Command Injection
Affects horovodSource GCVE Database
Not known to be exploited · CVSS 9.8 Critical.
Data as of 27 Oct 2026, 18:29 UTC
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:HExploitation evidence
Disclosed: evidence found.
CVE published 20 Mar 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by 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
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| PyPIhorovod | Affected
| Fixed in– |
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
Users should monitor vendor advisories for updates. Until a fix is available, restrict network access to the Horovod service to trusted users only and consider disabling or isolating the ElasticRendezvousHandler functionality if possible to reduce exposure.
Description
Horovod versions up to and including 0.28.1 contain a critical vulnerability that allows unauthenticated remote code execution. The flaw arises from insecure deserialization of base64-encoded data in the ElasticRendezvousHandler component, enabling attackers to send malicious pickle objects via PUT requests to execute arbitrary code on the server.
References
- nvd.nist.gov/vuln/detail/CVE-2024-10190 (opens in a new tab)
- github.com/horovod/horovod (opens in a new tab)
- github.com/pypa/advisory-database/tree/main/vulns/horovod/PYSEC-2026-355.yaml (opens in a new tab)
- huntr.com/bounties/3e398d1f-70c2-4e05-ae22-f5d66b19a754 (opens in a new tab)
- pypi.org/project/horovod (opens in a new tab)