LSP untrusted repo interpreter/SDK execution security fix
Cluster 125954. Data as of
Nothing open on GitHub. Fix merged in #126239 on 28 Sep 2026. Check it covers your case.
The short answer
- Known?
- Yes. 3 related items grouped here, 1 issue already closed.
- Fix event
- A fix was merged to main in PR #126239. Check it covers your case. No release data is tracked.
- Tracker
- The maintainers' tracker marks this
resolved, deciding PR #126239. That is separate from the fix event. - Still open
- Nothing open on GitHub.
A bug was identified where editing files in a cloned repository could cause the LSP to run that repository's own Python interpreter, TypeScript SDK, or plugins without user approval. The cluster covers the bug report and two related fix attempts addressing untrusted workspace execution boundaries.
Open issues0
Open PRs0
Fixes on record
-
#126239 fix(lsp): never run a cloned repo's own interpreter, SDK or plugins; trust the session's workspace (salvage #125955)
files:
agent/lsp/cli.py,agent/lsp/eventlog.py,agent/lsp/manager.py,agent/lsp/servers.py,agent/lsp/workspace.py,cli-config.yaml.example,hermes_cli/config_defaults.py,tests/agent/lsp/test_custom_servers.py,tests/agent/lsp/test_install_and_lint_fixes.py,tests/agent/lsp/test_manager_locking.py,tests/agent/lsp/test_python_discovery.py,tests/agent/lsp/test_root_policy.py,tests/agent/lsp/test_shell_linter_lsp_skip.py,tests/agent/lsp/test_workspace_trust.py,tests/pm/test_node_resolution.py,tools/file_operations_lint.py,website/docs/user-guide/features/lsp.md,website/i18n/zh-Hans/docusaurus-plugin-content-docs/current/user-guide/features/lsp.md
1 PR closed without merging
From the close comments: superseded by another PR 1
-
#125955 fix(lsp): never run a cloned repository's own interpreter or TypeScript SDK in an untrusted workspace · superseded by another PR →
1f3b384,482e5a1,#126239
Closed issues · 1
- Closed#125954[Bug]: editing a file in a cloned repository runs that repository's own Python interpreter through the LSP (no approval, on by default)
How this cluster was grouped
-
Link evidence (
structural links throughout): every member is connected by structural evidence: shared changed files, or a closing/superseded reference. -
Pairwise link density
1.00: the share of item pairs that carry a link, counting a structural link in full and a relevance-only link at 0.36.1.00means every pair is linked.
Pick up a Lab task
Check whether a fix covers the open issues here, with your own agent. Bring back evidence for maintainers.
Open the LabAt a glance
- Merged PRs
- #126239
- Closed issues
- 1
- Attempts
- 1 PR closed without merging
- Fix link checked
- 28 Sep 2026