CVE-2026-3989: High severity Lmsys Sglang vulnerability

Published Mar 12, 2026
·
Updated

SGLangs replayrequestdump.py contains an insecure pickle.load() without validation and proper deserialization. An attacker can take advantage of this by providing a malicious .pkl file, which will execute the attackers code on the device running the script.

Affected Software

2 affected components
pip/sglang<=0.5.9
Lmsys Sglang<0.5.10

Event History

Mar 12, 2026
CVE Published
via MITRE·11:37 AM
Data Sourced
via MITRE·11:37 AM
DescriptionWeakness
Data Sourced
via NVD·12:15 PM
Description
Data Sourced
via NVD·12:15 PM
RemedySeverityWeaknessAffected Software
Advisory Published
via GitHub·12:30 PM
Data Sourced
via GitHub·12:30 PM
DescriptionSeverityWeaknessAffected Software

Frequently Asked Questions

1

What is the severity of CVE-2026-3989?

CVE-2026-3989 is considered a high severity vulnerability due to its potential for remote code execution.

2

How do I fix CVE-2026-3989?

To fix CVE-2026-3989, upgrade to version 0.6.0 or later of the sglang package which addresses this vulnerability.

3

What does CVE-2026-3989 affect?

CVE-2026-3989 affects versions of the sglang package up to 0.5.9 installed via pip.

4

What is the primary risk associated with CVE-2026-3989?

The primary risk associated with CVE-2026-3989 is that an attacker could execute arbitrary code on the device through a malicious pickle file.

5

Is there a workaround for CVE-2026-3989?

A workaround for CVE-2026-3989 is to avoid using the insecure pickle.load() method and implement safer deserialization alternatives.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203