Threadlinqs IntelligenceStart free

VulnerabilityCVE-2026-94093Published 2026-09-20

CVE-2026-94093 — DLR-RM stable-baselines3

medium

As of 2026-09-21, CVE-2026-94093 is a MEDIUM-severity vulnerability in DLR-RM stable-baselines3, CVSS v3.1 6.3, EPSS 0.2% (17.8th percentile). No Threadlinqs-tracked threat campaign has been attributed to CVE-2026-94093 as of 2026-09-21; the identifier is re-checked against the Threadlinqs threat corpus on every daily ingest.

CVSS v3.1
6.3/10Medium
EPSS
0.2%Higher than 17.8% of scored CVEs
CISA KEV
NoNot in the KEV catalog
Tracked threats
0None linked yet
Priority
3.9/10Threadlinqs triage score
Published
Updated 2026-09-21
CVSS v3.1 6.3 (MEDIUM) · CVSS v4.0 5.3 · EPSS 0.2% (higher than 17.8% of all scored CVEs) · Priority 3.9/10 · Published 2026-09-20

Last updated:

What is CVE-2026-94093?

A security vulnerability has been detected in DLR-RM stable-baselines3 up to 2.9.0. This affects the function PPO.load/load_replay_buffer/VecNormalize.load of the file save_util.py. Such manipulation leads to deserialization. It is possible to launch the attack remotely. The exploit has been disclosed publicly and may be used. In v2.9.0 the PyTorch tensor load path is hardened (weights_only=True), but that hardening was later reverted on master via PR #1913 "Hotfix: revert loading with weights_only=True" [blocked] to fix PyTorch 1.13 compat - so even the one "safe" path is inconsistent across versions. #2281 was closed as a duplicate of #1831 since both are unsafe pickle deserialization - but #1831's fix (PR #41) only gated the Hugging Face Hub loader in the separate huggingface_sb3 package. This finding covers the core stable_baselines3 load APIs (PPO.load, load_replay_buffer, VecNormalize.load), which have no safe mode or gate and remained exploitable in v2.9.0 until the outstanding hardening (PR #2264) ships.

The record classifies CVE-2026-94093 under weakness classes CWE-502, CWE-20. Its CVSS v3 base vector states that the flaw is reachable remotely over the network, needs no prior authentication, needs a user to take an action first. 1 affected-product entry is recorded, across 1 vendor, listed below. The identifier was first published 15 days ago.

Severity and exploitation probability

CVSS v3.1 base score
6.3 — MEDIUM
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:L/A:L/E:P/RL:X/RC:R
CVSS v4.0 base score
5.3
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:P/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:P
EPSS (FIRST)
0.2% probability of exploitation in the next 30 days, higher than 17.8% of all scored CVEs
CISA KEV
Not listed in the CISA Known Exploited Vulnerabilities catalog
Threadlinqs priority
3.9/10 — a Threadlinqs composite of the CVSS base score, the EPSS percentile and public exploit availability
Published
2026-09-20, last modified 2026-09-21

Is CVE-2026-94093 being exploited?

It currently carries a trending score of 34 in the Threadlinqs vulnerability feed.

Affected products and versions

  • DLR-RM: stable-baselines3

How to fix CVE-2026-94093

No vendor patch reference has been recorded for CVE-2026-94093 in the tracked sources. Follow the references below for a fix, and treat the products listed above as exposed until the vendor states otherwise.

Threat activity tracking CVE-2026-94093

No threat campaign in the Threadlinqs corpus currently references CVE-2026-94093, in its CVE list or as an indicator. The linkage is recomputed from the live corpus on every daily ingest, so this section fills in as soon as a tracked campaign cites the identifier.

Sources

Enriched from CVE.org, FIRST EPSS. Last verified by Threadlinqs on .

Technical analysis

Third-party advisory

Issue tracking and product pages