Skip to content

deps(deps): bump aes from 0.9.2 to 0.9.3 - #139

Open
dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/cargo/aes-0.9.3
Open

deps(deps): bump aes from 0.9.2 to 0.9.3#139
dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/cargo/aes-0.9.3

Conversation

@dependabot

@dependabot dependabot Bot commented on behalf of github Sep 7, 2026

Copy link
Copy Markdown
Contributor

Bumps aes from 0.9.2 to 0.9.3.

Commits
  • c153436 Release aes v0.9.3 (#587)
  • 6226693 aes: disable aarch64_aes backend on Miri (#586)
  • 1013f13 kuznyechik: remove unnecessary mut in f.call() (#584)
  • 9201609 Fix build badges (#583)
  • e207dc6 ci: bump hybrid-array from 0.4.13 to 0.4.14 in the all-deps group across 1 di...
  • 9b8b0c9 aes: enable VAES backends by default, bump MSRV to 1.89 (#580)
  • See full diff in compare view

Dependabot compatibility score

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.


Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

  • @dependabot rebase will rebase this PR
  • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
  • @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
  • @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

Bumps [aes](https://github.com/RustCrypto/block-ciphers) from 0.9.2 to 0.9.3.
- [Commits](RustCrypto/block-ciphers@aes-v0.9.2...aes-v0.9.3)

---
updated-dependencies:
- dependency-name: aes
  dependency-version: 0.9.3
  dependency-type: direct:production
  update-type: version-update:semver-patch
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot @github

dependabot Bot commented on behalf of github Sep 7, 2026

Copy link
Copy Markdown
Contributor Author

Labels

The following labels could not be found: dependencies, rust, security. Please create them before Dependabot can add them to a pull request.

Please fix the above issues or remove invalid values from dependabot.yml.

@socket-security

Copy link
Copy Markdown

Review the following changes in direct dependencies. Learn more about Socket for GitHub.

Diff Package Supply Chain
Security
Vulnerability Quality Maintenance License
Updatedcargo/​aes@​0.9.2 ⏵ 0.9.310010093100100

View full report

@github-actions

github-actions Bot commented Sep 7, 2026

Copy link
Copy Markdown

🔒 Security Validation Report

Generated: Mon Sep 7 09:17:07 UTC 2026

📊 Summary

  • NIST compliance: success
  • Cryptographic validation: success
  • Constant-time operations: success
  • Memory safety: success
  • Dependency security: success
  • WASM security: success

✅ Overall Security Status: PASSED

All critical security validations passed successfully.

🔍 Details

This report covers:

  • NIST post-quantum algorithm compliance
  • Constant-time operation verification
  • Memory safety and zeroization checks
  • Dependency vulnerability scanning
  • WASM build artifact validation

📋 Next Steps

✅ Security validation passed. Code is ready for deployment.


Security validation passed! This code meets all security requirements.

@github-actions

github-actions Bot commented Sep 7, 2026

Copy link
Copy Markdown

🔍 Pull Request Summary

Generated: Mon Sep 7 09:23:19 UTC 2026

📋 Validation Results

  • Core Validation: success
  • Security Validation: success
  • Test Coverage: success
  • WASM Compatibility: success
  • Documentation: success

✅ Overall Status: PASSED

🔒 Security Checklist

  • No classical cryptographic algorithms
  • Only SHA-3 family hash functions
  • Constant-time operations
  • Proper memory zeroization
  • Input validation
  • Error handling

📝 Review Notes

Please review the security implications of this change carefully.
All cryptographic changes require security team review.


Automated validation passed! This PR is ready for review.

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.

0 participants