CVE-2026-1258: Arbitrary File Write via Symlink Bypass in AWS Language Servers

Vulnerability Overview Vulnerability Name: Arbitrary File Write in Language Servers for AWS CVE ID: CVE-2026-1258 Severity: 8.5 / 10 Description: AWS Language Servers ( project) provides an implementation of the Language Server Protocol (LSP) supporting AWS developer tools, including the Amazon Q Developer agent, which delivers experience within IDEs such as VS Code, JetBrains, Visual Studio, and Eclipse. Language Servers for AWS lacks symbolic link validation, which can lead to arbitrary file writes outside the workspace trust boundary. This may occur when a local user opens a workspace containing a maliciously crafted symbolic link that resolves to a file path outside the workspace's trust boundary. Scope Affected Versions: (npm): < 0.0.117 (https://github.com/aws/language-servers): < 1.69.0 Impact: If a user opens a workspace containing a symbolic link that is located within the workspace but resolves to a location outside the workspace trust boundary, the agent may follow the symbolic link and write to the external location without user approval. This can result in the modification of files outside the workspace trust boundary. This issue is triggered when a user opens a workspace, trusts it, and the agent subsequently writes to a path within the workspace. Remediation Patch: This issue has been resolved in AWS Language Servers version 1.69.0. It is recommended to upgrade to the latest version and ensure that all branches or forked codebases are patched with the new fix. Workaround: There are currently no available workarounds. References For any questions or comments, please contact AWS Security via the vulnerability reporting page or directly by email to . Please do not create public GitHub issues. Acknowledgments Thank you to Wiz and Maor Dokhanian for their collaboration on coordinating the vulnerability disclosure process.

Goal Reached Thanks to every supporter — we hit 100%!

CVE-2026-1258: Arbitrary File Write via Symlink Bypass in AWS Language Servers

More from this source