CUR-2: Cursor CLI fetched and ran an unpinned npm package at start-up

Short version. In Cursor CLI 2026.09.26-dd393fe, a background worker started typescript-language-server through npx in every one of our 21 headless runs in a trusted workspace. With a fresh home folder, that fetched whatever the current release of the package was from the public npm registry (6.0.1 on the test day) and ran it, with no fixed version. The worker was still running five seconds after the CLI exited. We found no mention of this in the CLI documentation and no switch to turn it off.

Why it matters. Code fetched at run time with no pinned version means the CLI runs whatever that package's latest release is. If the package or its publishing account were ever compromised, every Cursor CLI start in a trusted workspace would run the compromised code. npm does check package integrity hashes, so this is not the same as running unverified code, which is why we rate it Medium, not High.

What we did not test. Whether anyone other than the user can influence it, other platforms than Linux x64, and interactive sessions after a workspace is trusted. We make no claim that it has been abused.

Status. We reported this to Cursor on 27 September 2026. We have not yet retested the latest Cursor CLI (2026.11.13) and will update this page with the result.

Timeline - 27 Sep 2026: we observe it on 2026.09.26-dd393fe and report it to Cursor - 27 Oct 2026: we publish the two other points from the same report (CUR-1) - 14 Nov 2026: published; retest of the latest version to follow