Skip to main content
VulnerabilityPublished

CVE-2026-18140: aws-smithy-json · Uncontrolled Recursion

Affects aws-smithy-jsonSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 7.5 High : upgrade to 0.62.7 soon.

Data as of 29 Oct 2026, 07:15 UTC

CVSS 3.1 base score
7.5High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.7% chance of exploitation in 30 days – higher than 55% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 0.62.7
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 30 Jul 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 29 Oct 2026.

What to do

Upgrade aws-smithy-json to 0.62.7.

Affected software

ProductAffectedFixed in
AWSaws-smithy-jsonAffected
  • >=0.32.0 <=0.62.6
Fixed in–
crates.ioaws-smithy-jsonpkg:cargo/aws-smithy-jsonOther threatsAffected
  • <0.62.7
Fixed in
  • 0.62.7

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

Description

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.

References

Community reviews

Loading reviews…