Skip to content

Conversation

@renovate
Copy link
Contributor

@renovate renovate bot commented Jan 8, 2026

This PR contains the following updates:

Package Type Update Change
aws-sdk-s3 dev-dependencies minor 1.108.01.112.0
aws-sdk-s3 dependencies minor 1.108.01.112.0

GitHub Vulnerability Alerts

GHSA-g59m-gf8j-gjf5

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

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.

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


Configuration

📅 Schedule: Branch creation - "" (UTC), Automerge - At any time (no schedule defined).

🚦 Automerge: Enabled.

Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about these updates again.


  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.


This change is Reviewable

@renovate renovate bot enabled auto-merge (squash) January 8, 2026 23:07
@renovate renovate bot force-pushed the renovate/crate-aws-sdk-s3-vulnerability branch from 151492f to ba6b99c Compare January 14, 2026 15:42
@renovate renovate bot force-pushed the renovate/crate-aws-sdk-s3-vulnerability branch from ba6b99c to 1f8868f Compare January 15, 2026 17:03
@renovate renovate bot force-pushed the renovate/crate-aws-sdk-s3-vulnerability branch from 1f8868f to c24ecf2 Compare January 16, 2026 08:36
@palfrey
Copy link
Member

palfrey commented Jan 16, 2026

This needs a Rust version update, which will need me to sort out #2041. Closing for now.

@palfrey palfrey closed this Jan 16, 2026
auto-merge was automatically disabled January 16, 2026 10:37

Pull request was closed

@renovate
Copy link
Contributor Author

renovate bot commented Jan 16, 2026

Renovate Ignore Notification

Because you closed this PR without merging, Renovate will ignore this update (1.82.0). You will get a PR once a newer version is released. To ignore this dependency forever, add it to the ignoreDeps array of your Renovate config.

If you accidentally closed this PR, or if you changed your mind: rename this PR to get a fresh replacement PR.

@renovate renovate bot deleted the renovate/crate-aws-sdk-s3-vulnerability branch January 16, 2026 10:41
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants