CVE-2026-18140

HIGHPre-NVD 7.57.5—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 7.5 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.4% (35th percentile of EPSS-scored CVEs). GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, secondary
Trending — 3 sources updated this week
7.5EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.4%CVSS: 7.5Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

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.

CVSS v3
7.5
EG Score
7.5HIGHmedium confidence
EG Risk
38
EG Risk 38/100CISA SSVC

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity75% × 45%
Exploitation0% × 40%
Automatability30% × 15%
CISA SSVC: Track at low or medium mission impact; Track or Attend at high (mission-essential systems).
Action: A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
EPSS PROB
0.4%
EPSS %ILE
35th
KEV
Not listed

CISA SSVCTrack at low or medium mission impact; Track or Attend at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.

Exploitation none (no KEV listing, exploit record or EPSS ≥ 50%) · Automatable unknown (not published for this CVE) · Technical impact partial (CVSS below 9.0). Mission impact is CISA's Mission & Well-being decision point, and only you can judge it: high means the affected system is essential to your organisation's mission, or its compromise could cause irreversible harm to people. CISA's decision table

Published

July 30, 2026

Last Modified

August 10, 2026

Advisory Details (3)

Auto-updated Jul 30, 2026
Patch available. Sources: github.
github Patch Available

Uncontrolled recursion in the aws-smithy-json unknown-key skip path allows unauthenticated remote denial of service in smithy-rs generated servers · Advisory · smithy-lang/smithy-rs · GitHub

https://github.com/smithy-lang/smithy-rs/security/advisories/GHSA-8ffr-xgwf-xj56
generic

crates.io: Rust Package Registry

https://crates.io/crates/aws-smithy-json/0.62.7

Patch Availability(5)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
redhatopenshift-logging/vector-rhel9:17896595412026-09-23redhat
redhatopenshift-logging/vector-rhel9:17890505382026-09-16redhat
redhatgoose-0:1.38.0-1.el10_22026-09-15redhat
redhatgoose-0:1.38.0-1.el9_82026-09-15redhat
redhatopenshift-logging/vector-rhel9:17884397472026-09-10redhat

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(1 across 1 ecosystem)
crates.io(1)
PackageVulnerable rangeFix by version rangeDependents
aws-smithy-json—
  • every version up to 0.62.7: fixed in 0.62.7
—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 17× in last 7d / 72× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

Showing the most recent 100 of 139 total refreshes for this CVE.

  1. 2026-10-04 23:55 UTCEG score recompute
  2. 2026-10-04 23:55 UTCVendor advisory
  3. 2026-10-04 23:21 UTCEPSS rescore
  4. 2026-10-04 06:37 UTCEG score recompute
  5. 2026-10-04 06:37 UTCVendor advisory
  6. 2026-10-03 14:25 UTCEPSS rescore
  7. 2026-10-02 16:56 UTCEG score recompute
  8. 2026-10-02 16:56 UTCVendor advisory
  9. 2026-10-01 19:49 UTCEPSS rescore
  10. 2026-10-01 14:44 UTCVendor advisory
  11. 2026-10-01 02:52 UTCEG score recompute
  12. 2026-10-01 02:52 UTCVendor advisory
  13. 2026-09-30 15:02 UTCEPSS rescore
  14. 2026-09-29 15:20 UTCEPSS rescore
  15. 2026-09-29 06:52 UTCEG score recompute
  16. 2026-09-29 06:52 UTCVendor advisory
  17. 2026-09-28 13:51 UTCEPSS rescore
  18. 2026-09-28 07:09 UTCVendor advisory
  19. 2026-09-27 18:59 UTCEG score recompute
  20. 2026-09-27 18:59 UTCVendor advisory
  21. 2026-09-27 13:47 UTCEPSS rescore
  22. 2026-09-26 15:58 UTCEPSS rescore
  23. 2026-09-25 04:56 UTCEG score recompute
  24. 2026-09-25 04:56 UTCVendor advisory
  25. 2026-09-24 09:21 UTCVendor advisory
