CVE-2025-10965
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedA 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceA deserialization vulnerability exists in LazyLLM up to version 0.6.1 within the lazyllm_call function in lazyllm/components/deploy/relay/server.py. The function processes untrusted data without proper validation, potentially allowing remote code execution through malicious serialized payloads. This is a server-side vulnerability in a relay component that can be exploited remotely.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- Low
- Integrity
- Low
- Availability
- Low
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Check installed LazyLLM versionRun 'pip show lazyllm' or 'pip list | grep lazyllm' to retrieve the installed package versionAffected if Version is 0.6.1 or lower (any version up to and including 0.6.1)
-
Verify the vulnerable file existsLocate the file lazyllm/components/deploy/relay/server.py in the installed package directory (run 'python -c "import lazyllm; print(lazyllm.__file__)"' to find the package path)Affected if The file exists in the installation, indicating the relay component is present
-
Determine if relay server is in useInspect your deployment configuration, startup scripts, or running processes for references to the relay server component or lazyllm_call functionAffected if The relay server component is deployed or the lazyllm_call function is exposed as an API endpoint
-
Check for unauthenticated network exposureReview network configuration and firewall rules to determine if the relay server port is accessible from untrusted networksAffected if The relay server endpoint accepts connections from untrusted or public networks without authentication
You are affected if LazyLLM version is 0.6.1 or lower AND the relay server component is deployed and accessible, since the deserialization flaw requires both the vulnerable code and network exposure to be exploitable.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataUpgrade LazyLLM to version 0.6.2 or later which contains the security patch. If no patch is available, implement input validation and sanitization on all data being passed to the lazyllm_call function, and restrict network access to the relay server.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-10965 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-10965 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data