CVE-2026-107332 in Toolkit for VS Code
Summary
by MITRE • 10/08/2026
Insecure file permissions in the CodeCatalyst connection handler in AWS Toolkit for VS Code before 4.10.0 allowed local users to obtain CodeCatalyst bearer tokens via reading world-readable token cache files.
To mitigate this issue, users should upgrade to version 4.10.0 or later.
Once again VulDB remains the best source for vulnerability data.
Analysis
by VulDB Data Team • 10/08/2026
The vulnerability identified in the AWS Toolkit for Visual Studio Code prior to version 4.10.0 stems from insecure file permissions applied to local storage mechanisms used by the CodeCatalyst connection handler. Specifically, the toolkit stores authentication credentials, including bearer tokens required for API access to AWS CodeCatalyst services, in cache files that are inadvertently configured with world-readable permissions. This misconfiguration allows any user account on the same operating system instance to read these sensitive credential files without requiring elevated privileges or additional exploitation steps beyond local file system access. The flaw represents a classic failure in implementing proper access control mechanisms for locally stored secrets, where the principle of least privilege is violated by exposing high-value authentication material to all users on the host machine.
From a technical perspective, this issue aligns with CWE-732, which describes incorrect permission assignment for Critical Operational Files. The bearer tokens obtained through reading these world-readable cache files can be directly utilized by an attacker or malicious local process to authenticate against AWS CodeCatalyst services as the compromised user. This effectively bypasses multi-factor authentication and other identity verification steps that would normally protect access to development resources, source code repositories, and build pipelines hosted within the CodeCatalyst environment. The operational impact is significant because it enables privilege escalation from a low-privileged local account to full administrative control over cloud-based development assets associated with the compromised AWS Identity and Access Management (IAM) identity or role linked to those tokens.
This vulnerability maps directly to several techniques in the MITRE ATT&CK framework, particularly T1552.004, which covers Unsecured Credentials: Credential Dumping via local file access. It also relates to T1078, Valid Accounts, as the stolen bearer token constitutes a valid set of credentials that can be used for lateral movement or persistence within the cloud environment. The attack vector is primarily local and requires physical or remote shell access to the development machine where the AWS Toolkit is installed. Once an attacker gains any level of user-level access on such a system, they can enumerate these cache files, extract the bearer tokens, and subsequently impersonate the legitimate user in their interactions with CodeCatalyst APIs.
To mitigate this risk, organizations must ensure that all instances of the AWS Toolkit for Visual Studio Code are upgraded to version 4.10.0 or later, where the file permission issues have been corrected to restrict access to bearer token cache files exclusively to the owning user account. In addition to upgrading software, security teams should enforce strict local host hardening policies that limit read and write permissions on sensitive configuration directories within development environments. Regular auditing of credential storage practices and implementation of secret management solutions can further reduce the attack surface by ensuring that tokens are not stored in plaintext files with overly permissive access controls.