# GHSA-g59m-gf8j-gjf5: AWS SDK for Rust v1 adopted defense in depth enhancement for region parameter value > An attacker with environment access could manipulate region parameters to route AWS API calls to malicious hosts, mitigated by upgrading the SDK. - **Severity:** Not scored - **Exploited in the wild:** Not known - **Login needed:** Not needed - **Attackable:** Over the internet - **Victim action needed:** Not needed - **Fix available:** Yes - **Published:** 8 Jan 2026 ## What is GHSA-g59m-gf8j-gjf5? GHSA-g59m-gf8j-gjf5 is a server-side request forgery vulnerability in aws-sdk-accessanalyzer, published on 8 Jan 2026. An attacker can exploit it over the internet without logging in, with no action from the victim. ### Official description ## **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 Rust. This enhancement validates that a region used to construct an endpoint URL is a valid host label. The change was released on November 6, 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 safely within the requirements of the shared responsibility model, additional safeguards have been added to support secure customer implementations. **Impacted versions**: All versions prior to [November 6, 2025 release](https://github.com/awslabs/aws-sdk-rust/releases/tag/release-2025-11-06) ## **Patches** On November 6, 2025, an enhancement [1] was made to the AWS SDK for Rust release, which validates the formatting of a region, providing additional safeguards. ## **Workarounds** No workarounds are needed, but as always developers should ensure that their application is following security best practices: - Implement proper input validation in your application code - Update to the latest AWS SDK for Rust release on a regular basis - Follow AWS security best practices [2] for SDK configuration ## **References** Contact AWS Security via the vulnerability reporting page or email [aws-security@amazon.com](mailto:aws-security@amazon.com). ## **Acknowledgement** AWS Security thanks Guy Arazi for bringing these customer security considerations to our attention through the coordinated disclosure process. [1] https://github.com/smithy-lang/smithy-rs/pull/4383 [2] https://docs.aws.amazon.com/sdk-for-rust/latest/dg/security.html ## Which versions are affected by GHSA-g59m-gf8j-gjf5? 40 open source packages ship an affected version, including aws-sdk-accessanalyzer, aws-sdk-account and aws-sdk-acm. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `aws-sdk-accessanalyzer` | crates.io | All versions | 1.96.0 | | `aws-sdk-accessanalyzer` | crates.io | All versions | 1.96.0 | | `aws-sdk-account` | crates.io | All versions | 1.92.0 | | `aws-sdk-account` | crates.io | All versions | 1.92.0 | | `aws-sdk-acm` | crates.io | All versions | 1.92.0 | | `aws-sdk-acm` | crates.io | All versions | 1.92.0 | | `aws-sdk-acmpca` | crates.io | All versions | 1.94.0 | | `aws-sdk-acmpca` | crates.io | All versions | 1.94.0 | | `aws-sdk-aiops` | crates.io | All versions | 1.18.0 | | `aws-sdk-aiops` | crates.io | All versions | 1.18.0 | | `aws-sdk-amp` | crates.io | All versions | 1.95.0 | | `aws-sdk-amp` | crates.io | All versions | 1.95.0 | | `aws-sdk-amplify` | crates.io | All versions | 1.98.0 | | `aws-sdk-amplify` | crates.io | All versions | 1.98.0 | | `aws-sdk-amplifybackend` | crates.io | All versions | 1.89.0 | | `aws-sdk-amplifybackend` | crates.io | All versions | 1.89.0 | | `aws-sdk-amplifyuibuilder` | crates.io | All versions | 1.89.0 | | `aws-sdk-amplifyuibuilder` | crates.io | All versions | 1.89.0 | | `aws-sdk-apigateway` | crates.io | All versions | 1.92.0 | | `aws-sdk-apigateway` | crates.io | All versions | 1.92.0 | | `aws-sdk-apigatewaymanagement` | crates.io | All versions | 1.89.0 | | `aws-sdk-apigatewaymanagement` | crates.io | All versions | 1.89.0 | | `aws-sdk-apigatewayv2` | crates.io | All versions | 1.91.0 | | `aws-sdk-apigatewayv2` | crates.io | All versions | 1.91.0 | | `aws-sdk-appconfig` | crates.io | All versions | 1.94.0 | | `aws-sdk-appconfig` | crates.io | All versions | 1.94.0 | | `aws-sdk-appconfigdata` | crates.io | All versions | 1.89.0 | | `aws-sdk-appconfigdata` | crates.io | All versions | 1.89.0 | | `aws-sdk-appfabric` | crates.io | All versions | 1.89.0 | | `aws-sdk-appfabric` | crates.io | All versions | 1.89.0 | | `aws-sdk-appflow` | crates.io | All versions | 1.89.0 | | `aws-sdk-appflow` | crates.io | All versions | 1.89.0 | | `aws-sdk-appintegrations` | crates.io | All versions | 1.90.0 | | `aws-sdk-appintegrations` | crates.io | All versions | 1.90.0 | | `aws-sdk-applicationautoscaling` | crates.io | All versions | 1.95.0 | | `aws-sdk-applicationautoscaling` | crates.io | All versions | 1.95.0 | | `aws-sdk-applicationcostprofiler` | crates.io | All versions | 1.89.0 | | `aws-sdk-applicationcostprofiler` | crates.io | All versions | 1.89.0 | | `aws-sdk-applicationdiscovery` | crates.io | All versions | 1.91.0 | | `aws-sdk-applicationdiscovery` | crates.io | All versions | 1.91.0 | ## How do I fix GHSA-g59m-gf8j-gjf5? Upgrade aws-sdk-accessanalyzer to 1.96.0 or later. ## Is GHSA-g59m-gf8j-gjf5 being exploited? There is no known exploitation of GHSA-g59m-gf8j-gjf5 in the wild and no public exploit code. ## Fix prompt for AI coding agents ```text Check this codebase for GHSA-g59m-gf8j-gjf5 and fix it if it is affected. What it is: GHSA-g59m-gf8j-gjf5 is a server-side request forgery vulnerability in aws-sdk-accessanalyzer, published on 8 Jan 2026. An attacker can exploit it over the internet without logging in, with no action from the victim. Exploitation: There is no known exploitation of GHSA-g59m-gf8j-gjf5 in the wild and no public exploit code. Affected packages and fixed versions: - aws-sdk-accessanalyzer (crates.io): affected all versions; fixed in 1.96.0 - aws-sdk-accessanalyzer (crates.io): affected all versions; fixed in 1.96.0 - aws-sdk-account (crates.io): affected all versions; fixed in 1.92.0 - aws-sdk-account (crates.io): affected all versions; fixed in 1.92.0 - aws-sdk-acm (crates.io): affected all versions; fixed in 1.92.0 - aws-sdk-acm (crates.io): affected all versions; fixed in 1.92.0 - aws-sdk-acmpca (crates.io): affected all versions; fixed in 1.94.0 - aws-sdk-acmpca (crates.io): affected all versions; fixed in 1.94.0 - aws-sdk-aiops (crates.io): affected all versions; fixed in 1.18.0 - aws-sdk-aiops (crates.io): affected all versions; fixed in 1.18.0 - aws-sdk-amp (crates.io): affected all versions; fixed in 1.95.0 - aws-sdk-amp (crates.io): affected all versions; fixed in 1.95.0 Task: 1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies. 2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it. 3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead. 4. Run the tests and summarise what changed and why. 5. If nothing in the project is affected, say so and change nothing. Reference: https://insights.sbomify.com/GHSA-g59m-gf8j-gjf5/ (Markdown: https://insights.sbomify.com/GHSA-g59m-gf8j-gjf5/index.md) ``` ## Sources - OSV: https://osv.dev/vulnerability/GHSA-g59m-gf8j-gjf5 --- From sbomify Insights: https://insights.sbomify.com/GHSA-g59m-gf8j-gjf5/ Summaries are generated and may contain mistakes; the official description above is the record.