AWS Fixes Insecure File Permissions for CodeCatalyst Tokens in VS Code Extension
The AWS Toolkit for Visual Studio Code cached bearer tokens with world-readable permissions, exposing credentials to local attackers.
Key points
- AWS identified CVE-2026-107332 in the Toolkit for Visual Studio Code.
- Cached CodeCatalyst bearer tokens were stored with world-readable permissions.
- The vulnerability affects extension versions prior to 4.10.0.
AWS has released a security bulletin addressing a vulnerability in the AWS Toolkit for Visual Studio Code that allowed local attackers to access cached credentials. The issue, tracked as CVE-2026-107332, involved insecure default file permissions on files containing CodeCatalyst bearer tokens.
At a glance
- Publisher
- AWS Security Bulletins
- CVEs
- CVE-2026-107332
The vulnerability exists within the CodeCatalyst connection handler of the open-source extension. When developers connected to a CodeCatalyst Dev Environment, the extension saved the user's bearer token to a local file. According to the AWS Security Bulletin published on October 8, 2026, these files were created with world-readable permissions. Furthermore, the extension failed to delete the credential file after the session ended, leaving the tokens accessible on the file system.
Technical Context
AWS Toolkit for Visual Studio Code enables developers to interact with various AWS services directly from the Visual Studio Code editor. This includes connectivity to Amazon CodeCatalyst, a development platform for managing software projects. The specific flaw was identified in how the extension managed the lifecycle of authentication tokens during Dev Environment sessions.
Because the cached files were world-readable, any local user or process on the same machine with file system access could read the contents. This allowed an attacker to obtain the bearer token, potentially compromising the associated AWS resources. AWS classified the bulletin as "Important," indicating that the issue requires attention from users of the affected software.
Who Is Affected
The vulnerability impacts users of the AWS Toolkit for Visual Studio Code running versions earlier than 4.10.0. Any developer who has used the extension to connect to a CodeCatalyst Dev Environment on a version prior to the fix may have had their bearer tokens exposed. The risk is primarily to systems where multiple users share access or where malicious processes could run with lower privileges than the developer's account.
What should you do?
AWS has addressed the issue in version 4.10.0 of the AWS Toolkit for Visual Studio Code. Users should update their extension to this version or later to ensure that cached credentials are handled with appropriate file permissions and that temporary files are removed after sessions end. Developers should also review their systems for any residual cached token files from previous sessions if they are upgrading from an older version.
What to do and how to stay safe: AWS
- Patch scores alone ignore context like network exposure and asset criticality.
- You must map vulnerabilities to specific business risks to prioritize correctly.
- Continuous exposure data replaces static scanning for accurate prioritization.
Prioritize vulnerabilities by actual exploitability and business impact, not by theoretical severity scores. Update your asset context and exposure data continuously to maintain accurate risk rankings.
Step-by-step guide: Risk Based Vulnerability Management: Prioritize Fixes by Actual Threat
General security guidance from the Threat Times newsroom. It is not confirmed advice from the organisations named in this story.
Frequently asked questions
What is CVE-2026-107332?
It is a vulnerability in the AWS Toolkit for Visual Studio Code where cached CodeCatalyst bearer tokens were stored with world-readable permissions.
Which versions of the extension are vulnerable?
All versions of the AWS Toolkit for Visual Studio Code prior to 4.10.0 are affected by this issue.
Is there a fix available for this vulnerability?
Yes, AWS has released version 4.10.0 which resolves the insecure file permissions and ensures files are removed after sessions end.
