s2n-tls
An implementation of the TLS/SSL protocols
View on Github
Activity
- Latest release
- 2w ago
- Total releases
- 104
- Cadence
- ~15 days
- Last 12 months
- 15
Reach
- Downloads
- 8.8M
- Stars
- 4.8k
Details
- License
- Apache-2.0
- First release
- Apr 21, 2021
| Version | Released | |
|---|---|---|
0.3.43
patch
|
0.3.43
patch
Dependencies (11)
+ 3 more
Changelog
Compare changes
|
|
0.3.42
patch
|
0.3.42
patch
Dependencies (11)
+ 3 more
Changelog
Compare changes
|
|
0.3.41
unknown
|
0.3.41
unknown
Dependencies (11)
+ 3 more
Changelog
Compare changes
|
|
0.3.40
unknown
|
0.3.40
unknown
Dependencies (11)
+ 3 more
Changelog
Compare changes
|
|
0.3.39
unknown
|
0.3.39
unknown
Dependencies (11)
+ 3 more
Changelog
Compare changes
|
|
0.3.38
unknown
|
0.3.38
unknown
Dependencies (11)
+ 3 more
Changelog
Compare changes
|
|
0.3.37
unknown
|
0.3.37
unknown
Dependencies (11)
+ 3 more
Changelog
Compare changes
|
|
0.3.36
unknown
|
0.3.36
unknown
Dependencies (11)
+ 3 more
Changelog
Compare changes
|
|
0.3.35
unknown
|
0.3.35
unknown
Dependencies (11)
+ 3 more
Changelog
Compare changes
|
|
0.3.34
unknown
|
0.3.34
unknown
Dependencies (11)
+ 3 more
Changelog
Compare changes
|
|
0.3.33
unknown
|
0.3.33
unknown
Dependencies (11)
+ 3 more
Changelog
Compare changes
|
|
0.3.32
unknown
|
0.3.32
unknown
Dependencies (11)
+ 3 more
Changelog
Compare changes
|
|
0.3.31
unknown
|
0.3.31
unknown
Dependencies (11)
+ 3 more
Changelog
Compare changes
|
|
0.3.30
unknown
|
0.3.30
unknown
Dependencies (11)
+ 3 more
Changelog
Compare changes
|
|
0.3.29
unknown
|
0.3.29
unknown
Dependencies (11)
+ 3 more
Changelog
Compare changes
|
|
0.3.28
unknown
|
0.3.28
unknown
Dependencies (12)
+ 4 more
Changelog
Compare changes
|
|
0.3.26
unknown
|
0.3.26
unknown
Dependencies (12)
+ 4 more
Changelog
Compare changes
|
|
0.3.25
unknown
|
0.3.25
unknown
Dependencies (12)
+ 4 more
Changelog
Compare changes
|
|
0.3.24
unknown
|
0.3.24
unknown
Dependencies (12)
+ 4 more
Changelog
Compare changes
|
|
0.3.23
unknown
|
0.3.23
unknown
Dependencies (12)
+ 4 more
Changelog
Compare changes
|
|
0.3.22
unknown
|
0.3.22
unknown
Dependencies (12)
+ 4 more
Changelog
Compare changes
|
|
0.3.21
unknown
|
0.3.21
unknown
Dependencies (12)
+ 4 more
Changelog
Compare changes
|
|
0.3.20
unknown
|
0.3.20
unknown
Dependencies (12)
+ 4 more
Changelog
Compare changes
|
|
0.3.19
unknown
|
0.3.19
unknown
Dependencies (12)
+ 4 more
Changelog
Compare changes
|
|
0.3.18
unknown
|
0.3.18
unknown
Dependencies (12)
+ 4 more
Changelog
Compare changes
|
|
0.3.17
unknown
|
0.3.17
unknown
Dependencies (12)
+ 4 more
Changelog
Compare changes
|
|
0.3.16
unknown
|
0.3.16
unknown
Dependencies (12)
+ 4 more
Changelog
Compare changes
|
|
0.3.15
unknown
|
0.3.15
unknown
Dependencies (12)
+ 4 more
Changelog
Compare changes
|
|
0.3.14
unknown
|
0.3.14
unknown
Dependencies (12)
+ 4 more
Changelog
Compare changes
|
|
0.3.13
unknown
|
0.3.13
unknown
Dependencies (11)
+ 3 more
Changelog
Compare changes
|
|
0.3.12
unknown
|
0.3.12
unknown
Dependencies (11)
+ 3 more
Changelog
Compare changes
|
|
0.3.11
unknown
|
0.3.11
unknown
Dependencies (11)
+ 3 more
Changelog
Compare changes
|
|
0.3.10
unknown
|
0.3.10
unknown
Dependencies (11)
+ 3 more
Changelog
Compare changes
|
|
0.3.9
unknown
|
0.3.9
unknown
Dependencies (11)
+ 3 more
Changelog
Compare changes
|
|
0.3.8
unknown
|
0.3.8
unknown
Dependencies (11)
+ 3 more
Changelog
Compare changes
|
|
0.3.7
unknown
|
0.3.7
unknown
Dependencies (11)
+ 3 more
Changelog
Compare changes
|
|
0.3.6
unknown
1 CVE
GHSA-rp9h-rf7g-hwgr
Nov 14, 2024
s2n-tls has undefined behavior at process exit
Low
Impacts2n-tls uses the Linux atexit function to register functions that clean up the global state when the process exits. In multi-threaded environments, the atexit handler may clean up state which is still in use by other threads. When this occurs, the exiting process may experience a segmentation fault or other undefined behavior. Customers of AWS services do not need to take action. Applications using s2n-tls should upgrade to the most recent release of s2n-tls. Impacted versions: < v1.5.9. PatchesThe patch commit 493b771 is included in s2n-tls v1.5.9 [1] WorkaroundsThe atexit handler may be disabled by calling If you have any questions or comments about this advisory, we ask that you contact AWS/Amazon Security via our vulnerability reporting page [2] or directly via email to aws-security@amazon.com. Please do not create a public GitHub issue. [1] https://github.com/aws/s2n-tls/releases/tag/v1.5.9 [2] Vulnerability reporting page: https://aws.amazon.com/security/vulnerability-reporting Fixed in
0.3.7
References Updated Sep 10, 2026 · Source: OSV.dev |
0.3.6
unknown
Dependencies (11)
+ 3 more
Changelog
Compare changes
|
|
0.3.5
unknown
1 CVE
GHSA-rp9h-rf7g-hwgr
Nov 14, 2024
s2n-tls has undefined behavior at process exit
Low
Impacts2n-tls uses the Linux atexit function to register functions that clean up the global state when the process exits. In multi-threaded environments, the atexit handler may clean up state which is still in use by other threads. When this occurs, the exiting process may experience a segmentation fault or other undefined behavior. Customers of AWS services do not need to take action. Applications using s2n-tls should upgrade to the most recent release of s2n-tls. Impacted versions: < v1.5.9. PatchesThe patch commit 493b771 is included in s2n-tls v1.5.9 [1] WorkaroundsThe atexit handler may be disabled by calling If you have any questions or comments about this advisory, we ask that you contact AWS/Amazon Security via our vulnerability reporting page [2] or directly via email to aws-security@amazon.com. Please do not create a public GitHub issue. [1] https://github.com/aws/s2n-tls/releases/tag/v1.5.9 [2] Vulnerability reporting page: https://aws.amazon.com/security/vulnerability-reporting Fixed in
0.3.7
References Updated Sep 10, 2026 · Source: OSV.dev |
0.3.5
unknown
Dependencies (11)
+ 3 more
Changelog
Compare changes
|
|
0.3.4
unknown
1 CVE
GHSA-rp9h-rf7g-hwgr
Nov 14, 2024
s2n-tls has undefined behavior at process exit
Low
Impacts2n-tls uses the Linux atexit function to register functions that clean up the global state when the process exits. In multi-threaded environments, the atexit handler may clean up state which is still in use by other threads. When this occurs, the exiting process may experience a segmentation fault or other undefined behavior. Customers of AWS services do not need to take action. Applications using s2n-tls should upgrade to the most recent release of s2n-tls. Impacted versions: < v1.5.9. PatchesThe patch commit 493b771 is included in s2n-tls v1.5.9 [1] WorkaroundsThe atexit handler may be disabled by calling If you have any questions or comments about this advisory, we ask that you contact AWS/Amazon Security via our vulnerability reporting page [2] or directly via email to aws-security@amazon.com. Please do not create a public GitHub issue. [1] https://github.com/aws/s2n-tls/releases/tag/v1.5.9 [2] Vulnerability reporting page: https://aws.amazon.com/security/vulnerability-reporting Fixed in
0.3.7
References Updated Sep 10, 2026 · Source: OSV.dev |
0.3.4
unknown
Dependencies (11)
+ 3 more
Changelog
Compare changes
|
|
0.3.3
unknown
1 CVE
GHSA-rp9h-rf7g-hwgr
Nov 14, 2024
s2n-tls has undefined behavior at process exit
Low
Impacts2n-tls uses the Linux atexit function to register functions that clean up the global state when the process exits. In multi-threaded environments, the atexit handler may clean up state which is still in use by other threads. When this occurs, the exiting process may experience a segmentation fault or other undefined behavior. Customers of AWS services do not need to take action. Applications using s2n-tls should upgrade to the most recent release of s2n-tls. Impacted versions: < v1.5.9. PatchesThe patch commit 493b771 is included in s2n-tls v1.5.9 [1] WorkaroundsThe atexit handler may be disabled by calling If you have any questions or comments about this advisory, we ask that you contact AWS/Amazon Security via our vulnerability reporting page [2] or directly via email to aws-security@amazon.com. Please do not create a public GitHub issue. [1] https://github.com/aws/s2n-tls/releases/tag/v1.5.9 [2] Vulnerability reporting page: https://aws.amazon.com/security/vulnerability-reporting Fixed in
0.3.7
References Updated Sep 10, 2026 · Source: OSV.dev |
0.3.3
unknown
Dependencies (11)
+ 3 more
Changelog
Compare changes
|
|
0.3.2
unknown
1 CVE
GHSA-rp9h-rf7g-hwgr
Nov 14, 2024
s2n-tls has undefined behavior at process exit
Low
Impacts2n-tls uses the Linux atexit function to register functions that clean up the global state when the process exits. In multi-threaded environments, the atexit handler may clean up state which is still in use by other threads. When this occurs, the exiting process may experience a segmentation fault or other undefined behavior. Customers of AWS services do not need to take action. Applications using s2n-tls should upgrade to the most recent release of s2n-tls. Impacted versions: < v1.5.9. PatchesThe patch commit 493b771 is included in s2n-tls v1.5.9 [1] WorkaroundsThe atexit handler may be disabled by calling If you have any questions or comments about this advisory, we ask that you contact AWS/Amazon Security via our vulnerability reporting page [2] or directly via email to aws-security@amazon.com. Please do not create a public GitHub issue. [1] https://github.com/aws/s2n-tls/releases/tag/v1.5.9 [2] Vulnerability reporting page: https://aws.amazon.com/security/vulnerability-reporting Fixed in
0.3.7
References Updated Sep 10, 2026 · Source: OSV.dev |
0.3.2
unknown
Dependencies (11)
+ 3 more
Changelog
Compare changes
|
|
0.3.1
unknown
1 CVE
GHSA-rp9h-rf7g-hwgr
Nov 14, 2024
s2n-tls has undefined behavior at process exit
Low
Impacts2n-tls uses the Linux atexit function to register functions that clean up the global state when the process exits. In multi-threaded environments, the atexit handler may clean up state which is still in use by other threads. When this occurs, the exiting process may experience a segmentation fault or other undefined behavior. Customers of AWS services do not need to take action. Applications using s2n-tls should upgrade to the most recent release of s2n-tls. Impacted versions: < v1.5.9. PatchesThe patch commit 493b771 is included in s2n-tls v1.5.9 [1] WorkaroundsThe atexit handler may be disabled by calling If you have any questions or comments about this advisory, we ask that you contact AWS/Amazon Security via our vulnerability reporting page [2] or directly via email to aws-security@amazon.com. Please do not create a public GitHub issue. [1] https://github.com/aws/s2n-tls/releases/tag/v1.5.9 [2] Vulnerability reporting page: https://aws.amazon.com/security/vulnerability-reporting Fixed in
0.3.7
References Updated Sep 10, 2026 · Source: OSV.dev |
0.3.1
unknown
Dependencies (12)
+ 4 more
Changelog
Compare changes
|
|
0.3.0
unknown
1 CVE
GHSA-rp9h-rf7g-hwgr
Nov 14, 2024
s2n-tls has undefined behavior at process exit
Low
Impacts2n-tls uses the Linux atexit function to register functions that clean up the global state when the process exits. In multi-threaded environments, the atexit handler may clean up state which is still in use by other threads. When this occurs, the exiting process may experience a segmentation fault or other undefined behavior. Customers of AWS services do not need to take action. Applications using s2n-tls should upgrade to the most recent release of s2n-tls. Impacted versions: < v1.5.9. PatchesThe patch commit 493b771 is included in s2n-tls v1.5.9 [1] WorkaroundsThe atexit handler may be disabled by calling If you have any questions or comments about this advisory, we ask that you contact AWS/Amazon Security via our vulnerability reporting page [2] or directly via email to aws-security@amazon.com. Please do not create a public GitHub issue. [1] https://github.com/aws/s2n-tls/releases/tag/v1.5.9 [2] Vulnerability reporting page: https://aws.amazon.com/security/vulnerability-reporting Fixed in
0.3.7
References Updated Sep 10, 2026 · Source: OSV.dev |
0.3.0
unknown
Dependencies (12)
+ 4 more
Changelog
Compare changes
|
|
0.2.11
unknown
2 CVEs
GHSA-rp9h-rf7g-hwgr
Nov 14, 2024
s2n-tls has undefined behavior at process exit
Low
Impacts2n-tls uses the Linux atexit function to register functions that clean up the global state when the process exits. In multi-threaded environments, the atexit handler may clean up state which is still in use by other threads. When this occurs, the exiting process may experience a segmentation fault or other undefined behavior. Customers of AWS services do not need to take action. Applications using s2n-tls should upgrade to the most recent release of s2n-tls. Impacted versions: < v1.5.9. PatchesThe patch commit 493b771 is included in s2n-tls v1.5.9 [1] WorkaroundsThe atexit handler may be disabled by calling If you have any questions or comments about this advisory, we ask that you contact AWS/Amazon Security via our vulnerability reporting page [2] or directly via email to aws-security@amazon.com. Please do not create a public GitHub issue. [1] https://github.com/aws/s2n-tls/releases/tag/v1.5.9 [2] Vulnerability reporting page: https://aws.amazon.com/security/vulnerability-reporting Fixed in
0.3.7
References Updated Sep 10, 2026 · Source: OSV.dev
GHSA-857q-xmph-p2v5
Aug 09, 2024
s2n-tls's mTLS API ordering may skip client authentication
Medium
Network
Low
None
None
ImpactAn API ordering issue in s2n-tls can cause client authentication to unexpectedly not be enabled on the server when it otherwise appears to be. Server applications are impacted if client authentication is enabled by calling s2n_connection_set_config() before calling s2n_connection_set_client_auth_type(). Applications are not impacted if these APIs are called in the opposite order, or if client authentication is enabled on the config with s2n_config_set_client_auth_type(). s2n-tls clients verifying server certificates are not impacted. Impacted versions: < v1.5.0. PatchesThe patch is included in v1.5.0 [1]. WorkaroundsApplications can workaround this issue by calling s2n_connection_set_config() after calling s2n_connection_set_client_auth_type(), or by enabling client authentication on the config with s2n_config_set_client_auth_type(). If you have any questions or comments about this advisory we ask that you contact AWS/Amazon Security via our vulnerability reporting page [2] or directly via email to aws-security@amazon.com. Please do not create a public GitHub issue. [1] https://github.com/aws/s2n-tls/releases/tag/v1.5.0 [2] https://aws.amazon.com/security/vulnerability-reporting Fixed in
0.3.0
References Updated Sep 10, 2026 · Source: OSV.dev |
0.2.11
unknown
Dependencies (12)
+ 4 more
Changelog
Compare changes
|
|
0.2.10
unknown
yanked
2 CVEs
GHSA-rp9h-rf7g-hwgr
Nov 14, 2024
s2n-tls has undefined behavior at process exit
Low
Impacts2n-tls uses the Linux atexit function to register functions that clean up the global state when the process exits. In multi-threaded environments, the atexit handler may clean up state which is still in use by other threads. When this occurs, the exiting process may experience a segmentation fault or other undefined behavior. Customers of AWS services do not need to take action. Applications using s2n-tls should upgrade to the most recent release of s2n-tls. Impacted versions: < v1.5.9. PatchesThe patch commit 493b771 is included in s2n-tls v1.5.9 [1] WorkaroundsThe atexit handler may be disabled by calling If you have any questions or comments about this advisory, we ask that you contact AWS/Amazon Security via our vulnerability reporting page [2] or directly via email to aws-security@amazon.com. Please do not create a public GitHub issue. [1] https://github.com/aws/s2n-tls/releases/tag/v1.5.9 [2] Vulnerability reporting page: https://aws.amazon.com/security/vulnerability-reporting Fixed in
0.3.7
References Updated Sep 10, 2026 · Source: OSV.dev
GHSA-857q-xmph-p2v5
Aug 09, 2024
s2n-tls's mTLS API ordering may skip client authentication
Medium
Network
Low
None
None
ImpactAn API ordering issue in s2n-tls can cause client authentication to unexpectedly not be enabled on the server when it otherwise appears to be. Server applications are impacted if client authentication is enabled by calling s2n_connection_set_config() before calling s2n_connection_set_client_auth_type(). Applications are not impacted if these APIs are called in the opposite order, or if client authentication is enabled on the config with s2n_config_set_client_auth_type(). s2n-tls clients verifying server certificates are not impacted. Impacted versions: < v1.5.0. PatchesThe patch is included in v1.5.0 [1]. WorkaroundsApplications can workaround this issue by calling s2n_connection_set_config() after calling s2n_connection_set_client_auth_type(), or by enabling client authentication on the config with s2n_config_set_client_auth_type(). If you have any questions or comments about this advisory we ask that you contact AWS/Amazon Security via our vulnerability reporting page [2] or directly via email to aws-security@amazon.com. Please do not create a public GitHub issue. [1] https://github.com/aws/s2n-tls/releases/tag/v1.5.0 [2] https://aws.amazon.com/security/vulnerability-reporting Fixed in
0.3.0
References Updated Sep 10, 2026 · Source: OSV.dev |
0.2.10
unknown
yanked
Dependencies (12)
+ 4 more
Changelog
Compare changes
|
|
0.2.9
unknown
2 CVEs
GHSA-rp9h-rf7g-hwgr
Nov 14, 2024
s2n-tls has undefined behavior at process exit
Low
Impacts2n-tls uses the Linux atexit function to register functions that clean up the global state when the process exits. In multi-threaded environments, the atexit handler may clean up state which is still in use by other threads. When this occurs, the exiting process may experience a segmentation fault or other undefined behavior. Customers of AWS services do not need to take action. Applications using s2n-tls should upgrade to the most recent release of s2n-tls. Impacted versions: < v1.5.9. PatchesThe patch commit 493b771 is included in s2n-tls v1.5.9 [1] WorkaroundsThe atexit handler may be disabled by calling If you have any questions or comments about this advisory, we ask that you contact AWS/Amazon Security via our vulnerability reporting page [2] or directly via email to aws-security@amazon.com. Please do not create a public GitHub issue. [1] https://github.com/aws/s2n-tls/releases/tag/v1.5.9 [2] Vulnerability reporting page: https://aws.amazon.com/security/vulnerability-reporting Fixed in
0.3.7
References Updated Sep 10, 2026 · Source: OSV.dev
GHSA-857q-xmph-p2v5
Aug 09, 2024
s2n-tls's mTLS API ordering may skip client authentication
Medium
Network
Low
None
None
ImpactAn API ordering issue in s2n-tls can cause client authentication to unexpectedly not be enabled on the server when it otherwise appears to be. Server applications are impacted if client authentication is enabled by calling s2n_connection_set_config() before calling s2n_connection_set_client_auth_type(). Applications are not impacted if these APIs are called in the opposite order, or if client authentication is enabled on the config with s2n_config_set_client_auth_type(). s2n-tls clients verifying server certificates are not impacted. Impacted versions: < v1.5.0. PatchesThe patch is included in v1.5.0 [1]. WorkaroundsApplications can workaround this issue by calling s2n_connection_set_config() after calling s2n_connection_set_client_auth_type(), or by enabling client authentication on the config with s2n_config_set_client_auth_type(). If you have any questions or comments about this advisory we ask that you contact AWS/Amazon Security via our vulnerability reporting page [2] or directly via email to aws-security@amazon.com. Please do not create a public GitHub issue. [1] https://github.com/aws/s2n-tls/releases/tag/v1.5.0 [2] https://aws.amazon.com/security/vulnerability-reporting Fixed in
0.3.0
References Updated Sep 10, 2026 · Source: OSV.dev |
0.2.9
unknown
Dependencies (10)
+ 2 more
Changelog
Compare changes
|
|
0.2.8
unknown
2 CVEs
GHSA-rp9h-rf7g-hwgr
Nov 14, 2024
s2n-tls has undefined behavior at process exit
Low
Impacts2n-tls uses the Linux atexit function to register functions that clean up the global state when the process exits. In multi-threaded environments, the atexit handler may clean up state which is still in use by other threads. When this occurs, the exiting process may experience a segmentation fault or other undefined behavior. Customers of AWS services do not need to take action. Applications using s2n-tls should upgrade to the most recent release of s2n-tls. Impacted versions: < v1.5.9. PatchesThe patch commit 493b771 is included in s2n-tls v1.5.9 [1] WorkaroundsThe atexit handler may be disabled by calling If you have any questions or comments about this advisory, we ask that you contact AWS/Amazon Security via our vulnerability reporting page [2] or directly via email to aws-security@amazon.com. Please do not create a public GitHub issue. [1] https://github.com/aws/s2n-tls/releases/tag/v1.5.9 [2] Vulnerability reporting page: https://aws.amazon.com/security/vulnerability-reporting Fixed in
0.3.7
References Updated Sep 10, 2026 · Source: OSV.dev
GHSA-857q-xmph-p2v5
Aug 09, 2024
s2n-tls's mTLS API ordering may skip client authentication
Medium
Network
Low
None
None
ImpactAn API ordering issue in s2n-tls can cause client authentication to unexpectedly not be enabled on the server when it otherwise appears to be. Server applications are impacted if client authentication is enabled by calling s2n_connection_set_config() before calling s2n_connection_set_client_auth_type(). Applications are not impacted if these APIs are called in the opposite order, or if client authentication is enabled on the config with s2n_config_set_client_auth_type(). s2n-tls clients verifying server certificates are not impacted. Impacted versions: < v1.5.0. PatchesThe patch is included in v1.5.0 [1]. WorkaroundsApplications can workaround this issue by calling s2n_connection_set_config() after calling s2n_connection_set_client_auth_type(), or by enabling client authentication on the config with s2n_config_set_client_auth_type(). If you have any questions or comments about this advisory we ask that you contact AWS/Amazon Security via our vulnerability reporting page [2] or directly via email to aws-security@amazon.com. Please do not create a public GitHub issue. [1] https://github.com/aws/s2n-tls/releases/tag/v1.5.0 [2] https://aws.amazon.com/security/vulnerability-reporting Fixed in
0.3.0
References Updated Sep 10, 2026 · Source: OSV.dev | ||
0.2.7
unknown
2 CVEs
GHSA-rp9h-rf7g-hwgr
Nov 14, 2024
s2n-tls has undefined behavior at process exit
Low
Impacts2n-tls uses the Linux atexit function to register functions that clean up the global state when the process exits. In multi-threaded environments, the atexit handler may clean up state which is still in use by other threads. When this occurs, the exiting process may experience a segmentation fault or other undefined behavior. Customers of AWS services do not need to take action. Applications using s2n-tls should upgrade to the most recent release of s2n-tls. Impacted versions: < v1.5.9. PatchesThe patch commit 493b771 is included in s2n-tls v1.5.9 [1] WorkaroundsThe atexit handler may be disabled by calling If you have any questions or comments about this advisory, we ask that you contact AWS/Amazon Security via our vulnerability reporting page [2] or directly via email to aws-security@amazon.com. Please do not create a public GitHub issue. [1] https://github.com/aws/s2n-tls/releases/tag/v1.5.9 [2] Vulnerability reporting page: https://aws.amazon.com/security/vulnerability-reporting Fixed in
0.3.7
References Updated Sep 10, 2026 · Source: OSV.dev
GHSA-857q-xmph-p2v5
Aug 09, 2024
s2n-tls's mTLS API ordering may skip client authentication
Medium
Network
Low
None
None
ImpactAn API ordering issue in s2n-tls can cause client authentication to unexpectedly not be enabled on the server when it otherwise appears to be. Server applications are impacted if client authentication is enabled by calling s2n_connection_set_config() before calling s2n_connection_set_client_auth_type(). Applications are not impacted if these APIs are called in the opposite order, or if client authentication is enabled on the config with s2n_config_set_client_auth_type(). s2n-tls clients verifying server certificates are not impacted. Impacted versions: < v1.5.0. PatchesThe patch is included in v1.5.0 [1]. WorkaroundsApplications can workaround this issue by calling s2n_connection_set_config() after calling s2n_connection_set_client_auth_type(), or by enabling client authentication on the config with s2n_config_set_client_auth_type(). If you have any questions or comments about this advisory we ask that you contact AWS/Amazon Security via our vulnerability reporting page [2] or directly via email to aws-security@amazon.com. Please do not create a public GitHub issue. [1] https://github.com/aws/s2n-tls/releases/tag/v1.5.0 [2] https://aws.amazon.com/security/vulnerability-reporting Fixed in
0.3.0
References Updated Sep 10, 2026 · Source: OSV.dev | ||
0.2.6
unknown
3 CVEs
GHSA-rp9h-rf7g-hwgr
Nov 14, 2024
s2n-tls has undefined behavior at process exit
Low
Impacts2n-tls uses the Linux atexit function to register functions that clean up the global state when the process exits. In multi-threaded environments, the atexit handler may clean up state which is still in use by other threads. When this occurs, the exiting process may experience a segmentation fault or other undefined behavior. Customers of AWS services do not need to take action. Applications using s2n-tls should upgrade to the most recent release of s2n-tls. Impacted versions: < v1.5.9. PatchesThe patch commit 493b771 is included in s2n-tls v1.5.9 [1] WorkaroundsThe atexit handler may be disabled by calling If you have any questions or comments about this advisory, we ask that you contact AWS/Amazon Security via our vulnerability reporting page [2] or directly via email to aws-security@amazon.com. Please do not create a public GitHub issue. [1] https://github.com/aws/s2n-tls/releases/tag/v1.5.9 [2] Vulnerability reporting page: https://aws.amazon.com/security/vulnerability-reporting Fixed in
0.3.7
References Updated Sep 10, 2026 · Source: OSV.dev
GHSA-857q-xmph-p2v5
Aug 09, 2024
s2n-tls's mTLS API ordering may skip client authentication
Medium
Network
Low
None
None
ImpactAn API ordering issue in s2n-tls can cause client authentication to unexpectedly not be enabled on the server when it otherwise appears to be. Server applications are impacted if client authentication is enabled by calling s2n_connection_set_config() before calling s2n_connection_set_client_auth_type(). Applications are not impacted if these APIs are called in the opposite order, or if client authentication is enabled on the config with s2n_config_set_client_auth_type(). s2n-tls clients verifying server certificates are not impacted. Impacted versions: < v1.5.0. PatchesThe patch is included in v1.5.0 [1]. WorkaroundsApplications can workaround this issue by calling s2n_connection_set_config() after calling s2n_connection_set_client_auth_type(), or by enabling client authentication on the config with s2n_config_set_client_auth_type(). If you have any questions or comments about this advisory we ask that you contact AWS/Amazon Security via our vulnerability reporting page [2] or directly via email to aws-security@amazon.com. Please do not create a public GitHub issue. [1] https://github.com/aws/s2n-tls/releases/tag/v1.5.0 [2] https://aws.amazon.com/security/vulnerability-reporting Fixed in
0.3.0
References Updated Sep 10, 2026 · Source: OSV.dev
GHSA-52xf-5p2m-9wrv
Jun 06, 2024
s2n-tls has a potentially observable differences in RSA premaster secret handling
Low
When receiving a message from a client that sent an invalid RSA premaster secret, an issue in s2n-tls results in the server performing additional processing when the premaster secret contains an incorrect client hello version. While no practical attack on s2n-tls has been demonstrated, this causes a small timing difference which could theoretically be used as described in the Marvin Attack [1]. We would like to thank Hubert Kario [2] for reporting this issue. ImpactThe extent of this issue is a timing difference. No practical attack on s2n-tls has been demonstrated. This issue affects server applications that permit RSA key exchange. Applications that use the default, built-in blinding feature or properly implement self-service blinding are not affected. Impacted versions: <= v1.4.15. PatchesThe patch is included in v1.4.16 [3]. WorkaroundsApplications can work around this issue by using an s2n-tls security policy that disallows RSA key exchange. If you have any questions or comments about this advisory we ask that you contact AWS/Amazon Security via our vulnerability reporting page [4] or directly via email to aws-security@amazon.com. Please do not create a public GitHub issue. [1] https://people.redhat.com/~hkario/marvin/ [2] https://github.com/tomato42 [3] https://github.com/aws/s2n-tls/releases/tag/v1.4.16 [4] https://aws.amazon.com/security/vulnerability-reporting Fixed in
0.2.7
References Updated Sep 10, 2026 · Source: OSV.dev | ||
0.2.5
unknown
3 CVEs
GHSA-rp9h-rf7g-hwgr
Nov 14, 2024
s2n-tls has undefined behavior at process exit
Low
Impacts2n-tls uses the Linux atexit function to register functions that clean up the global state when the process exits. In multi-threaded environments, the atexit handler may clean up state which is still in use by other threads. When this occurs, the exiting process may experience a segmentation fault or other undefined behavior. Customers of AWS services do not need to take action. Applications using s2n-tls should upgrade to the most recent release of s2n-tls. Impacted versions: < v1.5.9. PatchesThe patch commit 493b771 is included in s2n-tls v1.5.9 [1] WorkaroundsThe atexit handler may be disabled by calling If you have any questions or comments about this advisory, we ask that you contact AWS/Amazon Security via our vulnerability reporting page [2] or directly via email to aws-security@amazon.com. Please do not create a public GitHub issue. [1] https://github.com/aws/s2n-tls/releases/tag/v1.5.9 [2] Vulnerability reporting page: https://aws.amazon.com/security/vulnerability-reporting Fixed in
0.3.7
References Updated Sep 10, 2026 · Source: OSV.dev
GHSA-857q-xmph-p2v5
Aug 09, 2024
s2n-tls's mTLS API ordering may skip client authentication
Medium
Network
Low
None
None
ImpactAn API ordering issue in s2n-tls can cause client authentication to unexpectedly not be enabled on the server when it otherwise appears to be. Server applications are impacted if client authentication is enabled by calling s2n_connection_set_config() before calling s2n_connection_set_client_auth_type(). Applications are not impacted if these APIs are called in the opposite order, or if client authentication is enabled on the config with s2n_config_set_client_auth_type(). s2n-tls clients verifying server certificates are not impacted. Impacted versions: < v1.5.0. PatchesThe patch is included in v1.5.0 [1]. WorkaroundsApplications can workaround this issue by calling s2n_connection_set_config() after calling s2n_connection_set_client_auth_type(), or by enabling client authentication on the config with s2n_config_set_client_auth_type(). If you have any questions or comments about this advisory we ask that you contact AWS/Amazon Security via our vulnerability reporting page [2] or directly via email to aws-security@amazon.com. Please do not create a public GitHub issue. [1] https://github.com/aws/s2n-tls/releases/tag/v1.5.0 [2] https://aws.amazon.com/security/vulnerability-reporting Fixed in
0.3.0
References Updated Sep 10, 2026 · Source: OSV.dev
GHSA-52xf-5p2m-9wrv
Jun 06, 2024
s2n-tls has a potentially observable differences in RSA premaster secret handling
Low
When receiving a message from a client that sent an invalid RSA premaster secret, an issue in s2n-tls results in the server performing additional processing when the premaster secret contains an incorrect client hello version. While no practical attack on s2n-tls has been demonstrated, this causes a small timing difference which could theoretically be used as described in the Marvin Attack [1]. We would like to thank Hubert Kario [2] for reporting this issue. ImpactThe extent of this issue is a timing difference. No practical attack on s2n-tls has been demonstrated. This issue affects server applications that permit RSA key exchange. Applications that use the default, built-in blinding feature or properly implement self-service blinding are not affected. Impacted versions: <= v1.4.15. PatchesThe patch is included in v1.4.16 [3]. WorkaroundsApplications can work around this issue by using an s2n-tls security policy that disallows RSA key exchange. If you have any questions or comments about this advisory we ask that you contact AWS/Amazon Security via our vulnerability reporting page [4] or directly via email to aws-security@amazon.com. Please do not create a public GitHub issue. [1] https://people.redhat.com/~hkario/marvin/ [2] https://github.com/tomato42 [3] https://github.com/aws/s2n-tls/releases/tag/v1.4.16 [4] https://aws.amazon.com/security/vulnerability-reporting Fixed in
0.2.7
References Updated Sep 10, 2026 · Source: OSV.dev |