Secuno
ENNL
Book demo

CVE-2026-15971

Lmsys Sglang code injection

9.8 CRITICALEPSS 0.73%
  1. Published30 Jul 2026

Description

SGLang contains an RCE vulnerability when the optional dumper subsystem is enabled, allowing for a sandbox escape when DUMPER_SERVER_PORT is set, enabling code execution on inference requests.

CVSS 3.1 breakdown

Attack vectorNetwork
Attack complexityLow
Privileges requiredNone
User interactionNone
ScopeUnchanged
ConfidentialityHigh
IntegrityHigh
AvailabilityHigh
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Affected products

Lmsys Sglang≤ 0.5.15

Remediation

No fixed version is recorded in the NVD data. Check the vendor advisory for the latest guidance.

References

Related CVEs

Recent high-severity vulnerabilities sharing a weakness type.

CVE-2026-659548.6
PHPCSUtils is a suite of utility functions for use with PHP_CodeSniffer. From…
CVE-2026-1082639.9
Astron Agent is an agentic workflow platform for building and running AI agents. Prior…
CVE-2024-420028.4
A code injection vulnerability has been discovered in the Robot Operating System 2 (ROS…
CVE-2026-1007419.8
Eval injection in the JScript event-script dispatcher in Progressive Robot Ltd's…
CVE-2026-571499.9
plone.app.portlets.portlets provides a Plone-specific user interface for…
CVE-2026-788479.8
An issue in gray-matter All versions (verified on 4.0.3) allows the JavaScript engine…

Frequently asked

Is CVE-2026-15971 being actively exploited?

CVE-2026-15971 is not in the CISA KEV catalog. Its EPSS exploit probability is 0.73%.

How severe is CVE-2026-15971?

CVE-2026-15971 has a CVSS 3.1 base score of 9.8, rated critical. EPSS estimates a 0.73% probability of exploitation.

Which products are affected by CVE-2026-15971?

Affected products include Lmsys Sglang.

How do I fix CVE-2026-15971?

Apply the vendor's patch or advisory guidance, then verify no affected versions remain across your devices.

How Secuno handles this

Secuno correlates vulnerabilities like CVE-2026-15971 against the real software inventory on every managed device, as each hourly inventory arrives. Rather than a static severity, each match is scored in context: exploit availability, EPSS, the asset's exposure, and business criticality decide where it lands in the queue. If an affected version is present anywhere across your portfolio, it surfaces automatically with a prioritised remediation path.

See how prioritisation worksBook a demo

Get Patch this first every Monday

Five vulnerabilities that matter this week, ranked on real exploitation. Plain language, one email, no spam.

You can unsubscribe with one click from every issue. We handle your details as described in our privacy policy.

Data from the NVD, CISA KEV catalog and FIRST EPSS. CVSS 3.1 base score shown where available.