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

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

- **Severity:** Medium 5.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 25 Sep 2025
- **Updated:** 25 Sep 2025
- **Also known as:** GHSA-57hm-8rjv-498w, PYSEC-2026-1633

## 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 (Deserialization of Untrusted Data), CWE-20 (Improper Input Validation)

## Which versions are affected by CVE-2025-10950?

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


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `ml-logger` | PyPI | All versions to 0.10.36 | None |
| `ml-logger` | PyPI | All versions to 0.10.36 | None |
| `ml-logger` | PyPI | All versions to 0.10.36 | None |

## 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.

## Is CVE-2025-10950 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-10950 and fix it if it is affected.

What it is: 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.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-10950 exists.

Affected packages and fixed versions:
- ml-logger (PyPI): affected all versions up to 0.10.36; no fix listed
- ml-logger (PyPI): affected all versions up to 0.10.36; no fix listed
- ml-logger (PyPI): affected all versions up to 0.10.36; no fix listed

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-10950/ (Markdown: https://insights.sbomify.com/CVE-2025-10950/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-10950
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-10950
- OSV: https://osv.dev/vulnerability/CVE-2025-10950

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-10950/
Summaries are generated and may contain mistakes; the official description above is the record.