CVE-2026-127143
9.4CriticalPublished 18 Nov 2026 · NVD status: Received · AI triage by gemini-3.1-flash-lite
Critical
0CVSS v4.010
- Attack vector
- Network
- Complexity
- Low
- Privileges
- Low
- User action
- None
- Impact
- Full C/I/A compromise
- Weakness
- CWE-829
What an attacker gets
Attackers can gain root privileges by registering a malicious library in the LMS database. This requires either web server access or write access to the LMS database.
Root cause
The lmsd daemon loads libraries from the database without verifying their source or location.
Affected versions
LMS (Lan Management System) versions prior to commit 89dd3f7.
CVSS v4.0 · CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
Fix & remediation
Disable and remove the lmsd component entirely, as it has been removed from the codebase.
$ sudo systemctl stop lmsd && sudo systemctl disable lmsdAI-suggested. Run it in staging first and check it against the vendor advisory. Why?
NVD description
LMS (Lan Management System) is vulnerable to privilege escalation in the lmsd daemon. The daemon loads the libraries listed in the LMS database without checking that they come from a trusted location. An attacker with access to the web server process or with write access to the LMS database can register a malicious library and trigger a configuration reload, causing lmsd to load and execute it. Because the example systemd unit does not set a separate user, lmsd runs as root, allowing the attacker to execute arbitrary code with root privileges. This issue was fixed in commit 89dd3f7. The lmsd component was removed. For existing installations that use lmsd, the recommended solution is to disable and remove this component.