⚠️ NSSM is not inherently vulnerable; the risk lies in improperly secured services installed by NSSM. Always review service permission assignments.
You're referring to a paper about a privilege escalation vulnerability in NSSM (Non-Sucking Service Manager) version 224. nssm224 privilege escalation updated
The replacement is possible because the file permissions allow low‑privileged users to write to the directory. ⚠️ NSSM is not inherently vulnerable; the risk
A closely related vulnerability, , was disclosed in IBM’s Robotic Process Automation (RPA) product. IBM RPA versions 21.0.0 through 21.0.7.17 and 23.0.0 through 23.0.18 allow a local user to escalate privileges because “all files in the install inherit the file permissions of the parent directory and therefore a non‑privileged user can substitute any executable for the nssm.exe service.” This highlights how the same underlying weakness can reappear in different software packages that embed NSSM. The replacement is possible because the file permissions
Since its creation, NSSM has been embedded in countless enterprise products and open‑source projects, including database management systems, automation platforms, and monitoring tools. Its widespread adoption makes any security flaw in NSSM particularly impactful, as it can cascade across numerous third‑party applications that depend on it.