CVE-2026-18140: Uncontrolled recursion in the aws-smithy-json unknown-key skip path allows unauthenticated remote denial of service in smithy-rs generated servers

Published Jul 30, 2026
·
Updated

Summary Smithy-RS is a Rust code generation and runtime framework that generates HTTP clients and servers from Smithy interface definitions, powering the AWS SDK for Rust and custom service implementations. An issue exists which allows uncontrolled recursion in the unknown-key skip path of the Amazon aws-smithy-json runtime crate in versions 0.62.6 and earlier.

Impact Uncontrolled recursion in the unknown-key skip path of the aws-smithy-json runtime crate before 0.62.7, which the smithy-rs code generator invokes from every generated struct deserializer, might allow remote unauthenticated users to cause a denial of service (process abort via stack exhaustion) via a single small HTTP request containing deeply nested JSON to a smithy-rs generated server.

Impacted versions: aws-smithy-json <= 0.62.6

Patches This issue has been addressed in aws-smithy-json version 0.62.7. We recommend upgrading to the latest version and ensuring any forked or derivative code is patched to incorporate the new fixes.

Workarounds There are no workarounds besides updating to the patched version.

References If you have any questions or comments about this advisory, AWS asks that you contact [AWS/Amazon] Security via their vulnerability reporting page or directly via email to aws-security@amazon.com. Please do not create a public GitHub issue.

Other sources

Uncontrolled recursion in the unknown-key skip path of the aws-smithy-json runtime crate before 0.62.7, which the smithy-rs code generator invokes from every generated struct deserializer, might allow remote unauthenticated users to cause a denial of service (process abort via stack exhaustion) via a single small HTTP request containing deeply nested JSON to a smithy-rs generated server.

To remediate this issue, users should upgrade to aws-smithy-json 0.62.7 or later and rebuild.

— MITRE

Affected Software

4 affected componentsFixes available
aws-smithy-json aws-smithy-json (runtime crate)<0.62.7
aws-smithy-rs generated servers
Amazon Aws-smithy-json Rust<0.62.7
rust/aws-smithy-json<=0.62.6
0.62.7

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade rust/aws-smithy-json to a version that resolves this vulnerability.

    Fixed in 0.62.7
  2. Upgrade

    Upgrade aws-smithy-json to a version that resolves this vulnerability.

    Fixed in 0.62.7
  3. Operational

    Rebuild after upgrading aws-smithy-json to 0.62.7 or later.

Event History

Jul 30, 2026
CVE Published
via MITRE·06:34 PM
Data Sourced
via MITRE·06:34 PM
DescriptionSeverityWeakness
Data Sourced
via NVD·07:17 PM
DescriptionSeverityWeaknessAffected Software
Oct 2, 2026
Advisory Published
via GitHub·10:44 PM
Data Sourced
via GitHub·10:44 PM
DescriptionSeverityWeaknessAffected Software

Frequently Asked Questions

1

What is the severity of CVE-2026-18140?

CVE-2026-18140 has a high severity rating of 7.5.

2

How do I fix CVE-2026-18140?

To fix CVE-2026-18140, update the aws-smithy-json crate to version 0.62.7 or later.

3

What type of attack does CVE-2026-18140 allow?

CVE-2026-18140 allows unauthenticated remote denial of service via uncontrolled recursion.

4

Which software components are affected by CVE-2026-18140?

The affected components include aws-smithy-json and aws-smithy-rs generated servers.

5

When was CVE-2026-18140 published?

CVE-2026-18140 was published on July 30, 2026.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203