Deserialization Vulnerability in LazyAGI LazyLLM Server by LazyAGI
CVE-2025-10965

5.3MEDIUM

Key Information:

Vendor

Lazyagi

Status
Lazyllm
Vendor
CVE Published:
25 September 2025

Badges

👾 Exploit Exists🟡 Public PoC

What is CVE-2025-10965?

A deserialization vulnerability has been identified in LazyAGI's LazyLLM up to version 0.6.1, specifically in the lazyllm_call function located within the lazyllm/components/deploy/relay/server.py file. This flaw allows an attacker to manipulate the deserialization process remotely, potentially leading to unauthorized operations or execution of arbitrary code. The vulnerability has been publicly disclosed, raising concerns about its exploitation in the wild.

Affected Version(s)

LazyLLM 0.6.0

LazyLLM 0.6.1

Exploit Proof of Concept (PoC)

PoC code is written by security researchers to demonstrate the vulnerability can be exploited. PoC code is also a key component for weaponization which could lead to ransomware.

CVE-2025-10965 - Proof of Concept

References

https://vuldb.com/?id.325833
vdb-entrytechnical-description
https://vuldb.com/?ctiid.325833
signaturepermissions-required
https://vuldb.com/?submit.652936
third-party-advisory

CVSS V4

Score:
5.3
Severity:
MEDIUM
Confidentiality:
Low
Integrity:
Low
Availability:
Low
Attack Vector:
Network
Attack Complexity:
Low
Attack Required:
None
Privileges Required:
Undefined
User Interaction:
None

Timeline

  • 🟡

    Public PoC available

  • 👾

    Exploit known to exist

  • Vulnerability published

  • Vulnerability Reserved

Credit

0x1f (VulDB User)
JSON
.
CVE-2025-10965 : Deserialization Vulnerability in LazyAGI LazyLLM Server by LazyAGI