CVE-2025-10950 geyang ml-logger Ping server.py log_handler deserialization

Medium 5.3 Published Updated

Remote attackers can execute arbitrary code via unsafe deserialization in the ml-logger Ping server's log handler.

Exploited in the wild
Not known
Login needed
Any signed-in user
Attackable
Over the internet
Victim action needed
Not needed
Fix
None listed

What is CVE-2025-10950?

CVE-2025-10950 is a medium-severity unsafe deserialization vulnerability in geyang ml-logger, published on 25 Sep 2025. Any signed-in user can exploit it over the network, with no action from the victim.

Official description

A vulnerability was determined in geyang ml-logger up to acf255bade5be6ad88d90735c8367b28cbe3a743. 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.

Weakness: CWE-502, CWE-20

Which versions are affected by CVE-2025-10950?

3 open source packages ship an affected version, including ml-logger.

PackageAffectedFixed in
ml-logger PyPIAll versions to 0.10.36None
ml-logger PyPIAll versions to 0.10.36None
ml-logger PyPIAll versions to 0.10.36None

How do I fix CVE-2025-10950?

No fix has been published for CVE-2025-10950 yet. Limit exposure of the affected software until one is available.

Upgrade, and only deserialise data from trusted sources or with an allow-list of types. More about Unsafe deserialization.

Is CVE-2025-10950 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-10950 exists.

Sources

Also known as GHSA-57hm-8rjv-498w, PYSEC-2026-1633.

Is CVE-2025-10950 in your software?

Upload an SBOM and sbomify checks it against every vulnerability here, every day.

Check your SBOMs for free