{"answers":{"affected":"","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-10965 exists.","fix":"No fix has been published for CVE-2025-10965 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-10965 is a medium-severity unsafe deserialization vulnerability in LazyAGI LazyLLM, published on 25 Sep 2025. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2025-10965 and fix it if it is affected.\n\nWhat it is: CVE-2025-10965 is a medium-severity unsafe deserialization vulnerability in LazyAGI LazyLLM, published on 25 Sep 2025. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-10965 exists.\n\nAffected product: LazyAGI LazyLLM. No package-level version data is available, so check the vendor advisory linked from the reference page.\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-10965/ (Markdown: https://insights.sbomify.com/CVE-2025-10965/index.md)","id":"CVE-2025-10965","markdown":"https://insights.sbomify.com/CVE-2025-10965/index.md","name":"CVE-2025-10965","record":{"aliases":["GHSA-4c22-7xx9-4rpv"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"LazyLLM library","requires_auth":"low_privilege","summary":"Remote attackers can execute arbitrary code via unsafe deserialization in the LazyLLM library's relay server component.","user_interaction":"not_required","vuln_class":"deserialization"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"VulDB","cpe":[],"cvss":{"score":5.3,"severity":"medium","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:P","version":"4.0"},"cwes":[{"id":"CWE-502","name":"Deserialization of Untrusted Data"},{"id":"CWE-20","name":"Improper Input Validation"}],"description":"A security vulnerability has been detected in LazyAGI LazyLLM up to 0.6.1. Affected by this issue is the function lazyllm_call of the file lazyllm/components/deploy/relay/server.py. Such manipulation leads to deserialization. The attack can be launched remotely. The exploit has been disclosed publicly and may be used.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":false,"headline":"LazyAGI LazyLLM server.py lazyllm_call deserialization","id":"CVE-2025-10965","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"deserialization","year":"2025"},"n_packages":0,"n_references":4,"next":{"headline":"missing SFTP host verification with wolfSSH","id":"CVE-2025-10966"},"packages":[],"prev":{"headline":"Wavlink NU516U1 firewall.cgi sub_401B30 command injection","id":"CVE-2025-10964"},"products":["LazyLLM"],"published":"2025-09-25","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2025-09-26","vendors":["LazyAGI"]},"summary":"Remote attackers can execute arbitrary code via unsafe deserialization in the LazyLLM library's relay server component.","url":"https://insights.sbomify.com/CVE-2025-10965/"}