Arbitrary Code Injection Affecting nemo-gym package, versions <0.5.0_rc0_git20260729-r1


Severity

Recommended
low

Based on default assessment until relevant scores are available.

Threat Intelligence

EPSS
0.17% (6th 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-NEMOGYM-21175539
  • published17 Oct 2026
  • disclosed6 Oct 2026

Introduced: 6 Oct 2026

NewCVE-2026-106441  (opens in a new tab)
CWE-94  (opens in a new tab)

How to fix?

Upgrade Chainguard nemo-gym to version 0.5.0_rc0_git20260729-r1 or higher.

NVD Description

Note: Versions mentioned in the description apply only to the upstream nemo-gym package and not the nemo-gym 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. Prior to 1.3.6 and 1.4.0.dev9, Hydra passes Python logging configuration to logging.config.dictConfig() without applying Hydra's target policy to handler class values or formatter, filter, handler, queue, and listener factories. An attacker who controls Hydra logging configuration can therefore select an importable class or factory and cause it to be invoked with the application's privileges, even in versions where instantiate() is protected because the logging path does not use instantiate(). This issue is fixed in versions 1.3.6 and 1.4.0.dev9.