Live › vulnerability › CVE-2026-107332
Go to dashboardBefore 4.10.0, the AWS Toolkit for Visual Studio Code extension cached a user's CodeCatalyst bearer token in a world-readable file and did not delete it after a Dev Environment session ended. A local user or process on the same machine can read that file and take the token.
Summary written from the sources below. Check the originals before acting.
First seen by InfraStack 2026-10-24 18:43 UTC, 0h before NVD. All times on this page are UTC.
Developers who connected VS Code to a CodeCatalyst Dev Environment with the AWS Toolkit extension before 4.10.0 on a shared or multi-user machine are exposed, because other local users or processes could read the cached token. Machines with a single trusted user, or that never used CodeCatalyst Dev Environments, have less exposure.
No product ranges from the sources yet.
codecatalyst..token in the AWS Toolkit extension's Visual Studio Code global storage directory.4.10.0 are affected.4.10.0 or later.codecatalyst..token files in the extension's global storage directory after each session.Each row is the first time that source carried this signal. The analyst’s rows are its own findings.
CVE-2026-107332 - Insecure default file permissions on cached credentials in AWS Toolkit for Visual Studio Code
Bulletin ID: 2026-129-AWS Scope: AWS Content Type: Important (requires attention) Publication Date: 10/08/2026 10:30 AM PDT
Description:
AWS Toolkit for Visual Studio Code is an open source extension that lets developers work with AWS services, including Amazon CodeCatalyst, from within Visual Studio Code. We identified CVE-2026-107332, an issue in the CodeCatalyst connection handler. When a user connected to a CodeCatalyst Dev Environment, the extension cached the user's CodeCatalyst bearer token to a file with world-readable permissions and did not remove the file after the session ended. A local user or process on the same machine with access to the file system was able to read this file and obtain the bearer token.
Impacted versions: < 4.10.0
Resolution:
This issue has been addressed in AWS Toolkit for Visual Studio Code version 4.10.0, released on July 9, 2026. Version 4.10.0 writes the token cache file with owner-only permissions and deletes it when the Dev Environment is stopped. We recommend upgrading to the latest version and ensuring any forked or derivative code is patched to incorporate the new fixes.
Workarounds:
Users who cannot upgrade immediately can delete any files named codecatalyst..token in the AWS Toolkit extension's Visual Studio Code global storage directory after each session.
References:
Please email [email protected] with any security questions or concerns.
This page as .md · .json · in your agent: get_signal("CVE-2026-107332")
NVD data is provided by NIST and is public domain · EPSS scores by FIRST, used with attribution. Posts quoted belong to their authors.