Homepage

Use of Externally-Controlled Input to Select Classes or Code ('Unsafe Reflection') Affecting nemo-rl-cuda-13.0 package, versions <0.7.0-r4

Severity

 Recommended
low

Based on default assessment until relevant scores are available.

Threat Intelligence

EPSS
0.46% (39th percentile)

Do your applications use this vulnerable package?

In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.

Test your applications
  • Snyk IDSNYK-CHAINGUARDLATEST-NEMORLCUDA130-21092270
  • published16 Oct 2026
  • disclosed6 Oct 2026
Report a new vulnerability Found a mistake?

Introduced: 6 Oct 2026

NewCVE-2026-106439  (opens in a new tab)
CWE-470  (opens in a new tab)
CWE-693  (opens in a new tab)

How to fix?

Upgrade Chainguard nemo-rl-cuda-13.0 to version 0.7.0-r4 or higher.

NVD Description

Note: Versions mentioned in the description apply only to the upstream nemo-rl-cuda-13.0 package and not the nemo-rl-cuda-13.0 package as distributed by Chainguard. See How to fix? for Chainguard relevant fixed versions and status.

Hydra is a framework for elegantly configuring complex applications. From 1.3.4 until 1.3.7 and 1.4.0.dev10, Hydra stores legacy instantiate target blocklists and related execution-policy collections in mutable module-level state. An attacker who controls multiple sibling target entries can resolve hydra._internal.target_policy.UNCONTROLLED_EXECUTION_TARGETS.discard through instantiate(), remove a denied target, and then invoke that target because sibling nodes are processed in insertion order against the same modified policy. The mutation persists in process-global state and can enable code execution with the application's privileges, while a narrow execution whitelist supplied by trusted Python code is not bypassed by the reported direct mutation path. This issue is fixed in versions 1.3.7 and 1.4.0.dev10.