Sign in Sign up
JA · EN · FR
SecPulse
Categories
CVE-2026-16756 high CVSS 7.5

Vulnerability in Amazon aws-smithy-http-server (CVE-2026-16756)

Summary

Vulnerability in Amazon aws-smithy-http-server (CVE-2026-16756). Risk of unauthorized operations or information disclosure. Mitigation: upgrade to 0.66.5 or later.

Original description

The description as published by the source.

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 where, under certain circumstances, allocation of resources without limits in the default aws-smithy-http-server serve() path allows unauthenticated Slowloris denial of service.

Impact

Missing connection and header-read timeouts and the absence of a concurrent-connection cap in the default serve() path of Amazon aws-smithy-http-server might allow remote attackers to cause a denial of service by opening many connections and sending partial requests that are never completed, exhausting server sockets and tasks.

Impacted versions: aws-smithy-http-server <= 0.66.4

Patches

This issue has been addressed in aws-smithy-http-server version 0.66.5. AWS recommends upgrading to the latest version and ensuring any forked or derivative code is patched to incorporate the new fixes.

Workarounds

There is no workaround besides updating to the patched version.

Contact

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

Source: AWS Security Bulletins NVD GitHub Advisory

Auto-generated summary

Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.

A vulnerability tracked as CVE-2026-16756 has been found in Amazon aws-smithy-http-server.
Risk of unauthorized operations or information disclosure. CVSS score: 7.5/10.
What to do: upgrade Amazon aws-smithy-http-server to 0.66.5 or later.
If unsure, ask your IT team or search "Amazon aws-smithy-http-server CVE-2026-16756" on the vendor's site.

CVE-2026-16756 (Amazon aws-smithy-http-server) — CWE-770 / CVSS v3 7.5
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Patched: 0.66.5 — apply immediately
Workaround: There is no workaround besides updating to the patched version.
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.

❓ What is the problem

A vulnerability (CWE-770) exists in Amazon aws-smithy-http-server.

📍 Affected scope

Check the vendor advisory for the affected versions of Amazon aws-smithy-http-server.

🔥 Severity

Severity: High (CVSS 7.5/10). Risk of unauthorized operations or information disclosure.

🔧 How to fix

Update to 0.66.5.

🛡️ Workaround

Workaround: There is no workaround besides updating to the patched version.

🔍 Detection

Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'aws-smithy-http-server' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.

Response actions

Concrete steps and command examples for SOC/SRE teams to execute in order

  1. 1
    Identify exposure identify 
    grep -r 'aws-smithy-http-server' . | grep -v node_modules

    リポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で aws-smithy-http-server を grep し、稼働しているサービス・バージョンを把握する。

  2. 2
    Apply temporary workaround mitigate 
    There is no workaround besides updating to the patched version.

    パッチが適用されるまでの応急処置として、There is no workaround besides updating to the patched version. を実施。回避策の副作用 (機能低下) を確認した上で。

  3. 3
    Apply patch patch 
    Upgrade Amazon aws-smithy-http-server to 0.66.5

    ステージング環境で 0.66.5 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。

  4. 4
    Post-deployment verification verify 
    Confirm patched version is live in production

    パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。

Affected packages

rust aws-smithy-http-server
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0.66.5"}]}]
crates.io aws-smithy-http-server
[{"type":"SEMVER","events":[{"introduced":"0"},{"fixed":"0.66.5"}]}]

References

We use cookies for analytics and ad measurement. This setting applies to all Game co., Ltd. sites. Details