# CVE-2026-107332: AWS Toolkit for Visual Studio Code insecure credentials file permissions

Source: https://junglewise.ai/threats/cve-2026-107332-insecure-default-file-permissions-on-cached-credentials-in-aws  
Publisher: Junglewise Threat Intelligence, https://junglewise.ai/threats  
Published: 2026-10-08. Updated: 2026-10-08  
License: CC BY 4.0 with a link back

CVE-2026-107332 · Severity: high · Published 2026-10-08

AWS Toolkit for Visual Studio Code cached CodeCatalyst authentication tokens to files with world-readable permissions, allowing any local user on the same machine to steal the tokens. An attacker with local file system access could obtain valid credentials to access AWS services and CodeCatalyst dev environments without authorization.

Technologies: [Amazon AWS](https://junglewise.ai/threats/technologies/aws). Vendors: [Amazon](https://junglewise.ai/threats/vendors/amazon), [Amazon Web Services](https://junglewise.ai/threats/vendors/amazon-web-services).

## Quick answers

**Is CVE-2026-107332 exploited in the wild?** No. Junglewise Threat Intelligence has no report of CVE-2026-107332 being exploited in the wild.

**How severe is CVE-2026-107332?** High severity, published 8 October 2026.

**Which products and versions are affected?** Amazon Web Services Toolkit for Visual Studio Code before 4.10.0.

**Is there a fix for CVE-2026-107332?** Yes: fixed in 4.10.0. Until then: Users unable to upgrade immediately should manually delete any files named codecatalyst..token in the AWS Toolkit extension's Visual Studio Code global storage directory after each session. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

**How is CVE-2026-107332 attacked?** It is attacked with local access.

**Am I affected by CVE-2026-107332?** Check whether you run Amazon AWS or Amazon Web Services Toolkit for Visual Studio Code at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

## How to fix

- Fixed in 4.10.0

Users unable to upgrade immediately should manually delete any files named codecatalyst..token in the AWS Toolkit extension's Visual Studio Code global storage directory after each session.

## Technical details

The CodeCatalyst connection handler in AWS Toolkit for Visual Studio Code wrote cached bearer tokens to files with overly permissive (world-readable) file permissions and failed to clean them up after sessions ended. An authenticated local attacker or unprivileged process with file system access can read the token cache file and extract valid bearer tokens, bypassing authentication to CodeCatalyst and AWS services.

## Affected products

- Amazon Web Services Toolkit for Visual Studio Code before 4.10.0

## Timeline

- 2026-10-08: disclosed: AWS Security Bulletin published
- 2026-07-09: patched: Version 4.10.0 released with fix

## References

- [https://aws.amazon.com/security/security-bulletins/rss/2026-129-aws/](https://aws.amazon.com/security/security-bulletins/rss/2026-129-aws/)

## Related threats

- [An untrusted search path issue in Aurora PostgreSQL dialect detection in the AWS Advanced Go Wrapper from release 2026-04-06 (awssql/v2.0.0)](https://junglewise.ai/threats/cve-2026-126793-privilege-escalation-in-aurora-postgresql-dialect-detection-in)
- [AWS SDK for pandas EMR unverified bucket ownership](https://junglewise.ai/threats/cve-2026-127119-unverified-ownership-of-the-default-emr-cluster-log-location-in)
- [Amazon mcp-gateway-registry server-side request forgery in registration API](https://junglewise.ai/threats/cve-2026-125926-server-side-request-forgery-in-the-server-registration-and)
- [Amazon mcp-gateway-registry authorization bypass in management API](https://junglewise.ai/threats/cve-2026-100307-missing-authorization-on-the-external-management-api-in-mcp)
- [AWS Kiro CLI incorrect default permissions on session files](https://junglewise.ai/threats/cve-2026-124848-incorrect-default-permissions-on-session-transcripts-and-prompt)