---
id: "CVE-2026-115749"
kind: "vulnerability"
aliases: ["CVE-2026-115749"]
title: "hydra-ray-launcher: config resolver lets attackers import any installed module"
severity: "medium"
cvss: 4.8
epss: 0.00323
exploited: false
status: "open"
category: "package"
products: []
ecosystems: []
tags: ["hydra", "ml-pipelines", "package", "python", "ray"]
not_affected_if: ["fixed-config", "no-untrusted-overrides", "patched-version"]
published_at: "2026-10-23T13:17:09+00:00"
first_seen_at: "2026-10-23T21:57:33+00:00"
updated_at: "2026-10-25T12:38:50+00:00"
sources: [{"source": "nvd", "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-115749", "first_seen_at": "2026-10-23T21:57:33+00:00"}, {"source": "epss", "url": "https://api.first.org/data/v1/epss?cve=CVE-2026-115749", "first_seen_at": "2026-10-25T12:38:50+00:00"}]
---

# hydra-ray-launcher: config resolver lets attackers import any installed module

hydra-ray-launcher passes a configuration value straight into importlib.import_module() through its ray_pkg_version OmegaConf resolver. An attacker who controls config values or command-line overrides can import any installed module and trigger its import-time side effects inside the application process.

_Summary, check and fix written by a model from the sources; labelled as such._

## How to check

- Run `pip show hydra-ray-launcher` to see the installed version.
- Search configs and launch scripts for `ray_pkg_version` interpolations, for example `${ray_pkg_version:...}`.
- Check whether untrusted input reaches Hydra overrides, such as request parameters or CLI arguments built from user data.

## Fix

- Upgrade hydra-ray-launcher to `1.2.2` on the 1.x line, or to `1.4.0rc2` on the 1.4 development line.
- Stop passing untrusted values into Hydra configs and command-line overrides until the upgrade is done.

## Timeline

- 2026-10-23T21:57:33+00:00 nvd https://nvd.nist.gov/vuln/detail/CVE-2026-115749
- 2026-10-25T12:38:50+00:00 epss https://api.first.org/data/v1/epss?cve=CVE-2026-115749

## From the sources

hydra-ray-launcher 1.1.0.dev1 before 1.2.2 and 1.4.0.dev4 before 1.4.0rc2 contains an arbitrary module import vulnerability via the ray_pkg_version OmegaConf resolver passing input to importlib.import_module(). Attackers controlling configuration values or command-line overrides can supply a ray_pkg_version interpolation to import any installed module, triggering its import-time side effects in the application process.

---

_Free to read at a human pace. An API with keys and an MCP server are in preparation; early access: hello@infrastack.ai_