Use of insecure temporary file in Horovod

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS 4.0

8.8 · CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:L/VA:H/SC:N/SI:N/SA:N · score source

EPSS

• CVE-2022-0315: 0.96% estimated exploitation activity in the next 30 days; percentile 61.56 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

Impact The insecure tempfile.mktemp() is used when Horovod is run in an LSF job with jsrun. In that situation, a jsrun rank file is created with mktemp, which could be hijacked by another process to read or manipulate the content. This issue does not impact the use of MPI, Gloo, Spark or Ray. Patches The problem has been fixed in b96ecae4. Workarounds The rank file is not created when bindingargs are provided in the Settings instance. References Please see https://github.com/horovod/horovod/pull/3358 for details. For more information If you have any questions or comments about this advisory: Open an issue in https://github.com/horovod/horovod

Published by the source

29 Mar 2022, 19:18 UTC

Last modified by the source

20 Sep 2024, 21:43 UTC

Source last checked

26 Oct 2026, 13:17 UTC

1. Revision 3 · amended · 26 Oct 2026

   Amended from ghsa record GHSA-47wv-vhj2-g66m

2. Revision 2 · amended · 25 Oct 2026

   Reviewed OSV alias/range/CVSS4 correction; package source scopes and original publication preserved. No customer finding resolved.

3. Revision 1 · created · 24 Oct 2026

   Published from osv record GHSA-47wv-vhj2-g66m

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2022-0315

Advisory: Use of insecure temporary file in Horovod
IDs: CVE-2022-0315, GHSA-47wv-vhj2-g66m
Record: https://patchnext.com/advisories/cve-2022-0315 (revision 3, source checked 26 Oct 2026, 13:17 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 8.8)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: horovod 0.24.0. A vendor fix does not mean a deployment is fixed.

## Affected components
- PyPI horovod: affected < 0.24.0; fixed in 0.24.0

## Suggested inspection (read-only)
- `python -m pip show horovod`: prints the installed version. Run with the environment that serves production active.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on horovod.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://osv.dev/vulnerability/GHSA-47wv-vhj2-g66m (OSV record GHSA-47wv-vhj2-g66m lists affected ranges: PyPI horovod >=0 <0.24.0 (fixed))
- Verified: https://github.com/advisories/GHSA-47wv-vhj2-g66m (GitHub-reviewed advisory GHSA-47wv-vhj2-g66m lists affected ranges: PyPI horovod >=0 <0.24.0)

Commands are suggestions: review each one before running it.