CVE-2025-10952
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedA 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceA path traversal or insecure direct object reference vulnerability exists in the ml-logger's stream_handler function in ml_logger/server.py. By manipulating the 'key' argument, an attacker can access files or data they should not have access to, leading to information disclosure. The vulnerability is in the File Handler component and can be exploited remotely.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- Low
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Check ml-logger package versionRun 'pip show ml-logger' or 'pip list | grep ml-logger' to identify the installed versionAffected if The installed version falls within any affected version range (compare to vendor-advisory versions when available)
-
Locate the stream_handler source fileFind ml_logger/server.py in your environment using 'find / -path "*/ml_logger/server.py" 2>/dev/null' or checking the package installation pathAffected if The file exists and contains the stream_handler function definition
-
Verify File Handler is enabledCheck your ml-logger configuration files or initialization code for File Handler setup (look for 'stream_handler', 'file_handler', or similar handler configurations)Affected if File Handler component is configured and active in your deployment
-
Inspect key parameter handling in stream_handlerExamine the stream_handler function code in ml_logger/server.py - look for how the 'key' argument is processed and whether it is used in file path operations without validationAffected if The 'key' parameter is used directly in file operations (e.g., open(), os.path.join()) without proper sanitization or authorization checks
-
Test for path traversal exposureIf the endpoint is accessible, attempt a request with 'key' values like '../' or absolute paths to see if unauthorized file access is possible (e.g., '?key=../../../etc/passwd')Affected if The application returns file contents outside the intended directory or exposes sensitive files
You are affected if ml-logger with the vulnerable stream_handler is deployed, File Handler is enabled, and the 'key' parameter is not properly validated before use in file operations.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataImplement proper authorization and input validation on the 'key' parameter in the stream_handler function to ensure users can only access resources they are authorized to view. Validate that the requested key matches the user's permissions before returning any file data.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-10952 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-10952 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data