CVE-2026-94093 DLR-RM CVE debrief

Who should care

Defenders responsible for systems using DLR-RM stable-baselines3 up to 2.9.0 should verify exposure and assess the need for compensating controls. This includes operators, platform administrators, vulnerability management teams, and security teams who need to prioritize verifying exposure in systems using DLR-RM stable-baselines3 up to 2.9.0 and assessing the need for compensating controls. They should also monitor for potential exploitation attempts and

Why it matters

A security vulnerability in DLR-RM stable-baselines3 up to 2.9.0 leads to deserialization, with the exploit disclosed publicly. Defenders should prioritize verifying exposure and assessing the need for compensating controls.

• Verify exposure in systems using DLR-RM stable-baselines3 up to 2.9.0
• Assess the need for compensating controls
• Monitor for potential exploitation attempts

Technical summary

The vulnerability affects the function PPO.load/load_replay_buffer/VecNormalize.load of the file save_util.py in DLR-RM stable-baselines3 up to 2.9.0, leading to deserialization. The exploit has been disclosed publicly and may be used. In v2.9.0, the PyTorch tensor load path was hardened (weights_only=True), but that hardening was later reverted. The core stable_baselines3 load APIs (PPO.load, load_replay_buffer, VecNormalize.load) have no safe mode or gate and remained exploitable in v2.9.0 until the outstanding hardening ships. This vulnerability allows remote attackers to execute arbitrary code on affected systems, emphasizing the need for defenders to verify exposure and implement compensating controls.

Defensive priority

Defenders should prioritize verifying exposure in systems using DLR-RM stable-baselines3 up to 2.9.0 and assessing the need for compensating controls.

Recommended defensive actions

• Verify exposure in systems using DLR-RM stable-baselines3 up to 2.9.0
• Assess the need for compensating controls
• Monitor for potential exploitation attempts
• Review the supplied official advisory or CVE record to validate affected scope, severity, and vendor guidance
• Plan vendor-supported updates or mitigations through normal change control where exposure is confirmed
• Check relevant monitoring, detection, and logs for exposed assets that need extra review
• Track exceptions, retest remediated assets, and close the item only after evidence is documented

Evidence notes

The CVE record and source metadata indicate a security vulnerability in DLR-RM stable-baselines3 up to 2.9.0. The exploit has been disclosed publicly, but there is no information on known affected versions or remediation.

Sources and references

Methodology and review provenance

AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.