CVE-2024-10190: horovod/horovod · Deserialization of Untrusted Data
Affects horovod/horovodSource CVE Database V5
Not known to be exploited · CVSS 9.8 Critical : upgrade to 0.28.2 as a priority.
Data as of 25 Oct 2026, 19:02 UTC
- EPSS
- 1.1% chance of exploitation in 30 days – higher than 66% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 0.28.2
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 2026-10-25.
What to do
Upgrade horovod to 0.28.2.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
PyPIhorovodpkg:pypi/horovodOther threats | 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
1. Immediately restrict network access to Horovod services, especially the ElasticRendezvousHandler endpoint, using firewalls or network segmentation to limit exposure to trusted hosts only. 2. Implement strict input validation and filtering on incoming PUT requests to detect and block suspicious base64-encoded payloads that could contain malicious pickle objects. 3. Monitor logs for unusual PUT requests or deserialization attempts and set up alerts for anomalous activity targeting the KVStoreHandler endpoints. 4. Where possible, disable or replace the use of cloudpickle deserialization in Horovod workflows until a patch is available. 5. Deploy runtime application self-protection (RASP) or endpoint detection and response (EDR) tools to detect and prevent execution of unauthorized code on servers running Horovod. 6. 7. Conduct a thorough security review of all machine learning infrastructure to identify and remediate similar deserialization risks. 8. Educate development and operations teams about the dangers of insecure deserialization and enforce secure coding practices in AI/ML pipelines.
Description
Horovod versions up to and including v0.28.1 are vulnerable to unauthenticated remote code execution. The vulnerability is due to improper handling of base64-encoded data in the `ElasticRendezvousHandler`, a subclass of `KVStoreHandler`. Specifically, the `_put_value` method in `ElasticRendezvousHandler` calls `codec.loads_base64(value)`, which eventually invokes `cloudpickle.loads(decoded)`. This allows an attacker to send a malicious pickle object via a PUT request, leading to arbitrary code execution on the server.