https://cve.radiocsirt.org/rss/recent/all/10 Most recent entries from all 2026-10-14T17:04:00.843991+00:00 Vulnerability-Lookup csirt@opendfir.org python-feedgen Contains only the most 10 recent entries. https://cve.radiocsirt.org/vuln/euvd-2026-351690 EUVD-2026-351690 2026-10-14T17:04:00.846397+00:00 EUVD-2026-351690 https://cve.radiocsirt.org/vuln/fkie_cve-2026-16756 fkie_cve-2026-16756 2026-10-14T17:04:00.846441+00:00

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.

To mitigate this issue, users should upgrade to aws-smithy-http-server 0.66.5 or later.

 https://cve.radiocsirt.org/vuln/ghsa-jvxp-qmx7-gjpx GHSA-jvxp-qmx7-gjpx — Smithy-RS: Allocation of resources without limits in the default aws-smithy-http-server serve() path allows unauthentic… 2026-10-14T17:04:00.846492+00:00

Affected: crates.io: aws-smithy-http-server

## 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](https://aws.amazon.com/security/vulnerability-reporting) or directly via email to [aws-security@amazon.com](mailto:aws-security@amazon.com). Please do not create a public GitHub issue.