CVE-2026-12958
Arbitrary file write in Language Servers for AWS
No known exploitation. EPSS puts it in the 8th percentile. Fixed in 1.69.0.
What to do
Find your product and version, then upgrade to the build on the right.
- Amazon Web Services Language Servers for AWSAffected: < 1.69.0Upgrade to: 1.69.0Stated by: CVE record
Versions as the sources state them. Full version matrix after sign-in
Steps
Written by AI from the record- Check which version of Language Servers for AWS is installed in your developer environment.
- If it’s older than 1.69.0, upgrade to Language Servers for AWS 1.69.0 or higher.
- If you can’t upgrade right away, avoid opening untrusted repositories/workspaces that could contain malicious symlinks.
Coverage timeline
2 publishersTechnical analysis published
Vendor patch released
Sourced from public security reporting — each date is when it was published, not when it happened. 1 further article named this CVE in wider roundups without reporting it as a distinct event.
What it is
From the CVE record
Missing symlink validation in Language Servers for AWS may allow an arbitrary file write outside of the workspace trust boundary. This may occur when a local user opens a workspace with a maliciously crafted symlink that resolves to a file path outside the workspace trust boundary. To remediate this issue, users should upgrade to version 1.69.0 or higher.
In plain language
Written by AI from the recordLanguage Servers for AWS can be tricked into writing files anywhere on your computer when you open a workspace containing a malicious link; if your team uses this tool, you should update to the fixed version.
In Language Servers for AWS, a missing symlink validation allows arbitrary file write outside the workspace trust boundary when a user opens a malicious workspace that contains symlinks resolving to paths outside the trusted directory.
If you're affected
- Malicious files written on endpoints
- Cloud credential or API key theft
- Developer environment compromise
- Work disruption from altered files
Exploitation
Where each signal puts this CVE on the scale from published to confirmed exploited.
- CISA KEV
Not in the catalog. CISA has not confirmed exploitation.
- Public exploits
No public exploit or proof of concept found in the sources we track.
- EPSS
0.2% chance of exploitation activity in the next 30 days, which ranks it in the 8th percentile of scored CVEs.
Exploit Prediction Scoring System, FIRST.org. A probability, not a confirmation.
Lifecycle
3 events over 0 days, from the signal feeds we watch.
- Publishedweakness classified, record updated
Affected products
Technical detail
CVSS 3.1 vector
Open in the CVSS calculatorCVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
Scored 7.8 by NVD.
How it is reached
- Attack Vector LocalRequires local access to the vulnerable system (e.g. local login, malicious file)
- Attack Complexity LowNo special conditions — the attack can be reliably reproduced
- Privileges Required NoneNo authentication required — anyone can exploit this
- User Interaction RequiredA user must click a link, open a file, or perform some action
Scope
- Scope UnchangedImpact is limited to the vulnerable component itself
Impact if exploited
- Confidentiality HighTotal information disclosure — all data in the component is compromised
- Integrity HighTotal loss of integrity — attacker can modify any data in the component
- Availability HighTotal denial of service — the component is completely unavailable
Weaknesses
Sources
References in the record
In the news
Watch the software you run.
My Stack ranks new CVEs for your products by real-world exploitation, so the next serious one reaches you without reading every advisory.
We'll flag the next CVE, public exploit or patch for Language Servers for AWS, not every advisory.
A free account adds
- The full version matrix and every affected product
- Exploit links, proofs of concept and Metasploit modules
- Email alerts for the products you watch
- The same data over REST API, MCP and CLI