{"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-10952 exists.","fix":"No fix has been published for CVE-2025-10952 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-10952 is a medium-severity 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-10952 and fix it if it is affected.\n\nWhat it is: CVE-2025-10952 is a medium-severity 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-10952 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-10952/ (Markdown: https://insights.sbomify.com/CVE-2025-10952/index.md)","id":"CVE-2025-10952","markdown":"https://insights.sbomify.com/CVE-2025-10952/index.md","name":"CVE-2025-10952","record":{"aliases":["GHSA-9x36-c74v-fgr6","PYSEC-2026-1635"],"analysis":{"component_type":"library","fix_type":"no_fix_stated","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"Python logging library","requires_auth":"none","summary":"Remote attackers can exploit a flaw in the stream_handler function to disclose sensitive information from the ml-logger library.","user_interaction":"not_required","vuln_class":"information_disclosure"},"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:N/VA:N/SC:N/SI:N/SA:N/E:P","version":"4.0"},"cwes":[{"id":"CWE-284","name":"Improper Access Control"},{"id":"CWE-200","name":"Exposure of Sensitive Information to an Unauthorized Actor"}],"description":"A 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.","ecosystems":["PyPI"],"exploits":{"exploitdb":0,"first_seen":"2026-08-28","github_poc":1,"max_poc_stars":1,"metasploit":0,"nuclei":0,"refs":[{"date":"2026-08-28T09:49:40Z","kind":"github_poc","ref":"https://github.com/Khashayarnzk/CVE-2025-10952-ml-logger-AFR","stars":1,"title":"PoC for CVE-2025-10952 — ml-logger unauthenticated arbitrary file read. CVSS 5.3"}],"tier":"weaponised"},"has_fix":false,"headline":"geyang ml-logger File server.py stream_handler information disclosure","id":"CVE-2025-10952","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"PyPI","product":null,"products":[],"type":"information_disclosure","year":"2025"},"n_packages":3,"n_references":4,"next":{"headline":"UTT 1200GW/1250GW formApMail buffer overflow","id":"CVE-2025-10953"},"packages":[{"ecosystem":"PyPI","fixed":[],"introduced":["0"],"last_affected":["0.10.36"],"package":"ml-logger","purl":null,"source":"GHSA-9x36-c74v-fgr6"},{"ecosystem":"PyPI","fixed":[],"introduced":["0"],"last_affected":["0.10.36"],"package":"ml-logger","purl":"pkg:pypi/ml-logger","source":"GHSA-9x36-c74v-fgr6"},{"ecosystem":"PyPI","fixed":[],"introduced":["0"],"last_affected":["0.10.36"],"package":"ml-logger","purl":"pkg:pypi/ml-logger","source":"PYSEC-2026-1635"}],"prev":{"headline":"geyang ml-logger server.py log_handler path traversal","id":"CVE-2025-10951"},"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-25","vendors":["geyang"]},"summary":"Remote attackers can exploit a flaw in the stream_handler function to disclose sensitive information from the ml-logger library.","url":"https://insights.sbomify.com/CVE-2025-10952/"}