s2n-quic
An implementation of the IETF QUIC protocol
View on Github
Activity
- Latest release
- 3w ago
- Total releases
- 98
- Cadence
- ~15 days
- Last 12 months
- 22
Reach
- Downloads
- 666.7k
- Stars
- 1.4k
Details
- License
- Apache-2.0
- First release
- Feb 16, 2022
| Version | Released | |
|---|---|---|
1.88.0
minor
|
1.88.0
minor
Dependencies (19)
+ 11 more
Changelog
Compare changes
|
|
1.87.0
minor
|
1.87.0
minor
Dependencies (19)
+ 11 more
Changelog
Compare changes
|
|
1.86.0
minor
|
1.86.0
minor
Dependencies (19)
+ 11 more
Changelog
Compare changes
|
|
1.85.0
unknown
|
1.85.0
unknown
Dependencies (19)
+ 11 more
Changelog
Compare changes
|
|
1.84.0
unknown
| ||
1.83.0
unknown
| ||
1.82.0
unknown
| ||
1.81.0
unknown
1 CVE
CVE-2026-10740
GHSA-9q54-f358-3fqf
Aug 14, 2026
s2n-quic has excessive memory allocation
Medium
Network
Low
None
None
s2n-quic is a Rust implementation of the QUIC protocol. An unauthenticated user can attempt to exhaust server memory on an s2n-quic endpoint by sending crafted CRYPTO frames with high offsets. The buffer used for processing CRYPTO frames does not enforce a maximum size. In the worst case, a single 1200-byte packet can cause approximately 9.4 MB of allocation. By repeatedly sending such packets, the resulting memory pressure could cause denial of service. No valid handshake is required. Impacted versions: <= v1.81.0 PatchesThis issue has been addressed in s2n-quic version v1.82.0. We recommend upgrading to the latest version and ensuring any forked or derivative code is patched to incorporate the new fixes. WorkaroundsThere is no workaround that fully mitigates this issue. Upgrading to the patched version is the recommended remediation. ReferencesIf there are any questions or comments about this advisory, 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. Fixed in
1.82.0
References Updated Aug 14, 2026 · Source: OSV.dev | ||
1.80.0
unknown
1 CVE
CVE-2026-10740
GHSA-9q54-f358-3fqf
Aug 14, 2026
s2n-quic has excessive memory allocation
Medium
Network
Low
None
None
s2n-quic is a Rust implementation of the QUIC protocol. An unauthenticated user can attempt to exhaust server memory on an s2n-quic endpoint by sending crafted CRYPTO frames with high offsets. The buffer used for processing CRYPTO frames does not enforce a maximum size. In the worst case, a single 1200-byte packet can cause approximately 9.4 MB of allocation. By repeatedly sending such packets, the resulting memory pressure could cause denial of service. No valid handshake is required. Impacted versions: <= v1.81.0 PatchesThis issue has been addressed in s2n-quic version v1.82.0. We recommend upgrading to the latest version and ensuring any forked or derivative code is patched to incorporate the new fixes. WorkaroundsThere is no workaround that fully mitigates this issue. Upgrading to the patched version is the recommended remediation. ReferencesIf there are any questions or comments about this advisory, 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. Fixed in
1.82.0
References Updated Aug 14, 2026 · Source: OSV.dev | ||
1.79.0
unknown
1 CVE
CVE-2026-10740
GHSA-9q54-f358-3fqf
Aug 14, 2026
s2n-quic has excessive memory allocation
Medium
Network
Low
None
None
s2n-quic is a Rust implementation of the QUIC protocol. An unauthenticated user can attempt to exhaust server memory on an s2n-quic endpoint by sending crafted CRYPTO frames with high offsets. The buffer used for processing CRYPTO frames does not enforce a maximum size. In the worst case, a single 1200-byte packet can cause approximately 9.4 MB of allocation. By repeatedly sending such packets, the resulting memory pressure could cause denial of service. No valid handshake is required. Impacted versions: <= v1.81.0 PatchesThis issue has been addressed in s2n-quic version v1.82.0. We recommend upgrading to the latest version and ensuring any forked or derivative code is patched to incorporate the new fixes. WorkaroundsThere is no workaround that fully mitigates this issue. Upgrading to the patched version is the recommended remediation. ReferencesIf there are any questions or comments about this advisory, 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. Fixed in
1.82.0
References Updated Aug 14, 2026 · Source: OSV.dev | ||
1.78.0
unknown
1 CVE
CVE-2026-10740
GHSA-9q54-f358-3fqf
Aug 14, 2026
s2n-quic has excessive memory allocation
Medium
Network
Low
None
None
s2n-quic is a Rust implementation of the QUIC protocol. An unauthenticated user can attempt to exhaust server memory on an s2n-quic endpoint by sending crafted CRYPTO frames with high offsets. The buffer used for processing CRYPTO frames does not enforce a maximum size. In the worst case, a single 1200-byte packet can cause approximately 9.4 MB of allocation. By repeatedly sending such packets, the resulting memory pressure could cause denial of service. No valid handshake is required. Impacted versions: <= v1.81.0 PatchesThis issue has been addressed in s2n-quic version v1.82.0. We recommend upgrading to the latest version and ensuring any forked or derivative code is patched to incorporate the new fixes. WorkaroundsThere is no workaround that fully mitigates this issue. Upgrading to the patched version is the recommended remediation. ReferencesIf there are any questions or comments about this advisory, 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. Fixed in
1.82.0
References Updated Aug 14, 2026 · Source: OSV.dev | ||
1.77.0
unknown
1 CVE
CVE-2026-10740
GHSA-9q54-f358-3fqf
Aug 14, 2026
s2n-quic has excessive memory allocation
Medium
Network
Low
None
None
s2n-quic is a Rust implementation of the QUIC protocol. An unauthenticated user can attempt to exhaust server memory on an s2n-quic endpoint by sending crafted CRYPTO frames with high offsets. The buffer used for processing CRYPTO frames does not enforce a maximum size. In the worst case, a single 1200-byte packet can cause approximately 9.4 MB of allocation. By repeatedly sending such packets, the resulting memory pressure could cause denial of service. No valid handshake is required. Impacted versions: <= v1.81.0 PatchesThis issue has been addressed in s2n-quic version v1.82.0. We recommend upgrading to the latest version and ensuring any forked or derivative code is patched to incorporate the new fixes. WorkaroundsThere is no workaround that fully mitigates this issue. Upgrading to the patched version is the recommended remediation. ReferencesIf there are any questions or comments about this advisory, 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. Fixed in
1.82.0
References Updated Aug 14, 2026 · Source: OSV.dev | ||
1.76.0
unknown
1 CVE
CVE-2026-10740
GHSA-9q54-f358-3fqf
Aug 14, 2026
s2n-quic has excessive memory allocation
Medium
Network
Low
None
None
s2n-quic is a Rust implementation of the QUIC protocol. An unauthenticated user can attempt to exhaust server memory on an s2n-quic endpoint by sending crafted CRYPTO frames with high offsets. The buffer used for processing CRYPTO frames does not enforce a maximum size. In the worst case, a single 1200-byte packet can cause approximately 9.4 MB of allocation. By repeatedly sending such packets, the resulting memory pressure could cause denial of service. No valid handshake is required. Impacted versions: <= v1.81.0 PatchesThis issue has been addressed in s2n-quic version v1.82.0. We recommend upgrading to the latest version and ensuring any forked or derivative code is patched to incorporate the new fixes. WorkaroundsThere is no workaround that fully mitigates this issue. Upgrading to the patched version is the recommended remediation. ReferencesIf there are any questions or comments about this advisory, 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. Fixed in
1.82.0
References Updated Aug 14, 2026 · Source: OSV.dev | ||
1.75.0
unknown
1 CVE
CVE-2026-10740
GHSA-9q54-f358-3fqf
Aug 14, 2026
s2n-quic has excessive memory allocation
Medium
Network
Low
None
None
s2n-quic is a Rust implementation of the QUIC protocol. An unauthenticated user can attempt to exhaust server memory on an s2n-quic endpoint by sending crafted CRYPTO frames with high offsets. The buffer used for processing CRYPTO frames does not enforce a maximum size. In the worst case, a single 1200-byte packet can cause approximately 9.4 MB of allocation. By repeatedly sending such packets, the resulting memory pressure could cause denial of service. No valid handshake is required. Impacted versions: <= v1.81.0 PatchesThis issue has been addressed in s2n-quic version v1.82.0. We recommend upgrading to the latest version and ensuring any forked or derivative code is patched to incorporate the new fixes. WorkaroundsThere is no workaround that fully mitigates this issue. Upgrading to the patched version is the recommended remediation. ReferencesIf there are any questions or comments about this advisory, 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. Fixed in
1.82.0
References Updated Aug 14, 2026 · Source: OSV.dev | ||
1.74.0
unknown
1 CVE
CVE-2026-10740
GHSA-9q54-f358-3fqf
Aug 14, 2026
s2n-quic has excessive memory allocation
Medium
Network
Low
None
None
s2n-quic is a Rust implementation of the QUIC protocol. An unauthenticated user can attempt to exhaust server memory on an s2n-quic endpoint by sending crafted CRYPTO frames with high offsets. The buffer used for processing CRYPTO frames does not enforce a maximum size. In the worst case, a single 1200-byte packet can cause approximately 9.4 MB of allocation. By repeatedly sending such packets, the resulting memory pressure could cause denial of service. No valid handshake is required. Impacted versions: <= v1.81.0 PatchesThis issue has been addressed in s2n-quic version v1.82.0. We recommend upgrading to the latest version and ensuring any forked or derivative code is patched to incorporate the new fixes. WorkaroundsThere is no workaround that fully mitigates this issue. Upgrading to the patched version is the recommended remediation. ReferencesIf there are any questions or comments about this advisory, 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. Fixed in
1.82.0
References Updated Aug 14, 2026 · Source: OSV.dev | ||
1.73.0
unknown
1 CVE
CVE-2026-10740
GHSA-9q54-f358-3fqf
Aug 14, 2026
s2n-quic has excessive memory allocation
Medium
Network
Low
None
None
s2n-quic is a Rust implementation of the QUIC protocol. An unauthenticated user can attempt to exhaust server memory on an s2n-quic endpoint by sending crafted CRYPTO frames with high offsets. The buffer used for processing CRYPTO frames does not enforce a maximum size. In the worst case, a single 1200-byte packet can cause approximately 9.4 MB of allocation. By repeatedly sending such packets, the resulting memory pressure could cause denial of service. No valid handshake is required. Impacted versions: <= v1.81.0 PatchesThis issue has been addressed in s2n-quic version v1.82.0. We recommend upgrading to the latest version and ensuring any forked or derivative code is patched to incorporate the new fixes. WorkaroundsThere is no workaround that fully mitigates this issue. Upgrading to the patched version is the recommended remediation. ReferencesIf there are any questions or comments about this advisory, 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. Fixed in
1.82.0
References Updated Aug 14, 2026 · Source: OSV.dev | ||
1.72.0
unknown
1 CVE
CVE-2026-10740
GHSA-9q54-f358-3fqf
Aug 14, 2026
s2n-quic has excessive memory allocation
Medium
Network
Low
None
None
s2n-quic is a Rust implementation of the QUIC protocol. An unauthenticated user can attempt to exhaust server memory on an s2n-quic endpoint by sending crafted CRYPTO frames with high offsets. The buffer used for processing CRYPTO frames does not enforce a maximum size. In the worst case, a single 1200-byte packet can cause approximately 9.4 MB of allocation. By repeatedly sending such packets, the resulting memory pressure could cause denial of service. No valid handshake is required. Impacted versions: <= v1.81.0 PatchesThis issue has been addressed in s2n-quic version v1.82.0. We recommend upgrading to the latest version and ensuring any forked or derivative code is patched to incorporate the new fixes. WorkaroundsThere is no workaround that fully mitigates this issue. Upgrading to the patched version is the recommended remediation. ReferencesIf there are any questions or comments about this advisory, 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. Fixed in
1.82.0
References Updated Aug 14, 2026 · Source: OSV.dev | ||
1.71.0
unknown
1 CVE
CVE-2026-10740
GHSA-9q54-f358-3fqf
Aug 14, 2026
s2n-quic has excessive memory allocation
Medium
Network
Low
None
None
s2n-quic is a Rust implementation of the QUIC protocol. An unauthenticated user can attempt to exhaust server memory on an s2n-quic endpoint by sending crafted CRYPTO frames with high offsets. The buffer used for processing CRYPTO frames does not enforce a maximum size. In the worst case, a single 1200-byte packet can cause approximately 9.4 MB of allocation. By repeatedly sending such packets, the resulting memory pressure could cause denial of service. No valid handshake is required. Impacted versions: <= v1.81.0 PatchesThis issue has been addressed in s2n-quic version v1.82.0. We recommend upgrading to the latest version and ensuring any forked or derivative code is patched to incorporate the new fixes. WorkaroundsThere is no workaround that fully mitigates this issue. Upgrading to the patched version is the recommended remediation. ReferencesIf there are any questions or comments about this advisory, 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. Fixed in
1.82.0
References Updated Aug 14, 2026 · Source: OSV.dev | ||
1.70.0
unknown
1 CVE
CVE-2026-10740
GHSA-9q54-f358-3fqf
Aug 14, 2026
s2n-quic has excessive memory allocation
Medium
Network
Low
None
None
s2n-quic is a Rust implementation of the QUIC protocol. An unauthenticated user can attempt to exhaust server memory on an s2n-quic endpoint by sending crafted CRYPTO frames with high offsets. The buffer used for processing CRYPTO frames does not enforce a maximum size. In the worst case, a single 1200-byte packet can cause approximately 9.4 MB of allocation. By repeatedly sending such packets, the resulting memory pressure could cause denial of service. No valid handshake is required. Impacted versions: <= v1.81.0 PatchesThis issue has been addressed in s2n-quic version v1.82.0. We recommend upgrading to the latest version and ensuring any forked or derivative code is patched to incorporate the new fixes. WorkaroundsThere is no workaround that fully mitigates this issue. Upgrading to the patched version is the recommended remediation. ReferencesIf there are any questions or comments about this advisory, 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. Fixed in
1.82.0
References Updated Aug 14, 2026 · Source: OSV.dev | ||
1.69.0
unknown
1 CVE
CVE-2026-10740
GHSA-9q54-f358-3fqf
Aug 14, 2026
s2n-quic has excessive memory allocation
Medium
Network
Low
None
None
s2n-quic is a Rust implementation of the QUIC protocol. An unauthenticated user can attempt to exhaust server memory on an s2n-quic endpoint by sending crafted CRYPTO frames with high offsets. The buffer used for processing CRYPTO frames does not enforce a maximum size. In the worst case, a single 1200-byte packet can cause approximately 9.4 MB of allocation. By repeatedly sending such packets, the resulting memory pressure could cause denial of service. No valid handshake is required. Impacted versions: <= v1.81.0 PatchesThis issue has been addressed in s2n-quic version v1.82.0. We recommend upgrading to the latest version and ensuring any forked or derivative code is patched to incorporate the new fixes. WorkaroundsThere is no workaround that fully mitigates this issue. Upgrading to the patched version is the recommended remediation. ReferencesIf there are any questions or comments about this advisory, 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. Fixed in
1.82.0
References Updated Aug 14, 2026 · Source: OSV.dev | ||
1.68.0
unknown
1 CVE
CVE-2026-10740
GHSA-9q54-f358-3fqf
Aug 14, 2026
s2n-quic has excessive memory allocation
Medium
Network
Low
None
None
s2n-quic is a Rust implementation of the QUIC protocol. An unauthenticated user can attempt to exhaust server memory on an s2n-quic endpoint by sending crafted CRYPTO frames with high offsets. The buffer used for processing CRYPTO frames does not enforce a maximum size. In the worst case, a single 1200-byte packet can cause approximately 9.4 MB of allocation. By repeatedly sending such packets, the resulting memory pressure could cause denial of service. No valid handshake is required. Impacted versions: <= v1.81.0 PatchesThis issue has been addressed in s2n-quic version v1.82.0. We recommend upgrading to the latest version and ensuring any forked or derivative code is patched to incorporate the new fixes. WorkaroundsThere is no workaround that fully mitigates this issue. Upgrading to the patched version is the recommended remediation. ReferencesIf there are any questions or comments about this advisory, 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. Fixed in
1.82.0
References Updated Aug 14, 2026 · Source: OSV.dev | ||
1.67.0
unknown
1 CVE
CVE-2026-10740
GHSA-9q54-f358-3fqf
Aug 14, 2026
s2n-quic has excessive memory allocation
Medium
Network
Low
None
None
s2n-quic is a Rust implementation of the QUIC protocol. An unauthenticated user can attempt to exhaust server memory on an s2n-quic endpoint by sending crafted CRYPTO frames with high offsets. The buffer used for processing CRYPTO frames does not enforce a maximum size. In the worst case, a single 1200-byte packet can cause approximately 9.4 MB of allocation. By repeatedly sending such packets, the resulting memory pressure could cause denial of service. No valid handshake is required. Impacted versions: <= v1.81.0 PatchesThis issue has been addressed in s2n-quic version v1.82.0. We recommend upgrading to the latest version and ensuring any forked or derivative code is patched to incorporate the new fixes. WorkaroundsThere is no workaround that fully mitigates this issue. Upgrading to the patched version is the recommended remediation. ReferencesIf there are any questions or comments about this advisory, 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. Fixed in
1.82.0
References Updated Aug 14, 2026 · Source: OSV.dev | ||
1.66.0
unknown
1 CVE
CVE-2026-10740
GHSA-9q54-f358-3fqf
Aug 14, 2026
s2n-quic has excessive memory allocation
Medium
Network
Low
None
None
s2n-quic is a Rust implementation of the QUIC protocol. An unauthenticated user can attempt to exhaust server memory on an s2n-quic endpoint by sending crafted CRYPTO frames with high offsets. The buffer used for processing CRYPTO frames does not enforce a maximum size. In the worst case, a single 1200-byte packet can cause approximately 9.4 MB of allocation. By repeatedly sending such packets, the resulting memory pressure could cause denial of service. No valid handshake is required. Impacted versions: <= v1.81.0 PatchesThis issue has been addressed in s2n-quic version v1.82.0. We recommend upgrading to the latest version and ensuring any forked or derivative code is patched to incorporate the new fixes. WorkaroundsThere is no workaround that fully mitigates this issue. Upgrading to the patched version is the recommended remediation. ReferencesIf there are any questions or comments about this advisory, 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. Fixed in
1.82.0
References Updated Aug 14, 2026 · Source: OSV.dev | ||
1.65.0
unknown
1 CVE
CVE-2026-10740
GHSA-9q54-f358-3fqf
Aug 14, 2026
s2n-quic has excessive memory allocation
Medium
Network
Low
None
None
s2n-quic is a Rust implementation of the QUIC protocol. An unauthenticated user can attempt to exhaust server memory on an s2n-quic endpoint by sending crafted CRYPTO frames with high offsets. The buffer used for processing CRYPTO frames does not enforce a maximum size. In the worst case, a single 1200-byte packet can cause approximately 9.4 MB of allocation. By repeatedly sending such packets, the resulting memory pressure could cause denial of service. No valid handshake is required. Impacted versions: <= v1.81.0 PatchesThis issue has been addressed in s2n-quic version v1.82.0. We recommend upgrading to the latest version and ensuring any forked or derivative code is patched to incorporate the new fixes. WorkaroundsThere is no workaround that fully mitigates this issue. Upgrading to the patched version is the recommended remediation. ReferencesIf there are any questions or comments about this advisory, 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. Fixed in
1.82.0
References Updated Aug 14, 2026 · Source: OSV.dev | ||
1.64.0
unknown
1 CVE
CVE-2026-10740
GHSA-9q54-f358-3fqf
Aug 14, 2026
s2n-quic has excessive memory allocation
Medium
Network
Low
None
None
s2n-quic is a Rust implementation of the QUIC protocol. An unauthenticated user can attempt to exhaust server memory on an s2n-quic endpoint by sending crafted CRYPTO frames with high offsets. The buffer used for processing CRYPTO frames does not enforce a maximum size. In the worst case, a single 1200-byte packet can cause approximately 9.4 MB of allocation. By repeatedly sending such packets, the resulting memory pressure could cause denial of service. No valid handshake is required. Impacted versions: <= v1.81.0 PatchesThis issue has been addressed in s2n-quic version v1.82.0. We recommend upgrading to the latest version and ensuring any forked or derivative code is patched to incorporate the new fixes. WorkaroundsThere is no workaround that fully mitigates this issue. Upgrading to the patched version is the recommended remediation. ReferencesIf there are any questions or comments about this advisory, 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. Fixed in
1.82.0
References Updated Aug 14, 2026 · Source: OSV.dev | ||
1.63.0
unknown
1 CVE
CVE-2026-10740
GHSA-9q54-f358-3fqf
Aug 14, 2026
s2n-quic has excessive memory allocation
Medium
Network
Low
None
None
s2n-quic is a Rust implementation of the QUIC protocol. An unauthenticated user can attempt to exhaust server memory on an s2n-quic endpoint by sending crafted CRYPTO frames with high offsets. The buffer used for processing CRYPTO frames does not enforce a maximum size. In the worst case, a single 1200-byte packet can cause approximately 9.4 MB of allocation. By repeatedly sending such packets, the resulting memory pressure could cause denial of service. No valid handshake is required. Impacted versions: <= v1.81.0 PatchesThis issue has been addressed in s2n-quic version v1.82.0. We recommend upgrading to the latest version and ensuring any forked or derivative code is patched to incorporate the new fixes. WorkaroundsThere is no workaround that fully mitigates this issue. Upgrading to the patched version is the recommended remediation. ReferencesIf there are any questions or comments about this advisory, 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. Fixed in
1.82.0
References Updated Aug 14, 2026 · Source: OSV.dev | ||
1.62.0
unknown
1 CVE
CVE-2026-10740
GHSA-9q54-f358-3fqf
Aug 14, 2026
s2n-quic has excessive memory allocation
Medium
Network
Low
None
None
s2n-quic is a Rust implementation of the QUIC protocol. An unauthenticated user can attempt to exhaust server memory on an s2n-quic endpoint by sending crafted CRYPTO frames with high offsets. The buffer used for processing CRYPTO frames does not enforce a maximum size. In the worst case, a single 1200-byte packet can cause approximately 9.4 MB of allocation. By repeatedly sending such packets, the resulting memory pressure could cause denial of service. No valid handshake is required. Impacted versions: <= v1.81.0 PatchesThis issue has been addressed in s2n-quic version v1.82.0. We recommend upgrading to the latest version and ensuring any forked or derivative code is patched to incorporate the new fixes. WorkaroundsThere is no workaround that fully mitigates this issue. Upgrading to the patched version is the recommended remediation. ReferencesIf there are any questions or comments about this advisory, 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. Fixed in
1.82.0
References Updated Aug 14, 2026 · Source: OSV.dev | ||
1.61.0
unknown
1 CVE
CVE-2026-10740
GHSA-9q54-f358-3fqf
Aug 14, 2026
s2n-quic has excessive memory allocation
Medium
Network
Low
None
None
s2n-quic is a Rust implementation of the QUIC protocol. An unauthenticated user can attempt to exhaust server memory on an s2n-quic endpoint by sending crafted CRYPTO frames with high offsets. The buffer used for processing CRYPTO frames does not enforce a maximum size. In the worst case, a single 1200-byte packet can cause approximately 9.4 MB of allocation. By repeatedly sending such packets, the resulting memory pressure could cause denial of service. No valid handshake is required. Impacted versions: <= v1.81.0 PatchesThis issue has been addressed in s2n-quic version v1.82.0. We recommend upgrading to the latest version and ensuring any forked or derivative code is patched to incorporate the new fixes. WorkaroundsThere is no workaround that fully mitigates this issue. Upgrading to the patched version is the recommended remediation. ReferencesIf there are any questions or comments about this advisory, 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. Fixed in
1.82.0
References Updated Aug 14, 2026 · Source: OSV.dev | ||
1.60.0
unknown
1 CVE
CVE-2026-10740
GHSA-9q54-f358-3fqf
Aug 14, 2026
s2n-quic has excessive memory allocation
Medium
Network
Low
None
None
s2n-quic is a Rust implementation of the QUIC protocol. An unauthenticated user can attempt to exhaust server memory on an s2n-quic endpoint by sending crafted CRYPTO frames with high offsets. The buffer used for processing CRYPTO frames does not enforce a maximum size. In the worst case, a single 1200-byte packet can cause approximately 9.4 MB of allocation. By repeatedly sending such packets, the resulting memory pressure could cause denial of service. No valid handshake is required. Impacted versions: <= v1.81.0 PatchesThis issue has been addressed in s2n-quic version v1.82.0. We recommend upgrading to the latest version and ensuring any forked or derivative code is patched to incorporate the new fixes. WorkaroundsThere is no workaround that fully mitigates this issue. Upgrading to the patched version is the recommended remediation. ReferencesIf there are any questions or comments about this advisory, 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. Fixed in
1.82.0
References Updated Aug 14, 2026 · Source: OSV.dev | ||
1.59.0
unknown
1 CVE
CVE-2026-10740
GHSA-9q54-f358-3fqf
Aug 14, 2026
s2n-quic has excessive memory allocation
Medium
Network
Low
None
None
s2n-quic is a Rust implementation of the QUIC protocol. An unauthenticated user can attempt to exhaust server memory on an s2n-quic endpoint by sending crafted CRYPTO frames with high offsets. The buffer used for processing CRYPTO frames does not enforce a maximum size. In the worst case, a single 1200-byte packet can cause approximately 9.4 MB of allocation. By repeatedly sending such packets, the resulting memory pressure could cause denial of service. No valid handshake is required. Impacted versions: <= v1.81.0 PatchesThis issue has been addressed in s2n-quic version v1.82.0. We recommend upgrading to the latest version and ensuring any forked or derivative code is patched to incorporate the new fixes. WorkaroundsThere is no workaround that fully mitigates this issue. Upgrading to the patched version is the recommended remediation. ReferencesIf there are any questions or comments about this advisory, 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. Fixed in
1.82.0
References Updated Aug 14, 2026 · Source: OSV.dev | ||
1.58.0
unknown
1 CVE
CVE-2026-10740
GHSA-9q54-f358-3fqf
Aug 14, 2026
s2n-quic has excessive memory allocation
Medium
Network
Low
None
None
s2n-quic is a Rust implementation of the QUIC protocol. An unauthenticated user can attempt to exhaust server memory on an s2n-quic endpoint by sending crafted CRYPTO frames with high offsets. The buffer used for processing CRYPTO frames does not enforce a maximum size. In the worst case, a single 1200-byte packet can cause approximately 9.4 MB of allocation. By repeatedly sending such packets, the resulting memory pressure could cause denial of service. No valid handshake is required. Impacted versions: <= v1.81.0 PatchesThis issue has been addressed in s2n-quic version v1.82.0. We recommend upgrading to the latest version and ensuring any forked or derivative code is patched to incorporate the new fixes. WorkaroundsThere is no workaround that fully mitigates this issue. Upgrading to the patched version is the recommended remediation. ReferencesIf there are any questions or comments about this advisory, 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. Fixed in
1.82.0
References Updated Aug 14, 2026 · Source: OSV.dev | ||
1.57.0
unknown
1 CVE
CVE-2026-10740
GHSA-9q54-f358-3fqf
Aug 14, 2026
s2n-quic has excessive memory allocation
Medium
Network
Low
None
None
s2n-quic is a Rust implementation of the QUIC protocol. An unauthenticated user can attempt to exhaust server memory on an s2n-quic endpoint by sending crafted CRYPTO frames with high offsets. The buffer used for processing CRYPTO frames does not enforce a maximum size. In the worst case, a single 1200-byte packet can cause approximately 9.4 MB of allocation. By repeatedly sending such packets, the resulting memory pressure could cause denial of service. No valid handshake is required. Impacted versions: <= v1.81.0 PatchesThis issue has been addressed in s2n-quic version v1.82.0. We recommend upgrading to the latest version and ensuring any forked or derivative code is patched to incorporate the new fixes. WorkaroundsThere is no workaround that fully mitigates this issue. Upgrading to the patched version is the recommended remediation. ReferencesIf there are any questions or comments about this advisory, 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. Fixed in
1.82.0
References Updated Aug 14, 2026 · Source: OSV.dev | ||
1.56.0
unknown
1 CVE
CVE-2026-10740
GHSA-9q54-f358-3fqf
Aug 14, 2026
s2n-quic has excessive memory allocation
Medium
Network
Low
None
None
s2n-quic is a Rust implementation of the QUIC protocol. An unauthenticated user can attempt to exhaust server memory on an s2n-quic endpoint by sending crafted CRYPTO frames with high offsets. The buffer used for processing CRYPTO frames does not enforce a maximum size. In the worst case, a single 1200-byte packet can cause approximately 9.4 MB of allocation. By repeatedly sending such packets, the resulting memory pressure could cause denial of service. No valid handshake is required. Impacted versions: <= v1.81.0 PatchesThis issue has been addressed in s2n-quic version v1.82.0. We recommend upgrading to the latest version and ensuring any forked or derivative code is patched to incorporate the new fixes. WorkaroundsThere is no workaround that fully mitigates this issue. Upgrading to the patched version is the recommended remediation. ReferencesIf there are any questions or comments about this advisory, 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. Fixed in
1.82.0
References Updated Aug 14, 2026 · Source: OSV.dev | ||
1.55.0
unknown
1 CVE
CVE-2026-10740
GHSA-9q54-f358-3fqf
Aug 14, 2026
s2n-quic has excessive memory allocation
Medium
Network
Low
None
None
s2n-quic is a Rust implementation of the QUIC protocol. An unauthenticated user can attempt to exhaust server memory on an s2n-quic endpoint by sending crafted CRYPTO frames with high offsets. The buffer used for processing CRYPTO frames does not enforce a maximum size. In the worst case, a single 1200-byte packet can cause approximately 9.4 MB of allocation. By repeatedly sending such packets, the resulting memory pressure could cause denial of service. No valid handshake is required. Impacted versions: <= v1.81.0 PatchesThis issue has been addressed in s2n-quic version v1.82.0. We recommend upgrading to the latest version and ensuring any forked or derivative code is patched to incorporate the new fixes. WorkaroundsThere is no workaround that fully mitigates this issue. Upgrading to the patched version is the recommended remediation. ReferencesIf there are any questions or comments about this advisory, 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. Fixed in
1.82.0
References Updated Aug 14, 2026 · Source: OSV.dev | ||
1.54.0
unknown
1 CVE
CVE-2026-10740
GHSA-9q54-f358-3fqf
Aug 14, 2026
s2n-quic has excessive memory allocation
Medium
Network
Low
None
None
s2n-quic is a Rust implementation of the QUIC protocol. An unauthenticated user can attempt to exhaust server memory on an s2n-quic endpoint by sending crafted CRYPTO frames with high offsets. The buffer used for processing CRYPTO frames does not enforce a maximum size. In the worst case, a single 1200-byte packet can cause approximately 9.4 MB of allocation. By repeatedly sending such packets, the resulting memory pressure could cause denial of service. No valid handshake is required. Impacted versions: <= v1.81.0 PatchesThis issue has been addressed in s2n-quic version v1.82.0. We recommend upgrading to the latest version and ensuring any forked or derivative code is patched to incorporate the new fixes. WorkaroundsThere is no workaround that fully mitigates this issue. Upgrading to the patched version is the recommended remediation. ReferencesIf there are any questions or comments about this advisory, 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. Fixed in
1.82.0
References Updated Aug 14, 2026 · Source: OSV.dev | ||
1.53.0
unknown
1 CVE
CVE-2026-10740
GHSA-9q54-f358-3fqf
Aug 14, 2026
s2n-quic has excessive memory allocation
Medium
Network
Low
None
None
s2n-quic is a Rust implementation of the QUIC protocol. An unauthenticated user can attempt to exhaust server memory on an s2n-quic endpoint by sending crafted CRYPTO frames with high offsets. The buffer used for processing CRYPTO frames does not enforce a maximum size. In the worst case, a single 1200-byte packet can cause approximately 9.4 MB of allocation. By repeatedly sending such packets, the resulting memory pressure could cause denial of service. No valid handshake is required. Impacted versions: <= v1.81.0 PatchesThis issue has been addressed in s2n-quic version v1.82.0. We recommend upgrading to the latest version and ensuring any forked or derivative code is patched to incorporate the new fixes. WorkaroundsThere is no workaround that fully mitigates this issue. Upgrading to the patched version is the recommended remediation. ReferencesIf there are any questions or comments about this advisory, 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. Fixed in
1.82.0
References Updated Aug 14, 2026 · Source: OSV.dev | ||
1.52.1
unknown
1 CVE
CVE-2026-10740
GHSA-9q54-f358-3fqf
Aug 14, 2026
s2n-quic has excessive memory allocation
Medium
Network
Low
None
None
s2n-quic is a Rust implementation of the QUIC protocol. An unauthenticated user can attempt to exhaust server memory on an s2n-quic endpoint by sending crafted CRYPTO frames with high offsets. The buffer used for processing CRYPTO frames does not enforce a maximum size. In the worst case, a single 1200-byte packet can cause approximately 9.4 MB of allocation. By repeatedly sending such packets, the resulting memory pressure could cause denial of service. No valid handshake is required. Impacted versions: <= v1.81.0 PatchesThis issue has been addressed in s2n-quic version v1.82.0. We recommend upgrading to the latest version and ensuring any forked or derivative code is patched to incorporate the new fixes. WorkaroundsThere is no workaround that fully mitigates this issue. Upgrading to the patched version is the recommended remediation. ReferencesIf there are any questions or comments about this advisory, 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. Fixed in
1.82.0
References Updated Aug 14, 2026 · Source: OSV.dev | ||
1.52.0
unknown
1 CVE
CVE-2026-10740
GHSA-9q54-f358-3fqf
Aug 14, 2026
s2n-quic has excessive memory allocation
Medium
Network
Low
None
None
s2n-quic is a Rust implementation of the QUIC protocol. An unauthenticated user can attempt to exhaust server memory on an s2n-quic endpoint by sending crafted CRYPTO frames with high offsets. The buffer used for processing CRYPTO frames does not enforce a maximum size. In the worst case, a single 1200-byte packet can cause approximately 9.4 MB of allocation. By repeatedly sending such packets, the resulting memory pressure could cause denial of service. No valid handshake is required. Impacted versions: <= v1.81.0 PatchesThis issue has been addressed in s2n-quic version v1.82.0. We recommend upgrading to the latest version and ensuring any forked or derivative code is patched to incorporate the new fixes. WorkaroundsThere is no workaround that fully mitigates this issue. Upgrading to the patched version is the recommended remediation. ReferencesIf there are any questions or comments about this advisory, 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. Fixed in
1.82.0
References Updated Aug 14, 2026 · Source: OSV.dev | ||
1.51.0
unknown
1 CVE
CVE-2026-10740
GHSA-9q54-f358-3fqf
Aug 14, 2026
s2n-quic has excessive memory allocation
Medium
Network
Low
None
None
s2n-quic is a Rust implementation of the QUIC protocol. An unauthenticated user can attempt to exhaust server memory on an s2n-quic endpoint by sending crafted CRYPTO frames with high offsets. The buffer used for processing CRYPTO frames does not enforce a maximum size. In the worst case, a single 1200-byte packet can cause approximately 9.4 MB of allocation. By repeatedly sending such packets, the resulting memory pressure could cause denial of service. No valid handshake is required. Impacted versions: <= v1.81.0 PatchesThis issue has been addressed in s2n-quic version v1.82.0. We recommend upgrading to the latest version and ensuring any forked or derivative code is patched to incorporate the new fixes. WorkaroundsThere is no workaround that fully mitigates this issue. Upgrading to the patched version is the recommended remediation. ReferencesIf there are any questions or comments about this advisory, 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. Fixed in
1.82.0
References Updated Aug 14, 2026 · Source: OSV.dev | ||
1.50.0
unknown
1 CVE
CVE-2026-10740
GHSA-9q54-f358-3fqf
Aug 14, 2026
s2n-quic has excessive memory allocation
Medium
Network
Low
None
None
s2n-quic is a Rust implementation of the QUIC protocol. An unauthenticated user can attempt to exhaust server memory on an s2n-quic endpoint by sending crafted CRYPTO frames with high offsets. The buffer used for processing CRYPTO frames does not enforce a maximum size. In the worst case, a single 1200-byte packet can cause approximately 9.4 MB of allocation. By repeatedly sending such packets, the resulting memory pressure could cause denial of service. No valid handshake is required. Impacted versions: <= v1.81.0 PatchesThis issue has been addressed in s2n-quic version v1.82.0. We recommend upgrading to the latest version and ensuring any forked or derivative code is patched to incorporate the new fixes. WorkaroundsThere is no workaround that fully mitigates this issue. Upgrading to the patched version is the recommended remediation. ReferencesIf there are any questions or comments about this advisory, 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. Fixed in
1.82.0
References Updated Aug 14, 2026 · Source: OSV.dev | ||
1.49.0
unknown
1 CVE
CVE-2026-10740
GHSA-9q54-f358-3fqf
Aug 14, 2026
s2n-quic has excessive memory allocation
Medium
Network
Low
None
None
s2n-quic is a Rust implementation of the QUIC protocol. An unauthenticated user can attempt to exhaust server memory on an s2n-quic endpoint by sending crafted CRYPTO frames with high offsets. The buffer used for processing CRYPTO frames does not enforce a maximum size. In the worst case, a single 1200-byte packet can cause approximately 9.4 MB of allocation. By repeatedly sending such packets, the resulting memory pressure could cause denial of service. No valid handshake is required. Impacted versions: <= v1.81.0 PatchesThis issue has been addressed in s2n-quic version v1.82.0. We recommend upgrading to the latest version and ensuring any forked or derivative code is patched to incorporate the new fixes. WorkaroundsThere is no workaround that fully mitigates this issue. Upgrading to the patched version is the recommended remediation. ReferencesIf there are any questions or comments about this advisory, 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. Fixed in
1.82.0
References Updated Aug 14, 2026 · Source: OSV.dev | ||
1.48.0
unknown
1 CVE
CVE-2026-10740
GHSA-9q54-f358-3fqf
Aug 14, 2026
s2n-quic has excessive memory allocation
Medium
Network
Low
None
None
s2n-quic is a Rust implementation of the QUIC protocol. An unauthenticated user can attempt to exhaust server memory on an s2n-quic endpoint by sending crafted CRYPTO frames with high offsets. The buffer used for processing CRYPTO frames does not enforce a maximum size. In the worst case, a single 1200-byte packet can cause approximately 9.4 MB of allocation. By repeatedly sending such packets, the resulting memory pressure could cause denial of service. No valid handshake is required. Impacted versions: <= v1.81.0 PatchesThis issue has been addressed in s2n-quic version v1.82.0. We recommend upgrading to the latest version and ensuring any forked or derivative code is patched to incorporate the new fixes. WorkaroundsThere is no workaround that fully mitigates this issue. Upgrading to the patched version is the recommended remediation. ReferencesIf there are any questions or comments about this advisory, 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. Fixed in
1.82.0
References Updated Aug 14, 2026 · Source: OSV.dev | ||
1.47.0
unknown
1 CVE
CVE-2026-10740
GHSA-9q54-f358-3fqf
Aug 14, 2026
s2n-quic has excessive memory allocation
Medium
Network
Low
None
None
s2n-quic is a Rust implementation of the QUIC protocol. An unauthenticated user can attempt to exhaust server memory on an s2n-quic endpoint by sending crafted CRYPTO frames with high offsets. The buffer used for processing CRYPTO frames does not enforce a maximum size. In the worst case, a single 1200-byte packet can cause approximately 9.4 MB of allocation. By repeatedly sending such packets, the resulting memory pressure could cause denial of service. No valid handshake is required. Impacted versions: <= v1.81.0 PatchesThis issue has been addressed in s2n-quic version v1.82.0. We recommend upgrading to the latest version and ensuring any forked or derivative code is patched to incorporate the new fixes. WorkaroundsThere is no workaround that fully mitigates this issue. Upgrading to the patched version is the recommended remediation. ReferencesIf there are any questions or comments about this advisory, 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. Fixed in
1.82.0
References Updated Aug 14, 2026 · Source: OSV.dev | ||
1.46.0
unknown
1 CVE
CVE-2026-10740
GHSA-9q54-f358-3fqf
Aug 14, 2026
s2n-quic has excessive memory allocation
Medium
Network
Low
None
None
s2n-quic is a Rust implementation of the QUIC protocol. An unauthenticated user can attempt to exhaust server memory on an s2n-quic endpoint by sending crafted CRYPTO frames with high offsets. The buffer used for processing CRYPTO frames does not enforce a maximum size. In the worst case, a single 1200-byte packet can cause approximately 9.4 MB of allocation. By repeatedly sending such packets, the resulting memory pressure could cause denial of service. No valid handshake is required. Impacted versions: <= v1.81.0 PatchesThis issue has been addressed in s2n-quic version v1.82.0. We recommend upgrading to the latest version and ensuring any forked or derivative code is patched to incorporate the new fixes. WorkaroundsThere is no workaround that fully mitigates this issue. Upgrading to the patched version is the recommended remediation. ReferencesIf there are any questions or comments about this advisory, 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. Fixed in
1.82.0
References Updated Aug 14, 2026 · Source: OSV.dev | ||
1.45.0
unknown
1 CVE
CVE-2026-10740
GHSA-9q54-f358-3fqf
Aug 14, 2026
s2n-quic has excessive memory allocation
Medium
Network
Low
None
None
s2n-quic is a Rust implementation of the QUIC protocol. An unauthenticated user can attempt to exhaust server memory on an s2n-quic endpoint by sending crafted CRYPTO frames with high offsets. The buffer used for processing CRYPTO frames does not enforce a maximum size. In the worst case, a single 1200-byte packet can cause approximately 9.4 MB of allocation. By repeatedly sending such packets, the resulting memory pressure could cause denial of service. No valid handshake is required. Impacted versions: <= v1.81.0 PatchesThis issue has been addressed in s2n-quic version v1.82.0. We recommend upgrading to the latest version and ensuring any forked or derivative code is patched to incorporate the new fixes. WorkaroundsThere is no workaround that fully mitigates this issue. Upgrading to the patched version is the recommended remediation. ReferencesIf there are any questions or comments about this advisory, 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. Fixed in
1.82.0
References Updated Aug 14, 2026 · Source: OSV.dev | ||
1.44.1
unknown
1 CVE
CVE-2026-10740
GHSA-9q54-f358-3fqf
Aug 14, 2026
s2n-quic has excessive memory allocation
Medium
Network
Low
None
None
s2n-quic is a Rust implementation of the QUIC protocol. An unauthenticated user can attempt to exhaust server memory on an s2n-quic endpoint by sending crafted CRYPTO frames with high offsets. The buffer used for processing CRYPTO frames does not enforce a maximum size. In the worst case, a single 1200-byte packet can cause approximately 9.4 MB of allocation. By repeatedly sending such packets, the resulting memory pressure could cause denial of service. No valid handshake is required. Impacted versions: <= v1.81.0 PatchesThis issue has been addressed in s2n-quic version v1.82.0. We recommend upgrading to the latest version and ensuring any forked or derivative code is patched to incorporate the new fixes. WorkaroundsThere is no workaround that fully mitigates this issue. Upgrading to the patched version is the recommended remediation. ReferencesIf there are any questions or comments about this advisory, 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. Fixed in
1.82.0
References Updated Aug 14, 2026 · Source: OSV.dev | ||
1.44.0
unknown
1 CVE
CVE-2026-10740
GHSA-9q54-f358-3fqf
Aug 14, 2026
s2n-quic has excessive memory allocation
Medium
Network
Low
None
None
s2n-quic is a Rust implementation of the QUIC protocol. An unauthenticated user can attempt to exhaust server memory on an s2n-quic endpoint by sending crafted CRYPTO frames with high offsets. The buffer used for processing CRYPTO frames does not enforce a maximum size. In the worst case, a single 1200-byte packet can cause approximately 9.4 MB of allocation. By repeatedly sending such packets, the resulting memory pressure could cause denial of service. No valid handshake is required. Impacted versions: <= v1.81.0 PatchesThis issue has been addressed in s2n-quic version v1.82.0. We recommend upgrading to the latest version and ensuring any forked or derivative code is patched to incorporate the new fixes. WorkaroundsThere is no workaround that fully mitigates this issue. Upgrading to the patched version is the recommended remediation. ReferencesIf there are any questions or comments about this advisory, 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. Fixed in
1.82.0
References Updated Aug 14, 2026 · Source: OSV.dev | ||
1.43.0
unknown
1 CVE
CVE-2026-10740
GHSA-9q54-f358-3fqf
Aug 14, 2026
s2n-quic has excessive memory allocation
Medium
Network
Low
None
None
s2n-quic is a Rust implementation of the QUIC protocol. An unauthenticated user can attempt to exhaust server memory on an s2n-quic endpoint by sending crafted CRYPTO frames with high offsets. The buffer used for processing CRYPTO frames does not enforce a maximum size. In the worst case, a single 1200-byte packet can cause approximately 9.4 MB of allocation. By repeatedly sending such packets, the resulting memory pressure could cause denial of service. No valid handshake is required. Impacted versions: <= v1.81.0 PatchesThis issue has been addressed in s2n-quic version v1.82.0. We recommend upgrading to the latest version and ensuring any forked or derivative code is patched to incorporate the new fixes. WorkaroundsThere is no workaround that fully mitigates this issue. Upgrading to the patched version is the recommended remediation. ReferencesIf there are any questions or comments about this advisory, 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. Fixed in
1.82.0
References Updated Aug 14, 2026 · Source: OSV.dev | ||
1.42.0
unknown
1 CVE
CVE-2026-10740
GHSA-9q54-f358-3fqf
Aug 14, 2026
s2n-quic has excessive memory allocation
Medium
Network
Low
None
None
s2n-quic is a Rust implementation of the QUIC protocol. An unauthenticated user can attempt to exhaust server memory on an s2n-quic endpoint by sending crafted CRYPTO frames with high offsets. The buffer used for processing CRYPTO frames does not enforce a maximum size. In the worst case, a single 1200-byte packet can cause approximately 9.4 MB of allocation. By repeatedly sending such packets, the resulting memory pressure could cause denial of service. No valid handshake is required. Impacted versions: <= v1.81.0 PatchesThis issue has been addressed in s2n-quic version v1.82.0. We recommend upgrading to the latest version and ensuring any forked or derivative code is patched to incorporate the new fixes. WorkaroundsThere is no workaround that fully mitigates this issue. Upgrading to the patched version is the recommended remediation. ReferencesIf there are any questions or comments about this advisory, 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. Fixed in
1.82.0
References Updated Aug 14, 2026 · Source: OSV.dev | ||
1.41.0
unknown
1 CVE
CVE-2026-10740
GHSA-9q54-f358-3fqf
Aug 14, 2026
s2n-quic has excessive memory allocation
Medium
Network
Low
None
None
s2n-quic is a Rust implementation of the QUIC protocol. An unauthenticated user can attempt to exhaust server memory on an s2n-quic endpoint by sending crafted CRYPTO frames with high offsets. The buffer used for processing CRYPTO frames does not enforce a maximum size. In the worst case, a single 1200-byte packet can cause approximately 9.4 MB of allocation. By repeatedly sending such packets, the resulting memory pressure could cause denial of service. No valid handshake is required. Impacted versions: <= v1.81.0 PatchesThis issue has been addressed in s2n-quic version v1.82.0. We recommend upgrading to the latest version and ensuring any forked or derivative code is patched to incorporate the new fixes. WorkaroundsThere is no workaround that fully mitigates this issue. Upgrading to the patched version is the recommended remediation. ReferencesIf there are any questions or comments about this advisory, 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. Fixed in
1.82.0
References Updated Aug 14, 2026 · Source: OSV.dev |