How severe is GHSA-6475-r3vj-m8vf?

GHSA-6475-r3vj-m8vf has a CVSS score of 3.7/10, rated LOW. Review your exposure and patch according to your risk tolerance.

Which packages are affected by GHSA-6475-r3vj-m8vf?

GHSA-6475-r3vj-m8vf affects the following packages: @smithy/config-resolver (npm). Ecosystems affected: npm.

How do I fix GHSA-6475-r3vj-m8vf?

Update @smithy/config-resolver to 4.4.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-6475-r3vj-m8vf is resolved across your whole dependency graph.

How do I detect GHSA-6475-r3vj-m8vf in my npm dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for @smithy/config-resolver, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate GHSA-6475-r3vj-m8vf if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

How does O3 Security protect against GHSA-6475-r3vj-m8vf?

O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-6475-r3vj-m8vf can be triaged on real exposure rather than presence alone.

Is GHSA-6475-r3vj-m8vf actively exploited in the wild?

No public exploit code has been indexed for GHSA-6475-r3vj-m8vf yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

When was GHSA-6475-r3vj-m8vf published, and has it been updated?

GHSA-6475-r3vj-m8vf was published on January 8, 2026 and was last updated on September 10, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

📦

📦 npm

Not in CISA KEV

LOW severity

GHSA-6475-r3vj-m8vf — @smithy/config-resolver

LOW

GHSA-6475-r3vj-m8vf is a low-severity (CVSS 3.7) vulnerability in @smithy/config-resolver. A fix is available for @smithy/config-resolver — see the affected versions and patch details below.

AWS SDK for JavaScript v3 adopted defense in depth enhancement for region parameter value

Published

Jan 8, 2026

Updated

Sep 10, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Sep 10, 2026 · OSV.dev, FIRST.org (EPSS)

Real-World Exposure

1 pkg affected

📦@smithy/config-resolver

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects npm packages — download data is not available via public APIs for these ecosystems.

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.

A defense-in-depth enhancement has been implemented in the AWS SDK for JavaScript v3 (versions 3.723.0 and later). This enhancement validates that a region used to construct an endpoint URL is a valid host label. The change was released on November 15, 2025. This advisory is informational to help customers understand their responsibilities regarding configuration security.

Impact Customer applications could be configured to improperly route AWS API calls to non-existent or non-AWS hosts. While the SDK was functioning as designed, additional safeguards have been added to support secure customer implementations.

Impacted versions: @smithy/config-resolver <4.4.0

Patches

On November 15, 2025, an enhancement was made to the AWS SDK for JavaScript v3 (versions 3.723.0 and later) release, which validates the formatting of a region, providing additional safeguards. A feature enhancement was implemented in @smithy/config-resolver v4.4.0. This enhancement provides additional configuration validation safeguards but does not address a security vulnerability.

Workarounds No workarounds are needed, but as always you should ensure that your application is following security best practices:

Implement proper input validation in your application code
Update to the latest AWS SDK for Javascript v3 release on a regular basis
Follow AWS security best practices [1] for SDK configuration

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

[1] https://docs.aws.amazon.com/sdk-for-javascript/v3/developer-guide/security.html

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
📦npm	`@smithy/config-resolver`	all versions	4.4.0`npm install @smithy/config-resolver@4.4.0`

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for @smithy/config-resolver, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update @smithy/config-resolver to 4.4.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-6475-r3vj-m8vf is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-6475-r3vj-m8vf can be triaged on real exposure rather than presence alone.

Tailored to GHSA-6475-r3vj-m8vf. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

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. A defense-in-depth enhancement has been implemented in the AWS SDK for JavaScript v3 (versions 3.723.0 and later). This enhancement validates that a region used to construct an endpoint URL is a valid host label. The change was released on November 15, 2025. This advisory is informational to help customers understand their respo

O3 Security · Impact-Aware SCA

Is GHSA-6475-r3vj-m8vf in your dependencies?

O3 Security finds GHSA-6475-r3vj-m8vf across npm dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.

Scan my dependencies How O3 SCA works