{"answers":{"affected":"3 open source packages ship an affected version, including ml-logger.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-10951 exists.","fix":"No fix has been published for CVE-2025-10951 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-10951 is a medium-severity path traversal vulnerability in geyang ml-logger, published on 25 Sep 2025. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2025-10951 and fix it if it is affected.\n\nWhat it is: CVE-2025-10951 is a medium-severity path traversal vulnerability in geyang ml-logger, published on 25 Sep 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-10951 exists.\n\nAffected packages and fixed versions:\n- ml-logger (PyPI): affected all versions up to 0.10.36; no fix listed\n- ml-logger (PyPI): affected all versions up to 0.10.36; no fix listed\n- ml-logger (PyPI): affected all versions up to 0.10.36; no fix listed\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2025-10951/ (Markdown: https://insights.sbomify.com/CVE-2025-10951/index.md)","id":"CVE-2025-10951","markdown":"https://insights.sbomify.com/CVE-2025-10951/index.md","name":"CVE-2025-10951","record":{"aliases":["GHSA-8x9j-2p8r-7xc6","PYSEC-2026-1634"],"analysis":{"component_type":"library","fix_type":"no_fix_stated","impacts":["data_read","data_modify"],"network_reachable":"yes","non_default_config":false,"product_category":"Python logging library","requires_auth":"none","summary":"Remote attackers can exploit a path traversal flaw in the log handler to read or modify arbitrary files on the server.","user_interaction":"not_required","vuln_class":"path_traversal"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"VulDB","cpe":[],"cvss":{"score":6.9,"severity":"medium","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:P","version":"4.0"},"cwes":[{"id":"CWE-22","name":"Improper Limitation of a Pathname to a Restricted Directory"}],"description":"A 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.","ecosystems":["PyPI"],"exploits":{"exploitdb":0,"first_seen":"2026-08-11","github_poc":1,"max_poc_stars":0,"metasploit":0,"nuclei":0,"refs":[{"date":"2026-08-11T21:53:00Z","kind":"github_poc","ref":"https://github.com/1amUnvalid/CVE-2025-10951","stars":0,"title":null}],"tier":"weaponised"},"has_fix":false,"headline":"geyang ml-logger server.py log_handler path traversal","id":"CVE-2025-10951","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"PyPI","product":null,"products":[],"type":"path_traversal","year":"2025"},"n_packages":3,"n_references":4,"next":{"headline":"geyang ml-logger File server.py stream_handler information disclosure","id":"CVE-2025-10952"},"packages":[{"ecosystem":"PyPI","fixed":[],"introduced":["0"],"last_affected":["0.10.36"],"package":"ml-logger","purl":null,"source":"GHSA-8x9j-2p8r-7xc6"},{"ecosystem":"PyPI","fixed":[],"introduced":["0"],"last_affected":["0.10.36"],"package":"ml-logger","purl":"pkg:pypi/ml-logger","source":"GHSA-8x9j-2p8r-7xc6"},{"ecosystem":"PyPI","fixed":[],"introduced":["0"],"last_affected":["0.10.36"],"package":"ml-logger","purl":"pkg:pypi/ml-logger","source":"PYSEC-2026-1634"}],"prev":{"headline":"geyang ml-logger Ping server.py log_handler deserialization","id":"CVE-2025-10950"},"products":["ml-logger"],"published":"2025-09-25","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"class":"attribution","licence":"CC BY 4.0","name":"PyPA Advisory Database","prefix":"PYSEC"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"},{"class":"open","licence":"CC0","name":"PoC-in-GitHub"}],"ssvc":{"automatable":"yes","exploitation":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2025-09-26","vendors":["geyang"]},"summary":"Remote attackers can exploit a path traversal flaw in the log handler to read or modify arbitrary files on the server.","url":"https://insights.sbomify.com/CVE-2025-10951/"}