# CVE-2025-10952: geyang ml-logger File server.py stream_handler information disclosure

> Remote attackers can exploit a flaw in the stream_handler function to disclose sensitive information from the ml-logger library.

- **Severity:** Medium 6.9 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N/E:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 25 Sep 2025
- **Updated:** 25 Sep 2025
- **Also known as:** GHSA-9x36-c74v-fgr6, PYSEC-2026-1635

## What is CVE-2025-10952?

CVE-2025-10952 is a medium-severity vulnerability in geyang ml-logger, published on 25 Sep 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A security flaw has been discovered in geyang ml-logger up to acf255bade5be6ad88d90735c8367b28cbe3a743. Affected by this issue is the function stream_handler of the file ml_logger/server.py of the component File Handler. Performing manipulation of the argument key results in information disclosure. The attack can be initiated remotely. The exploit has been released to the public and may be exploited. Continious delivery with rolling releases is used by this product. Therefore, no version details of affected nor updated releases are available.

Weakness: CWE-284 (Improper Access Control), CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

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

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-10952?

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

## Is CVE-2025-10952 being exploited?

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

Public exploit code:

- PoC for CVE-2025-10952 — ml-logger unauthenticated arbitrary file read. CVSS 5.3 (github_poc): https://github.com/Khashayarnzk/CVE-2025-10952-ml-logger-AFR

## Fix prompt for AI coding agents

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

What it is: CVE-2025-10952 is a medium-severity vulnerability in geyang ml-logger, published on 25 Sep 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-10952 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-10952/ (Markdown: https://insights.sbomify.com/CVE-2025-10952/index.md)
```

## Sources

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

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