ml-logger deserialization vulnerability
A vulnerability was determined in geyang ml-logger 0.10.36 and prior. Affected is the function log_handler of the file ml_logger/server.py of the component Ping Handler. This manipulation of the argument data causes deserialization. It is possible to initiate the attack remotely. The exploit has been publicly disclosed and may be utilized. This product is using a rolling release to provide continious delivery. Therefore, no version details for affected nor updated releases are available.
Affected software
Click a technology to see all vulnerabilities affecting it.
| Platform | Package | Vulnerable versions | Fixed in |
|---|---|---|---|
| Python (PyPI) | ml-logger | <= 0.10.36 | no fix |
References
- https://nvd.nist.gov/vuln/detail/CVE-2025-10950
- https://github.com/geyang/ml-logger/issues/72
- https://github.com/geyang/ml-logger
- https://vuldb.com/?ctiid.325820
- https://vuldb.com/?id.325820
- https://vuldb.com/?submit.652461
- https://pypi.org/project/ml-logger
- https://github.com/advisories/GHSA-57hm-8rjv-498w
- CVSS vector
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L- Weakness (CWE)
CWE-20, CWE-502- Platform
- Python (PyPI)
- Package
ml-logger- Disclosed
- 25.09.2025
- Updated
- 11.10.2026 13:18
Sources and licenses
OSV / GitHub Advisory Database - PYSEC-2026-1633 - PyPA Advisory Database; CC BY 4.0
OSV / GitHub Advisory Database - GHSA-57hm-8rjv-498w - CC BY 4.0
Vulnerability history: ml-logger
All published vulnerabilities of this package (Python (PyPI)), newest first. Shows whether this is a one-off slip or a package that needs watching.
- Total entries
- 3
- First → latest
- 09.2025 09.2025
- Without a fix
- 3
- Exploited in attacks
- 0
Severity breakdown
- Medium 2
- Low 1
Disclosures per year
- 2025: 3
- 2026: 0
-
ml-logger deserialization vulnerability this entry
Know which vulnerabilities affect your application
With the DockRay integration and software inventory enabled, DockRay checks reported component versions against known vulnerabilities and notifies you about confirmed matches. Coverage depends on the supported technology and available advisory data.