ml-logger file handler allows reading arbitrary files

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS 4.0

5.5 · 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 · score source

EPSS

• CVE-2025-10952: 0.54% estimated exploitation activity in the next 30 days; percentile 45.57 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

A security flaw has been discovered in geyang ml-logger up to acf255bade5be6ad88d90735c8367b28cbe3a743. Affected by this issue is the function streamhandler of the file mllogger/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.

Published by the source

25 Sep 2025, 18:30 UTC

Last modified by the source

7 Jul 2026, 17:56 UTC

Source last checked

26 Oct 2026, 13:35 UTC

1. Revision 3 · amended · 26 Oct 2026

   Amended from ghsa record GHSA-9x36-c74v-fgr6

2. Revision 2 · amended · 24 Oct 2026

   Reviewed OSV alias/range/CVSS4 correction; package source scopes and original publication preserved. No customer finding resolved.

3. Revision 1 · created · 24 Oct 2026

   Published from osv record GHSA-9x36-c74v-fgr6

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2025-10952

Advisory: ml-logger file handler allows reading arbitrary files
IDs: CVE-2025-10952, GHSA-9x36-c74v-fgr6
Record: https://patchnext.com/advisories/cve-2025-10952 (revision 3, source checked 26 Oct 2026, 13:35 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 5.5)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor response not established. A vendor fix does not mean a deployment is fixed.

## Affected components
- PyPI ml-logger: affected <= 0.10.36

## Suggested inspection (read-only)
- `python -m pip show ml-logger`: prints the installed version. Run with the environment that serves production active.

## Supported action
No complete vendor fix is recorded. Follow the primary source's mitigation guidance and check this record again before closing anything.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on ml-logger.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://osv.dev/vulnerability/GHSA-9x36-c74v-fgr6 (OSV record GHSA-9x36-c74v-fgr6 lists affected ranges: PyPI ml-logger >=0 <=0.10.36)
- Verified: https://github.com/advisories/GHSA-9x36-c74v-fgr6 (GitHub-reviewed advisory GHSA-9x36-c74v-fgr6 lists affected ranges: PyPI ml-logger >=0 <=0.10.36)

Commands are suggestions: review each one before running it.