CVE-2025-10950: PYSEC-2026-1633 - ml-logger deserialization vulnerability

CVE-2025-10950 · Severity: low · CVSS 3.1 · Published 2026-07-07

ml-logger deserialization vulnerability

Technologies: ml-logger (PyPI). Vendors: PyPI.

Quick answers

Is CVE-2025-10950 exploited in the wild?
No. Junglewise Threat Intelligence has no report of CVE-2025-10950 being exploited in the wild.
How severe is CVE-2025-10950?
Low severity, with a CVSS score of 3.1, published 7 July 2026.
Which products and versions are affected?
ml-logger (PyPI) ECOSYSTEM:introduced=0,last_affected=0.10.36.
Is there a fix for CVE-2025-10950?
No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
Am I affected by CVE-2025-10950?
Check whether you run ml-logger (PyPI) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

Affected products

  • ml-logger (PyPI) ECOSYSTEM:introduced=0,last_affected=0.10.36

Identifiers

  • CVE-2025-10950
  • GHSA-57hm-8rjv-498w
  • PYSEC-2026-1633

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.