LazyAGI LazyLLM up to 0.6.1 server.py lazyllm_call deserialization
Summary
A vulnerability marked as critical has been reported in LazyAGI LazyLLM up to 0.6.1. This affects the function lazyllm_call of the file lazyllm/components/deploy/relay/server.py. Performing a manipulation results in deserialization.
This vulnerability was named CVE-2025-10965. The attack may be initiated remotely. In addition, an exploit is available.
Details
A vulnerability was found in LazyAGI LazyLLM up to 0.6.1. It has been classified as critical. This affects the function lazyllm_call of the file lazyllm/components/deploy/relay/server.py. The manipulation with an unknown input leads to a deserialization vulnerability. CWE is classifying the issue as CWE-502. The product deserializes untrusted data without sufficiently verifying that the resulting data will be valid. This is going to have an impact on confidentiality, integrity, and availability.
The advisory is shared at github.com. This vulnerability is uniquely identified as CVE-2025-10965. The exploitability is told to be easy. It is possible to initiate the attack remotely. Technical details and a public exploit are known.
The exploit is shared for download at github.com. It is declared as proof-of-concept.
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
Product
Vendor
Name
Version
Website
- Product: https://github.com/LazyAGI/LazyLLM/
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CNA CVSS-B Score: 🔒
CNA CVSS-BT Score: 🔒
CNA Vector: 🔒
CVSSv3
VulDB Meta Base Score: 6.3VulDB Meta Temp Score: 6.0
VulDB Base Score: 6.3
VulDB Temp Score: 5.7
VulDB Vector: 🔒
VulDB Reliability: 🔍
CNA Base Score: 6.3
CNA Vector: 🔒
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍
Exploiting
Class: DeserializationCWE: CWE-502 / CWE-20
CAPEC: 🔒
ATT&CK: 🔒
Physical: No
Local: No
Remote: Yes
Availability: 🔒
Access: Public
Status: Proof-of-Concept
Download: 🔒
EPSS Score: 🔒
EPSS Percentile: 🔒
Price Prediction: 🔍
Current Price Estimation: 🔒
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: no mitigation knownStatus: 🔍
0-Day Time: 🔒
Timeline
09/25/2025 Advisory disclosed09/25/2025 VulDB entry created
09/26/2025 VulDB entry last update
Sources
Product: github.comAdvisory: 764
Status: Not defined
CVE: CVE-2025-10965 (🔒)
GCVE (CVE): GCVE-0-2025-10965
GCVE (VulDB): GCVE-100-325833
scip Labs: https://www.scip.ch/en/?labs.20161013
Entry
Created: 09/25/2025 12:16Updated: 09/26/2025 06:28
Changes: 09/25/2025 12:16 (56), 09/26/2025 06:28 (30)
Complete: 🔍
Submitter: 0x1f
Cache ID: 216::103
Submit
Accepted
- Submit #652936: LazyAGI LazyLLM latest Remote Code Execution (by 0x1f)
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
No comments yet. Languages: en.
Please log in to comment.