Ml-Logger - CraftedSignal Threat Feedhttps://feed.craftedsignal.io/products/ml-logger/Trending threats, MITRE ATT&CK coverage, and detection metadata. Fed continuously.Hugoenhello@craftedsignal.iohello@craftedsignal.ioWed, 26 Aug 2026 05:02:51 +0000https://feed.craftedsignal.io/favicon-32x32.pngCraftedSignal Threat Feedhttps://feed.craftedsignal.io/3232https://feed.craftedsignal.io/favicon.svgUnauthenticated Path Traversal in geyang/ml-loggerhttps://feed.craftedsignal.io/briefs/2026-08-cve-2025-10951/Wed, 26 Aug 2026 05:02:51 +0000hello@craftedsignal.iohttps://feed.craftedsignal.io/briefs/2026-08-cve-2025-10951/An unauthenticated path traversal vulnerability (CVE-2025-10951) in the geyang/ml-logger library enables attackers to perform arbitrary file access via the log_handler and stream_handler components.CVE-2025-10951 is an unauthenticated path traversal vulnerability affecting the geyang/ml-logger library in versions up to 0.10.36. The vulnerability exists within the ml_logger/server.py component, specifically within the log_handler and stream_handler functions. This flaw allows remote, unauthenticated attackers to traverse the file system and access unauthorized files on the hosting server. Publicly available proof-of-concept (PoC) code has been released, significantly lowering the barrier for exploitation. Defenders should prioritize updating instances of ml-logger to a secure version to mitigate the risk of unauthorized file disclosure or system compromise.

Impact

The vulnerability carries a CVSS score of 7.5, indicating a high severity risk. Successful exploitation allows an attacker to bypass file system restrictions to read arbitrary files, which may lead to the exposure of sensitive credentials, configuration files, or other proprietary information. Organizations utilizing ml-logger in web-facing server environments are at the highest risk, as the vulnerability requires no authentication or user interaction to exploit.

Recommendation

  • Upgrade geyang/ml-logger to a version beyond 0.10.36 immediately to patch the vulnerable log_handler and stream_handler code.
  • Review web server access logs for requests containing directory traversal sequences (e.g., ../, ..%2f) directed toward the ml-logger server endpoint.
  • Restrict network access to the ml-logger server interface to trusted IP addresses if immediate patching is not possible.
]]>highadvisoryvulnerabilitypath-traversalweb-application