GHSA-j965-2qgj-vjmq JavaScript SDK v2 users should add validation to the region parameter value in or migrate to v3

Not scored Published

Attackers with environment access can manipulate region parameters to route AWS API calls to malicious hosts, requiring migration to SDK v3 or input validation.

Exploited in the wild
Not known
Login needed
Not needed
Attackable
Over the internet
Victim action needed
Not needed
Fix
None listed

What is GHSA-j965-2qgj-vjmq?

GHSA-j965-2qgj-vjmq is a server-side request forgery vulnerability in aws-sdk, published on 8 Jan 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

Official 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.

Which versions are affected by GHSA-j965-2qgj-vjmq?

2 open source packages ship an affected version, including aws-sdk.

PackageAffectedFixed in
aws-sdk npmFrom 2.0.0 to 3.0.0None
aws-sdk npmFrom 2.0.0 to 3.0.0None

How do I fix GHSA-j965-2qgj-vjmq?

No fix has been published for GHSA-j965-2qgj-vjmq yet. Limit exposure of the affected software until one is available.

Upgrade, and send outbound requests through an allow-list that blocks internal addresses. More about Server-side request forgery.

Is GHSA-j965-2qgj-vjmq being exploited?

There is no known exploitation of GHSA-j965-2qgj-vjmq in the wild and no public exploit code.

Sources

Is GHSA-j965-2qgj-vjmq in your software?

Upload an SBOM and sbomify checks it against every vulnerability here, every day.

Check your SBOMs for free