Skip to content

JavaScript SDK v2 users should add validation to the region parameter value in or migrate to v3

Low severity GitHub Reviewed Published Jan 8, 2026 in aws/aws-sdk-js • Updated Jan 8, 2026

Package

npm aws-sdk (npm)

Affected versions

>= 2.0.0, <= 3.0.0

Patched versions

None

Description

CVSSv3.1 Rating: 3.7 (LOW)

Summary
This notification is related to the use of specific values for the region input field when calling AWS services. An actor with access to the environment in which the SDK is used could set the region input field to an invalid value. Per the AWS shared responsibility model, customer applications should protect instances appropriately, or implement proper input sanitization checks. The AWS SDK for JavaScript v2 reached end-of-support on September 8, 2025, but a defense-in-depth enhancement has been implemented in AWS SDK for JavaScript v3. Please migrate to that version.

Impact
Customer applications could be configured to improperly route AWS API calls to non-existent or non-AWS hosts. While the SDK itself is functioning as designed, we recommend customers migrate to AWS SDK for JavaScript v3 for continued support and enhanced security features.

Impacted versions: All versions of AWS SDK for JavaScript v2

Patches
No security patch is required, this is an informational advisory.

Workarounds

  • Implement proper input sanitization in your application code
  • Migrate to AWS SDK for JavaScript v3
  • Follow AWS security best practices for SDK configuration

References
Contact AWS Security via the vulnerability reporting page or email [email protected].

Acknowledgement
AWS Security thanks Guy Arazi for bringing these customer security considerations to our attention through the coordinated disclosure process.

References

@aws-sdk-js-automation aws-sdk-js-automation published to aws/aws-sdk-js Jan 8, 2026
Published to the GitHub Advisory Database Jan 8, 2026
Reviewed Jan 8, 2026
Last updated Jan 8, 2026

Severity

Low

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

Attack vector
Network
Attack complexity
High
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
None
Availability
None

CVSS v3 base metrics

Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:N

EPSS score

Weaknesses

Improper Input Validation

The product receives input or data, but it does not validate or incorrectly validates that the input has the properties that are required to process the data safely and correctly. Learn more on MITRE.

CVE ID

No known CVE

GHSA ID

GHSA-j965-2qgj-vjmq

Source code

Loading Checking history
See something to contribute? Suggest improvements for this vulnerability.