PatchSiren

PatchSiren cyber security CVE debrief

CVE-2025-59953 InternLM CVE debrief

CVE-2025-59953 debrief: LMDeploy rpc server deserialization vulnerability allows remote code execution. Affected product deployments should assess exposure and apply the patch in version 0.10.2. The vulnerability exists in LMDeploy's rpc server (AsyncRPCServer in zmq_rpc.py) due to insecure deserialization practices. Defenders should verify exposure, apply the patch, and monitor for potential exploitation attempts. The CVE record and NVD entry provide details on the LMDeploy vulnerability.

Vendor
InternLM
Product
lmdeploy
CVSS
CRITICAL 9.8
CISA KEV
Not listed in stored evidence
Original CVE published
2026-09-16
Original CVE updated
2026-09-18
Advisory published
2026-09-16
Advisory updated
2026-09-18

Who should care

Defenders of systems using LMDeploy versions 0.9.1 and prior should assess exposure and apply the patch in version 0.10.2. Operators, security teams, and platform administrators should review rpc server configuration and deserialization practices to verify exposure and apply mitigations. Vulnerability management and security teams should monitor for potential exploitation attempts and track exceptions.

Why it matters

CVE-2025-59953 is a critical vulnerability in LMDeploy's rpc server, allowing for remote code execution due to insecure deserialization practices. Defenders should verify exposure, apply the patch, and monitor for potential exploitation attempts.

  • Potential remote code execution
  • Verification of LMDeploy version and patch application required
  • Monitoring for exploitation attempts recommended

Technical summary

LMDeploy's rpc server (AsyncRPCServer in zmq_rpc.py) is vulnerable to remote code execution due to insecure deserialization of received messages using pickles.loads() without sanitization. The vulnerability allows for remote code execution and defenders should verify exposure, apply the patch, and monitor for potential exploitation attempts. A patch is available in version 0.10.2. The CVE record and NVD entry provide details on the LMDeploy vulnerability, with no additional technical claims made beyond source-provided facts.

Defensive priority

High priority for version 0.9.1 and prior, verify exposure and apply patch

Recommended defensive actions

  • Verify LMDeploy version and apply patch if necessary
  • Review rpc server configuration and deserialization practices
  • Monitor for potential exploitation attempts
  • Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up
  • Review the supplied official advisory or CVE record to validate affected scope, severity, and vendor guidance
  • Plan vendor-supported updates or mitigations through normal change control where exposure is confirmed
  • Check relevant monitoring, detection, and logs for exposed assets that need extra review

Evidence notes

The CVE record and NVD entry provide details on the LMDeploy vulnerability, with a patch available in version 0.10.2. Defenders should verify exposure by reviewing LMDeploy version and rpc server configuration. The vulnerability allows for remote code execution due to insecure deserialization of received messages using pickles.loads() without sanitization. Evidence limits are based on CVE and NVD entries, with no additional facts claimed.

Sources and references

Verified primary and authoritative sources

  • CVE-2025-59953 CVE Program record

    Publisher, destination, and source semantics verified

    URL: https://www.cve.org/CVERecord?id=CVE-2025-59953

    CVE Program - Official CVE Program record with source-provided CVE metadata.

  • CVE-2025-59953 NVD vulnerability detail

    Publisher, destination, and source semantics verified

    URL: https://nvd.nist.gov/vuln/detail/CVE-2025-59953

    NIST National Vulnerability Database - Official NIST NVD detail page and source-specific vulnerability assessment.

Supplemental references

Methodology and review provenance

AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.