CVE-2025-10950
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 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.
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 confidenceThe ml-logger server contains an insecure deserialization vulnerability in the Ping Handler function (log_handler) of ml_logger/server.py. The function accepts serialized data via the 'data' argument and deserializes it without proper validation, allowing remote attackers to craft malicious payloads that execute arbitrary code on the server.
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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- Low
- Integrity
- Low
- Availability
- Low
CVSS:3.1/AV:N/AC:L/PR:L/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 installation and versionRun 'pip show ml-logger' or check your package manager for the installed version of the ml-logger package. If installed from source, check the version tag or the version field in setup.py/pyproject.toml.Affected if The installed version is any version of ml-logger that contains the vulnerable server.py with the Ping Handler function (no fixed version confirmed).
-
Locate the vulnerable server.py fileFind the ml_logger/server.py file in your environment. This is typically in the package installation directory or source code repository.Affected if The file exists and contains a 'log_handler' or 'Ping Handler' function that accepts a 'data' parameter for deserialization.
-
Inspect the deserialization implementationOpen ml_logger/server.py and search for the Ping Handler function. Look for usage of unsafe deserialization methods such as pickle.load(), pickle.loads(), yaml.load() with unsafe settings, or similar functions that deserialize data from the 'data' argument without validation.Affected if The code uses pickle, yaml.load(Loader=yaml.FullLoader or no Loader), jsonpickle, or other unsafe deserialization methods on the 'data' parameter without prior validation.
-
Verify input validation is absentIn the same Ping Handler function, check if there is any input validation, schema checking, or type verification performed on the 'data' argument before deserialization.Affected if No validation, schema enforcement, or type checking is performed on the 'data' parameter prior to deserialization.
-
Determine if the Ping Handler is network accessibleCheck your server configuration, firewall rules, or service binding to see if the Ping Handler endpoint (usually /ping or similar) is exposed to network requests.Affected if The Ping Handler endpoint is accessible over the network (even on localhost) without authentication, allowing external input to reach the vulnerable deserialization code.
You are affected if ml-logger is installed with the Ping Handler endpoint accessible and the code uses unsafe deserialization (like pickle) on the 'data' parameter without validation.
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 dataReplace unsafe deserialization (likely pickle) with safe formats like JSON, implement strict input validation, and add authentication/authorization checks to the Ping Handler endpoint. Consider implementing a proper message schema and validating all incoming data before processing.
- Consultation3.0 h
- Implementation6.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 $3,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-10950 — 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-10950 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