CVE-2025-10951
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 vulnerability was identified in geyang ml-logger up to acf255bade5be6ad88d90735c8367b28cbe3a743. Affected by this vulnerability is the function log_handler of the file ml_logger/server.py. Such manipulation of the argument File leads to path traversal. It is possible to launch the attack remotely. The exploit is publicly available and might be used. This product takes the approach of rolling releases to provide continious delivery. Therefore, version details for affected and updated releases are not 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 vulnerability exists in the ml-logger project's server.py file, specifically in the log_handler function. Attackers can manipulate the File argument to access files outside the intended directory, potentially exposing sensitive system files or application data. The vulnerability is remotely exploitable and public exploits are available.
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
- Low
- Availability
- Low
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L
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.
-
Identify ml-logger installationRun 'pip show ml-logger' or check your Python environment for the ml-logger package installation status and note the installed versionAffected if ml-logger is installed and the version has not been patched against path traversal in server.py
-
Locate the server.py fileFind the server.py file in the ml-logger package directory (typically in site-packages/ml-logger/) and verify it contains a log_handler functionAffected if server.py exists and contains a log_handler function that processes a File argument without proper path validation
-
Examine the log_handler function implementationOpen server.py and inspect the log_handler function for path traversal vulnerabilities - specifically look for file operations using user-controlled File argument without sanitization checks for '../' sequences or absolute path validationAffected if The log_handler function uses the File parameter directly in file operations (such as open(), os.path.join(), or similar) without validating the path is within an allowed directory
-
Determine if the log_handler is exposed via network serviceCheck if the ml-logger server is running and the log_handler endpoint is accessible over the network (typically on a port like 5000 or 8080)Affected if The ml-logger server is running and exposed on a network interface, allowing remote attackers to supply malicious File arguments
-
Test for path traversal vulnerabilityIf the server is accessible, send a request to the log_handler endpoint with a File argument containing traversal sequences like '../../etc/passwd' or '../../../etc/hostname' to verify if the application returns files outside the intended directoryAffected if The server returns file contents from paths outside the designated log directory when traversal sequences are provided
You are affected if ml-logger is installed, server.py contains the log_handler function with unsanitized File argument handling, and the server is accessible to process malicious path traversal requests.
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 strict input validation and sanitization for file paths in the log_handler function, ensuring paths are restricted to an allowed directory whitelist and preventing traversal sequences like '../' from reaching the filesystem.
- Consultation3.0 h
- Implementation2.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,832.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-10951 — 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-10951 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