Quick answers
- Is CVE-2026-10740 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-10740 being exploited in the wild.
- How severe is CVE-2026-10740?
- High severity, with a CVSS score of 5.3, published 10 June 2026.
- Which products and versions are affected?
- AWS S2n-Quic < 1.82.0, <= 1.81.0; s2n-quic (crates.io) SEMVER:introduced=0,fixed=1.82.0.
- Is there a fix for CVE-2026-10740?
- Yes. s2n-quic (crates.io): upgrade to 1.82.0 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-10740 attacked?
- It is attacked over the network.
- Am I affected by CVE-2026-10740?
- Check whether you run Amazon AWS, AWS S2n-Quic or s2n-quic (crates.io) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- s2n-quic (crates.io): upgrade to 1.82.0 or later
cargo update -p s2n-quic
Technical details
This vulnerability involves excessive memory allocation in s2n-quic, the AWS QUIC protocol implementation. An attacker can exploit the memory allocation flaw through network-based attacks to cause denial of service by exhausting memory resources. The vulnerability is reachable over the network to any system running the affected s2n-quic library. No evidence of active exploitation in the wild has been reported. Patches or mitigations are available from AWS.
Affected products
- AWS s2n-quic
Identifiers
- CVE-2026-10740
- GHSA-9q54-f358-3fqf
Timeline
- 2026-09-22: disclosed