Show 75 more
  1. 2026-09-23 21:29 UTCEG score recompute
  2. 2026-09-23 21:29 UTCVendor advisory
  3. 2026-09-23 03:04 UTCVendor advisory
  4. 2026-09-22 15:12 UTCEG score recompute
  5. 2026-09-22 15:12 UTCVendor advisory
  6. 2026-09-20 21:15 UTCEG score recompute
  7. 2026-09-20 21:15 UTCVendor advisory
  8. 2026-09-19 23:46 UTCEG score recompute
  9. 2026-09-19 23:46 UTCVendor advisory
  10. 2026-09-19 04:14 UTCEG score recompute
  11. 2026-09-19 04:14 UTCVendor advisory
  12. 2026-09-18 19:27 UTCEPSS rescore
  13. 2026-09-18 13:34 UTCVendor advisory
  14. 2026-09-18 01:18 UTCEG score recompute
  15. 2026-09-18 01:18 UTCVendor advisory
  16. 2026-09-17 01:28 UTCEG score recompute
  17. 2026-09-17 01:28 UTCVendor advisory
  18. 2026-09-16 14:07 UTCEPSS rescore
  19. 2026-09-16 05:32 UTCEG score recompute
  20. 2026-09-16 05:32 UTCVendor advisory
  21. 2026-09-16 05:14 UTCEPSS rescore
  22. 2026-09-15 03:14 UTCEG score recompute
  23. 2026-09-15 03:14 UTCVendor advisory
  24. 2026-09-14 15:08 UTCVendor advisory
  25. 2026-09-14 03:14 UTCEG score recompute
  26. 2026-09-14 03:14 UTCVendor advisory
  27. 2026-09-13 16:46 UTCEPSS rescore
  28. 2026-09-13 15:22 UTCVendor advisory
  29. 2026-09-13 03:30 UTCVendor advisory
  30. 2026-09-12 15:37 UTCEG score recompute
  31. 2026-09-12 15:37 UTCVendor advisory
  32. 2026-09-12 15:00 UTCEPSS rescore
  33. 2026-09-12 03:45 UTCVendor advisory
  34. 2026-09-11 15:52 UTCEG score recompute
  35. 2026-09-11 15:52 UTCVendor advisory
  36. 2026-09-11 14:52 UTCEPSS rescore
  37. 2026-09-11 09:36 UTCEPSS rescore
  38. 2026-09-11 03:45 UTCVendor advisory
  39. 2026-09-10 15:53 UTCEG score recompute
  40. 2026-09-10 09:34 UTCEPSS rescore
  41. 2026-09-09 07:11 UTCEG score recompute
  42. 2026-09-08 22:00 UTCEPSS rescore
  43. 2026-09-07 19:48 UTCEG score recompute
  44. 2026-09-07 16:01 UTCEPSS rescore
  45. 2026-09-06 18:36 UTCEG score recompute
  46. 2026-09-06 13:47 UTCEPSS rescore
  47. 2026-09-05 18:49 UTCEG score recompute
  48. 2026-09-05 04:51 UTCEG score recompute
  49. 2026-09-04 11:26 UTCEG score recompute
  50. 2026-09-04 05:06 UTCEPSS rescore
  51. 2026-09-02 14:11 UTCEPSS rescore
  52. 2026-09-01 22:36 UTCEG score recompute
  53. 2026-09-01 13:53 UTCEPSS rescore
  54. 2026-09-01 04:39 UTCEPSS rescore
  55. 2026-08-30 22:18 UTCEG score recompute
  56. 2026-08-30 19:17 UTCEPSS rescore
  57. 2026-08-30 10:25 UTCEG score recompute
  58. 2026-08-30 01:22 UTCEPSS rescore
  59. 2026-08-29 22:31 UTCEG score recompute
  60. 2026-08-28 21:41 UTCEPSS rescore
  61. 2026-08-27 20:48 UTCEG score recompute
  62. 2026-08-27 14:25 UTCEPSS rescore
  63. 2026-08-26 19:17 UTCEG score recompute
  64. 2026-08-26 14:46 UTCEPSS rescore
  65. 2026-08-25 18:13 UTCEG score recompute
  66. 2026-08-25 13:48 UTCEPSS rescore
  67. 2026-08-24 18:17 UTCEG score recompute
  68. 2026-08-23 06:38 UTCEG score recompute
  69. 2026-08-23 00:19 UTCEPSS rescore
  70. 2026-08-22 06:53 UTCEG score recompute
  71. 2026-08-21 23:49 UTCEPSS rescore
  72. 2026-08-21 07:06 UTCEG score recompute
  73. 2026-08-20 22:55 UTCEPSS rescore
  74. 2026-08-19 19:28 UTCEG score recompute
  75. 2026-08-19 17:03 UTCEPSS rescore

Frequently asked(5)

What is CVE-2026-18140?
CVE-2026-18140 is a high vulnerability published on July 30, 2026. 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…
When was CVE-2026-18140 disclosed?
CVE-2026-18140 was first published on July 30, 2026, with the most recent update on August 10, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-18140 actively exploited?
CVE-2026-18140 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.4% probability of exploitation in the next 30 days (35th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-18140?
CVE-2026-18140 has a CVSS base score of 7.5 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-18140?
A fix for CVE-2026-18140 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-18140 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-18140

Explore →

Is Your Infrastructure Affected by CVE-2026-18140?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.