Akka.Cluster
Clustering support for Akka.NET actors. Used to build highly-available, distributed applications.
Activity
- Latest release
- 3w ago
- Total releases
- 195
- Cadence
- ~10 days
- Last 12 months
- 25
Details
- License
- Apache-2.0
- First release
- Jun 03, 2015
| Version | Released | |
|---|---|---|
1.6.0-beta3
pre
|
1.6.0-beta3
pre
Dependencies (2)
|
|
1.6.0-beta2
pre
|
1.6.0-beta2
pre
Dependencies (2)
|
|
1.5.73
patch
|
1.5.73
patch
Dependencies (2)
|
|
1.5.72
patch
|
1.5.72
patch
Dependencies (2)
|
|
1.6.0-beta1
pre
|
1.6.0-beta1
pre
Dependencies (2)
|
|
1.5.71
patch
|
1.5.71
patch
Dependencies (2)
|
|
1.5.70
patch
|
1.5.70
patch
Dependencies (2)
|
|
1.5.70-beta2
pre
|
1.5.70-beta2
pre
Dependencies (2)
|
|
1.5.70-beta1
pre
|
1.5.70-beta1
pre
Dependencies (2)
|
|
1.5.69
patch
|
1.5.69
patch
Dependencies (2)
|
|
1.5.68
patch
|
1.5.68
patch
Dependencies (2)
|
|
1.5.67
patch
|
1.5.67
patch
Dependencies (2)
|
|
1.5.66
patch
|
1.5.66
patch
Dependencies (2)
|
|
1.5.65
patch
|
1.5.65
patch
Dependencies (2)
|
|
1.5.64
patch
|
1.5.64
patch
Dependencies (2)
|
|
1.5.63
patch
|
1.5.63
patch
Dependencies (2)
|
|
1.5.62
patch
|
1.5.62
patch
Dependencies (2)
|
|
1.5.61
patch
|
1.5.61
patch
Dependencies (2)
|
|
1.5.60
patch
|
1.5.60
patch
Dependencies (2)
|
|
1.5.59
patch
|
1.5.59
patch
Dependencies (2)
|
|
1.5.58
patch
|
1.5.58
patch
Dependencies (2)
|
|
1.5.57
patch
|
1.5.57
patch
Dependencies (2)
|
|
1.5.57-beta2
pre
|
1.5.57-beta2
pre
Dependencies (2)
|
|
1.5.57-beta1
pre
|
1.5.57-beta1
pre
Dependencies (2)
|
|
1.5.56
patch
|
1.5.56
patch
Dependencies (2)
|
|
1.5.55
patch
|
1.5.55
patch
Dependencies (2)
|
|
1.5.54
patch
|
1.5.54
patch
Dependencies (2)
|
|
1.5.53
patch
|
1.5.53
patch
Dependencies (2)
|
|
1.5.52
patch
|
1.5.52
patch
Dependencies (2)
|
|
1.5.51
patch
1 CVE
CVE-2025-61778
GHSA-jhpv-4q4f-43g5
Oct 07, 2025
Akka.Remote TLS did not properly implement certificate-based authentication
Critical
Network
Low
None
None
ImpactThis is a critical network security vulnerability for Akka.Remote users who have SSL / TLS enabled on their Akka.Remote connections and were expecting certificate-based authentication to be enforced on all peers attempting to join the network. In all versions of Akka.Remote from v1.2.0 to v1.5.51, TLS could be enabled via our The issue here is that for certificate-based authentication to work properly, ensuring that all members of the Akka.Remote network are secured with the same private key, Akka.Remote needed to implement mutual TLS. This was not the case before Akka.NET v1.5.52. If you are running Akka.NET inside a private network you fully control or you were never using TLS in the first place, then this bug has no impact on you. However: if you are using TLS to secure your network YOU MUST upgrade to Akka.NET V1.5.52 or later. Patcheshttps://github.com/akkadotnet/akka.net/pull/7847 - forces "fail fast" semantics if TLS is enabled but the private key is missing or invalid. Previous versions would only check that once connection attempts occurred. https://github.com/akkadotnet/akka.net/pull/7851 - critical fix: enforces mutual TLS (mTLS) by default, so both parties must be keyed using the same certificate. This fulfills the original security These updates have been shipped into Akka.NET v1.5.52: https://github.com/akkadotnet/akka.net/releases/tag/1.5.52 WorkaroundsIf your application isn't exposed publicly, then CVE-2025-61778 has no practical impact on your application. That being said: upgrading to Akka.NET v1.5.52 or later is a good idea. ReferencesPlease view our latest network security documentation here: https://getakka.net/articles/remoting/security.html Affected versions
1.2.0
1.2.1
1.2.2
1.2.3
1.3.0
1.3.1
1.3.10
1.3.11
1.3.12
1.3.13
1.3.14
1.3.15
+ 141 more Show less
1.3.16
1.3.17
1.3.18
1.3.19
1.3.2
1.3.3
1.3.4
1.3.5
1.3.6
1.3.7
1.3.8
1.3.9
1.4.0
1.4.0-beta1
1.4.0-beta2
1.4.0-beta3
1.4.0-beta4
1.4.1
1.4.1-rc1
1.4.1-rc2
1.4.1-rc3
1.4.10
1.4.11
1.4.12
1.4.13
1.4.14
1.4.15
1.4.16
1.4.17
1.4.18
1.4.19
1.4.2
1.4.20
1.4.21
1.4.21-beta1
1.4.22
1.4.23
1.4.24
1.4.25
1.4.26
1.4.27
1.4.28
1.4.29
1.4.3
1.4.30
1.4.31
1.4.32
1.4.33
1.4.34
1.4.35
1.4.36
1.4.37
1.4.38
1.4.39
1.4.4
1.4.40
1.4.41
1.4.42
1.4.43
1.4.44
1.4.45
1.4.46
1.4.47
1.4.48
1.4.49
1.4.49-beta1
1.4.5
1.4.50
1.4.51
1.4.6
1.4.7
1.4.8
1.4.9
1.5.0
1.5.0-alpha1
1.5.0-alpha2
1.5.0-alpha3
1.5.0-alpha4
1.5.0-beta1
1.5.0-beta2
1.5.0-beta3
1.5.0-beta4
1.5.0-beta5
1.5.0-beta6
1.5.1
1.5.10
1.5.11
1.5.12
1.5.13
1.5.13-beta1
1.5.14
1.5.15
1.5.16
1.5.17
1.5.17.1
1.5.18
1.5.19
1.5.2
1.5.20
1.5.21
1.5.22
1.5.23
1.5.24
1.5.25
1.5.26
1.5.27
1.5.27-beta1
1.5.27-beta2
1.5.27.1
1.5.28
1.5.28-beta1
1.5.29
1.5.3
1.5.30
1.5.31
1.5.32
1.5.33
1.5.34
1.5.35
1.5.36
1.5.37
1.5.38
1.5.39
1.5.4
1.5.40
1.5.41
1.5.42
1.5.43
1.5.44
1.5.45
1.5.46
1.5.47
1.5.48
1.5.49
1.5.5
1.5.50
1.5.51
1.5.6
1.5.7
1.5.8
1.5.9
Fixed in
1.5.52
References
Updated Oct 07, 2025 · Source: OSV.dev |
1.5.51
patch
Dependencies (2)
|
|
1.5.50
patch
1 CVE
CVE-2025-61778
GHSA-jhpv-4q4f-43g5
Oct 07, 2025
Akka.Remote TLS did not properly implement certificate-based authentication
Critical
Network
Low
None
None
ImpactThis is a critical network security vulnerability for Akka.Remote users who have SSL / TLS enabled on their Akka.Remote connections and were expecting certificate-based authentication to be enforced on all peers attempting to join the network. In all versions of Akka.Remote from v1.2.0 to v1.5.51, TLS could be enabled via our The issue here is that for certificate-based authentication to work properly, ensuring that all members of the Akka.Remote network are secured with the same private key, Akka.Remote needed to implement mutual TLS. This was not the case before Akka.NET v1.5.52. If you are running Akka.NET inside a private network you fully control or you were never using TLS in the first place, then this bug has no impact on you. However: if you are using TLS to secure your network YOU MUST upgrade to Akka.NET V1.5.52 or later. Patcheshttps://github.com/akkadotnet/akka.net/pull/7847 - forces "fail fast" semantics if TLS is enabled but the private key is missing or invalid. Previous versions would only check that once connection attempts occurred. https://github.com/akkadotnet/akka.net/pull/7851 - critical fix: enforces mutual TLS (mTLS) by default, so both parties must be keyed using the same certificate. This fulfills the original security These updates have been shipped into Akka.NET v1.5.52: https://github.com/akkadotnet/akka.net/releases/tag/1.5.52 WorkaroundsIf your application isn't exposed publicly, then CVE-2025-61778 has no practical impact on your application. That being said: upgrading to Akka.NET v1.5.52 or later is a good idea. ReferencesPlease view our latest network security documentation here: https://getakka.net/articles/remoting/security.html Affected versions
1.2.0
1.2.1
1.2.2
1.2.3
1.3.0
1.3.1
1.3.10
1.3.11
1.3.12
1.3.13
1.3.14
1.3.15
+ 141 more Show less
1.3.16
1.3.17
1.3.18
1.3.19
1.3.2
1.3.3
1.3.4
1.3.5
1.3.6
1.3.7
1.3.8
1.3.9
1.4.0
1.4.0-beta1
1.4.0-beta2
1.4.0-beta3
1.4.0-beta4
1.4.1
1.4.1-rc1
1.4.1-rc2
1.4.1-rc3
1.4.10
1.4.11
1.4.12
1.4.13
1.4.14
1.4.15
1.4.16
1.4.17
1.4.18
1.4.19
1.4.2
1.4.20
1.4.21
1.4.21-beta1
1.4.22
1.4.23
1.4.24
1.4.25
1.4.26
1.4.27
1.4.28
1.4.29
1.4.3
1.4.30
1.4.31
1.4.32
1.4.33
1.4.34
1.4.35
1.4.36
1.4.37
1.4.38
1.4.39
1.4.4
1.4.40
1.4.41
1.4.42
1.4.43
1.4.44
1.4.45
1.4.46
1.4.47
1.4.48
1.4.49
1.4.49-beta1
1.4.5
1.4.50
1.4.51
1.4.6
1.4.7
1.4.8
1.4.9
1.5.0
1.5.0-alpha1
1.5.0-alpha2
1.5.0-alpha3
1.5.0-alpha4
1.5.0-beta1
1.5.0-beta2
1.5.0-beta3
1.5.0-beta4
1.5.0-beta5
1.5.0-beta6
1.5.1
1.5.10
1.5.11
1.5.12
1.5.13
1.5.13-beta1
1.5.14
1.5.15
1.5.16
1.5.17
1.5.17.1
1.5.18
1.5.19
1.5.2
1.5.20
1.5.21
1.5.22
1.5.23
1.5.24
1.5.25
1.5.26
1.5.27
1.5.27-beta1
1.5.27-beta2
1.5.27.1
1.5.28
1.5.28-beta1
1.5.29
1.5.3
1.5.30
1.5.31
1.5.32
1.5.33
1.5.34
1.5.35
1.5.36
1.5.37
1.5.38
1.5.39
1.5.4
1.5.40
1.5.41
1.5.42
1.5.43
1.5.44
1.5.45
1.5.46
1.5.47
1.5.48
1.5.49
1.5.5
1.5.50
1.5.51
1.5.6
1.5.7
1.5.8
1.5.9
Fixed in
1.5.52
References
Updated Oct 07, 2025 · Source: OSV.dev |
1.5.50
patch
Dependencies (2)
|
|
1.5.49
patch
1 CVE
CVE-2025-61778
GHSA-jhpv-4q4f-43g5
Oct 07, 2025
Akka.Remote TLS did not properly implement certificate-based authentication
Critical
Network
Low
None
None
ImpactThis is a critical network security vulnerability for Akka.Remote users who have SSL / TLS enabled on their Akka.Remote connections and were expecting certificate-based authentication to be enforced on all peers attempting to join the network. In all versions of Akka.Remote from v1.2.0 to v1.5.51, TLS could be enabled via our The issue here is that for certificate-based authentication to work properly, ensuring that all members of the Akka.Remote network are secured with the same private key, Akka.Remote needed to implement mutual TLS. This was not the case before Akka.NET v1.5.52. If you are running Akka.NET inside a private network you fully control or you were never using TLS in the first place, then this bug has no impact on you. However: if you are using TLS to secure your network YOU MUST upgrade to Akka.NET V1.5.52 or later. Patcheshttps://github.com/akkadotnet/akka.net/pull/7847 - forces "fail fast" semantics if TLS is enabled but the private key is missing or invalid. Previous versions would only check that once connection attempts occurred. https://github.com/akkadotnet/akka.net/pull/7851 - critical fix: enforces mutual TLS (mTLS) by default, so both parties must be keyed using the same certificate. This fulfills the original security These updates have been shipped into Akka.NET v1.5.52: https://github.com/akkadotnet/akka.net/releases/tag/1.5.52 WorkaroundsIf your application isn't exposed publicly, then CVE-2025-61778 has no practical impact on your application. That being said: upgrading to Akka.NET v1.5.52 or later is a good idea. ReferencesPlease view our latest network security documentation here: https://getakka.net/articles/remoting/security.html Affected versions
1.2.0
1.2.1
1.2.2
1.2.3
1.3.0
1.3.1
1.3.10
1.3.11
1.3.12
1.3.13
1.3.14
1.3.15
+ 141 more Show less
1.3.16
1.3.17
1.3.18
1.3.19
1.3.2
1.3.3
1.3.4
1.3.5
1.3.6
1.3.7
1.3.8
1.3.9
1.4.0
1.4.0-beta1
1.4.0-beta2
1.4.0-beta3
1.4.0-beta4
1.4.1
1.4.1-rc1
1.4.1-rc2
1.4.1-rc3
1.4.10
1.4.11
1.4.12
1.4.13
1.4.14
1.4.15
1.4.16
1.4.17
1.4.18
1.4.19
1.4.2
1.4.20
1.4.21
1.4.21-beta1
1.4.22
1.4.23
1.4.24
1.4.25
1.4.26
1.4.27
1.4.28
1.4.29
1.4.3
1.4.30
1.4.31
1.4.32
1.4.33
1.4.34
1.4.35
1.4.36
1.4.37
1.4.38
1.4.39
1.4.4
1.4.40
1.4.41
1.4.42
1.4.43
1.4.44
1.4.45
1.4.46
1.4.47
1.4.48
1.4.49
1.4.49-beta1
1.4.5
1.4.50
1.4.51
1.4.6
1.4.7
1.4.8
1.4.9
1.5.0
1.5.0-alpha1
1.5.0-alpha2
1.5.0-alpha3
1.5.0-alpha4
1.5.0-beta1
1.5.0-beta2
1.5.0-beta3
1.5.0-beta4
1.5.0-beta5
1.5.0-beta6
1.5.1
1.5.10
1.5.11
1.5.12
1.5.13
1.5.13-beta1
1.5.14
1.5.15
1.5.16
1.5.17
1.5.17.1
1.5.18
1.5.19
1.5.2
1.5.20
1.5.21
1.5.22
1.5.23
1.5.24
1.5.25
1.5.26
1.5.27
1.5.27-beta1
1.5.27-beta2
1.5.27.1
1.5.28
1.5.28-beta1
1.5.29
1.5.3
1.5.30
1.5.31
1.5.32
1.5.33
1.5.34
1.5.35
1.5.36
1.5.37
1.5.38
1.5.39
1.5.4
1.5.40
1.5.41
1.5.42
1.5.43
1.5.44
1.5.45
1.5.46
1.5.47
1.5.48
1.5.49
1.5.5
1.5.50
1.5.51
1.5.6
1.5.7
1.5.8
1.5.9
Fixed in
1.5.52
References
Updated Oct 07, 2025 · Source: OSV.dev |
1.5.49
patch
Dependencies (2)
|
|
1.5.48
patch
1 CVE
CVE-2025-61778
GHSA-jhpv-4q4f-43g5
Oct 07, 2025
Akka.Remote TLS did not properly implement certificate-based authentication
Critical
Network
Low
None
None
ImpactThis is a critical network security vulnerability for Akka.Remote users who have SSL / TLS enabled on their Akka.Remote connections and were expecting certificate-based authentication to be enforced on all peers attempting to join the network. In all versions of Akka.Remote from v1.2.0 to v1.5.51, TLS could be enabled via our The issue here is that for certificate-based authentication to work properly, ensuring that all members of the Akka.Remote network are secured with the same private key, Akka.Remote needed to implement mutual TLS. This was not the case before Akka.NET v1.5.52. If you are running Akka.NET inside a private network you fully control or you were never using TLS in the first place, then this bug has no impact on you. However: if you are using TLS to secure your network YOU MUST upgrade to Akka.NET V1.5.52 or later. Patcheshttps://github.com/akkadotnet/akka.net/pull/7847 - forces "fail fast" semantics if TLS is enabled but the private key is missing or invalid. Previous versions would only check that once connection attempts occurred. https://github.com/akkadotnet/akka.net/pull/7851 - critical fix: enforces mutual TLS (mTLS) by default, so both parties must be keyed using the same certificate. This fulfills the original security These updates have been shipped into Akka.NET v1.5.52: https://github.com/akkadotnet/akka.net/releases/tag/1.5.52 WorkaroundsIf your application isn't exposed publicly, then CVE-2025-61778 has no practical impact on your application. That being said: upgrading to Akka.NET v1.5.52 or later is a good idea. ReferencesPlease view our latest network security documentation here: https://getakka.net/articles/remoting/security.html Affected versions
1.2.0
1.2.1
1.2.2
1.2.3
1.3.0
1.3.1
1.3.10
1.3.11
1.3.12
1.3.13
1.3.14
1.3.15
+ 141 more Show less
1.3.16
1.3.17
1.3.18
1.3.19
1.3.2
1.3.3
1.3.4
1.3.5
1.3.6
1.3.7
1.3.8
1.3.9
1.4.0
1.4.0-beta1
1.4.0-beta2
1.4.0-beta3
1.4.0-beta4
1.4.1
1.4.1-rc1
1.4.1-rc2
1.4.1-rc3
1.4.10
1.4.11
1.4.12
1.4.13
1.4.14
1.4.15
1.4.16
1.4.17
1.4.18
1.4.19
1.4.2
1.4.20
1.4.21
1.4.21-beta1
1.4.22
1.4.23
1.4.24
1.4.25
1.4.26
1.4.27
1.4.28
1.4.29
1.4.3
1.4.30
1.4.31
1.4.32
1.4.33
1.4.34
1.4.35
1.4.36
1.4.37
1.4.38
1.4.39
1.4.4
1.4.40
1.4.41
1.4.42
1.4.43
1.4.44
1.4.45
1.4.46
1.4.47
1.4.48
1.4.49
1.4.49-beta1
1.4.5
1.4.50
1.4.51
1.4.6
1.4.7
1.4.8
1.4.9
1.5.0
1.5.0-alpha1
1.5.0-alpha2
1.5.0-alpha3
1.5.0-alpha4
1.5.0-beta1
1.5.0-beta2
1.5.0-beta3
1.5.0-beta4
1.5.0-beta5
1.5.0-beta6
1.5.1
1.5.10
1.5.11
1.5.12
1.5.13
1.5.13-beta1
1.5.14
1.5.15
1.5.16
1.5.17
1.5.17.1
1.5.18
1.5.19
1.5.2
1.5.20
1.5.21
1.5.22
1.5.23
1.5.24
1.5.25
1.5.26
1.5.27
1.5.27-beta1
1.5.27-beta2
1.5.27.1
1.5.28
1.5.28-beta1
1.5.29
1.5.3
1.5.30
1.5.31
1.5.32
1.5.33
1.5.34
1.5.35
1.5.36
1.5.37
1.5.38
1.5.39
1.5.4
1.5.40
1.5.41
1.5.42
1.5.43
1.5.44
1.5.45
1.5.46
1.5.47
1.5.48
1.5.49
1.5.5
1.5.50
1.5.51
1.5.6
1.5.7
1.5.8
1.5.9
Fixed in
1.5.52
References
Updated Oct 07, 2025 · Source: OSV.dev |
1.5.48
patch
Dependencies (2)
|
|
1.5.47
patch
1 CVE
CVE-2025-61778
GHSA-jhpv-4q4f-43g5
Oct 07, 2025
Akka.Remote TLS did not properly implement certificate-based authentication
Critical
Network
Low
None
None
ImpactThis is a critical network security vulnerability for Akka.Remote users who have SSL / TLS enabled on their Akka.Remote connections and were expecting certificate-based authentication to be enforced on all peers attempting to join the network. In all versions of Akka.Remote from v1.2.0 to v1.5.51, TLS could be enabled via our The issue here is that for certificate-based authentication to work properly, ensuring that all members of the Akka.Remote network are secured with the same private key, Akka.Remote needed to implement mutual TLS. This was not the case before Akka.NET v1.5.52. If you are running Akka.NET inside a private network you fully control or you were never using TLS in the first place, then this bug has no impact on you. However: if you are using TLS to secure your network YOU MUST upgrade to Akka.NET V1.5.52 or later. Patcheshttps://github.com/akkadotnet/akka.net/pull/7847 - forces "fail fast" semantics if TLS is enabled but the private key is missing or invalid. Previous versions would only check that once connection attempts occurred. https://github.com/akkadotnet/akka.net/pull/7851 - critical fix: enforces mutual TLS (mTLS) by default, so both parties must be keyed using the same certificate. This fulfills the original security These updates have been shipped into Akka.NET v1.5.52: https://github.com/akkadotnet/akka.net/releases/tag/1.5.52 WorkaroundsIf your application isn't exposed publicly, then CVE-2025-61778 has no practical impact on your application. That being said: upgrading to Akka.NET v1.5.52 or later is a good idea. ReferencesPlease view our latest network security documentation here: https://getakka.net/articles/remoting/security.html Affected versions
1.2.0
1.2.1
1.2.2
1.2.3
1.3.0
1.3.1
1.3.10
1.3.11
1.3.12
1.3.13
1.3.14
1.3.15
+ 141 more Show less
1.3.16
1.3.17
1.3.18
1.3.19
1.3.2
1.3.3
1.3.4
1.3.5
1.3.6
1.3.7
1.3.8
1.3.9
1.4.0
1.4.0-beta1
1.4.0-beta2
1.4.0-beta3
1.4.0-beta4
1.4.1
1.4.1-rc1
1.4.1-rc2
1.4.1-rc3
1.4.10
1.4.11
1.4.12
1.4.13
1.4.14
1.4.15
1.4.16
1.4.17
1.4.18
1.4.19
1.4.2
1.4.20
1.4.21
1.4.21-beta1
1.4.22
1.4.23
1.4.24
1.4.25
1.4.26
1.4.27
1.4.28
1.4.29
1.4.3
1.4.30
1.4.31
1.4.32
1.4.33
1.4.34
1.4.35
1.4.36
1.4.37
1.4.38
1.4.39
1.4.4
1.4.40
1.4.41
1.4.42
1.4.43
1.4.44
1.4.45
1.4.46
1.4.47
1.4.48
1.4.49
1.4.49-beta1
1.4.5
1.4.50
1.4.51
1.4.6
1.4.7
1.4.8
1.4.9
1.5.0
1.5.0-alpha1
1.5.0-alpha2
1.5.0-alpha3
1.5.0-alpha4
1.5.0-beta1
1.5.0-beta2
1.5.0-beta3
1.5.0-beta4
1.5.0-beta5
1.5.0-beta6
1.5.1
1.5.10
1.5.11
1.5.12
1.5.13
1.5.13-beta1
1.5.14
1.5.15
1.5.16
1.5.17
1.5.17.1
1.5.18
1.5.19
1.5.2
1.5.20
1.5.21
1.5.22
1.5.23
1.5.24
1.5.25
1.5.26
1.5.27
1.5.27-beta1
1.5.27-beta2
1.5.27.1
1.5.28
1.5.28-beta1
1.5.29
1.5.3
1.5.30
1.5.31
1.5.32
1.5.33
1.5.34
1.5.35
1.5.36
1.5.37
1.5.38
1.5.39
1.5.4
1.5.40
1.5.41
1.5.42
1.5.43
1.5.44
1.5.45
1.5.46
1.5.47
1.5.48
1.5.49
1.5.5
1.5.50
1.5.51
1.5.6
1.5.7
1.5.8
1.5.9
Fixed in
1.5.52
References
Updated Oct 07, 2025 · Source: OSV.dev |
1.5.47
patch
Dependencies (2)
|
|
1.5.46
patch
1 CVE
CVE-2025-61778
GHSA-jhpv-4q4f-43g5
Oct 07, 2025
Akka.Remote TLS did not properly implement certificate-based authentication
Critical
Network
Low
None
None
ImpactThis is a critical network security vulnerability for Akka.Remote users who have SSL / TLS enabled on their Akka.Remote connections and were expecting certificate-based authentication to be enforced on all peers attempting to join the network. In all versions of Akka.Remote from v1.2.0 to v1.5.51, TLS could be enabled via our The issue here is that for certificate-based authentication to work properly, ensuring that all members of the Akka.Remote network are secured with the same private key, Akka.Remote needed to implement mutual TLS. This was not the case before Akka.NET v1.5.52. If you are running Akka.NET inside a private network you fully control or you were never using TLS in the first place, then this bug has no impact on you. However: if you are using TLS to secure your network YOU MUST upgrade to Akka.NET V1.5.52 or later. Patcheshttps://github.com/akkadotnet/akka.net/pull/7847 - forces "fail fast" semantics if TLS is enabled but the private key is missing or invalid. Previous versions would only check that once connection attempts occurred. https://github.com/akkadotnet/akka.net/pull/7851 - critical fix: enforces mutual TLS (mTLS) by default, so both parties must be keyed using the same certificate. This fulfills the original security These updates have been shipped into Akka.NET v1.5.52: https://github.com/akkadotnet/akka.net/releases/tag/1.5.52 WorkaroundsIf your application isn't exposed publicly, then CVE-2025-61778 has no practical impact on your application. That being said: upgrading to Akka.NET v1.5.52 or later is a good idea. ReferencesPlease view our latest network security documentation here: https://getakka.net/articles/remoting/security.html Affected versions
1.2.0
1.2.1
1.2.2
1.2.3
1.3.0
1.3.1
1.3.10
1.3.11
1.3.12
1.3.13
1.3.14
1.3.15
+ 141 more Show less
1.3.16
1.3.17
1.3.18
1.3.19
1.3.2
1.3.3
1.3.4
1.3.5
1.3.6
1.3.7
1.3.8
1.3.9
1.4.0
1.4.0-beta1
1.4.0-beta2
1.4.0-beta3
1.4.0-beta4
1.4.1
1.4.1-rc1
1.4.1-rc2
1.4.1-rc3
1.4.10
1.4.11
1.4.12
1.4.13
1.4.14
1.4.15
1.4.16
1.4.17
1.4.18
1.4.19
1.4.2
1.4.20
1.4.21
1.4.21-beta1
1.4.22
1.4.23
1.4.24
1.4.25
1.4.26
1.4.27
1.4.28
1.4.29
1.4.3
1.4.30
1.4.31
1.4.32
1.4.33
1.4.34
1.4.35
1.4.36
1.4.37
1.4.38
1.4.39
1.4.4
1.4.40
1.4.41
1.4.42
1.4.43
1.4.44
1.4.45
1.4.46
1.4.47
1.4.48
1.4.49
1.4.49-beta1
1.4.5
1.4.50
1.4.51
1.4.6
1.4.7
1.4.8
1.4.9
1.5.0
1.5.0-alpha1
1.5.0-alpha2
1.5.0-alpha3
1.5.0-alpha4
1.5.0-beta1
1.5.0-beta2
1.5.0-beta3
1.5.0-beta4
1.5.0-beta5
1.5.0-beta6
1.5.1
1.5.10
1.5.11
1.5.12
1.5.13
1.5.13-beta1
1.5.14
1.5.15
1.5.16
1.5.17
1.5.17.1
1.5.18
1.5.19
1.5.2
1.5.20
1.5.21
1.5.22
1.5.23
1.5.24
1.5.25
1.5.26
1.5.27
1.5.27-beta1
1.5.27-beta2
1.5.27.1
1.5.28
1.5.28-beta1
1.5.29
1.5.3
1.5.30
1.5.31
1.5.32
1.5.33
1.5.34
1.5.35
1.5.36
1.5.37
1.5.38
1.5.39
1.5.4
1.5.40
1.5.41
1.5.42
1.5.43
1.5.44
1.5.45
1.5.46
1.5.47
1.5.48
1.5.49
1.5.5
1.5.50
1.5.51
1.5.6
1.5.7
1.5.8
1.5.9
Fixed in
1.5.52
References
Updated Oct 07, 2025 · Source: OSV.dev |
1.5.46
patch
Dependencies (2)
|
|
1.5.45
patch
1 CVE
CVE-2025-61778
GHSA-jhpv-4q4f-43g5
Oct 07, 2025
Akka.Remote TLS did not properly implement certificate-based authentication
Critical
Network
Low
None
None
ImpactThis is a critical network security vulnerability for Akka.Remote users who have SSL / TLS enabled on their Akka.Remote connections and were expecting certificate-based authentication to be enforced on all peers attempting to join the network. In all versions of Akka.Remote from v1.2.0 to v1.5.51, TLS could be enabled via our The issue here is that for certificate-based authentication to work properly, ensuring that all members of the Akka.Remote network are secured with the same private key, Akka.Remote needed to implement mutual TLS. This was not the case before Akka.NET v1.5.52. If you are running Akka.NET inside a private network you fully control or you were never using TLS in the first place, then this bug has no impact on you. However: if you are using TLS to secure your network YOU MUST upgrade to Akka.NET V1.5.52 or later. Patcheshttps://github.com/akkadotnet/akka.net/pull/7847 - forces "fail fast" semantics if TLS is enabled but the private key is missing or invalid. Previous versions would only check that once connection attempts occurred. https://github.com/akkadotnet/akka.net/pull/7851 - critical fix: enforces mutual TLS (mTLS) by default, so both parties must be keyed using the same certificate. This fulfills the original security These updates have been shipped into Akka.NET v1.5.52: https://github.com/akkadotnet/akka.net/releases/tag/1.5.52 WorkaroundsIf your application isn't exposed publicly, then CVE-2025-61778 has no practical impact on your application. That being said: upgrading to Akka.NET v1.5.52 or later is a good idea. ReferencesPlease view our latest network security documentation here: https://getakka.net/articles/remoting/security.html Affected versions
1.2.0
1.2.1
1.2.2
1.2.3
1.3.0
1.3.1
1.3.10
1.3.11
1.3.12
1.3.13
1.3.14
1.3.15
+ 141 more Show less
1.3.16
1.3.17
1.3.18
1.3.19
1.3.2
1.3.3
1.3.4
1.3.5
1.3.6
1.3.7
1.3.8
1.3.9
1.4.0
1.4.0-beta1
1.4.0-beta2
1.4.0-beta3
1.4.0-beta4
1.4.1
1.4.1-rc1
1.4.1-rc2
1.4.1-rc3
1.4.10
1.4.11
1.4.12
1.4.13
1.4.14
1.4.15
1.4.16
1.4.17
1.4.18
1.4.19
1.4.2
1.4.20
1.4.21
1.4.21-beta1
1.4.22
1.4.23
1.4.24
1.4.25
1.4.26
1.4.27
1.4.28
1.4.29
1.4.3
1.4.30
1.4.31
1.4.32
1.4.33
1.4.34
1.4.35
1.4.36
1.4.37
1.4.38
1.4.39
1.4.4
1.4.40
1.4.41
1.4.42
1.4.43
1.4.44
1.4.45
1.4.46
1.4.47
1.4.48
1.4.49
1.4.49-beta1
1.4.5
1.4.50
1.4.51
1.4.6
1.4.7
1.4.8
1.4.9
1.5.0
1.5.0-alpha1
1.5.0-alpha2
1.5.0-alpha3
1.5.0-alpha4
1.5.0-beta1
1.5.0-beta2
1.5.0-beta3
1.5.0-beta4
1.5.0-beta5
1.5.0-beta6
1.5.1
1.5.10
1.5.11
1.5.12
1.5.13
1.5.13-beta1
1.5.14
1.5.15
1.5.16
1.5.17
1.5.17.1
1.5.18
1.5.19
1.5.2
1.5.20
1.5.21
1.5.22
1.5.23
1.5.24
1.5.25
1.5.26
1.5.27
1.5.27-beta1
1.5.27-beta2
1.5.27.1
1.5.28
1.5.28-beta1
1.5.29
1.5.3
1.5.30
1.5.31
1.5.32
1.5.33
1.5.34
1.5.35
1.5.36
1.5.37
1.5.38
1.5.39
1.5.4
1.5.40
1.5.41
1.5.42
1.5.43
1.5.44
1.5.45
1.5.46
1.5.47
1.5.48
1.5.49
1.5.5
1.5.50
1.5.51
1.5.6
1.5.7
1.5.8
1.5.9
Fixed in
1.5.52
References
Updated Oct 07, 2025 · Source: OSV.dev |
1.5.45
patch
Dependencies (2)
|
|
1.5.44
patch
1 CVE
CVE-2025-61778
GHSA-jhpv-4q4f-43g5
Oct 07, 2025
Akka.Remote TLS did not properly implement certificate-based authentication
Critical
Network
Low
None
None
ImpactThis is a critical network security vulnerability for Akka.Remote users who have SSL / TLS enabled on their Akka.Remote connections and were expecting certificate-based authentication to be enforced on all peers attempting to join the network. In all versions of Akka.Remote from v1.2.0 to v1.5.51, TLS could be enabled via our The issue here is that for certificate-based authentication to work properly, ensuring that all members of the Akka.Remote network are secured with the same private key, Akka.Remote needed to implement mutual TLS. This was not the case before Akka.NET v1.5.52. If you are running Akka.NET inside a private network you fully control or you were never using TLS in the first place, then this bug has no impact on you. However: if you are using TLS to secure your network YOU MUST upgrade to Akka.NET V1.5.52 or later. Patcheshttps://github.com/akkadotnet/akka.net/pull/7847 - forces "fail fast" semantics if TLS is enabled but the private key is missing or invalid. Previous versions would only check that once connection attempts occurred. https://github.com/akkadotnet/akka.net/pull/7851 - critical fix: enforces mutual TLS (mTLS) by default, so both parties must be keyed using the same certificate. This fulfills the original security These updates have been shipped into Akka.NET v1.5.52: https://github.com/akkadotnet/akka.net/releases/tag/1.5.52 WorkaroundsIf your application isn't exposed publicly, then CVE-2025-61778 has no practical impact on your application. That being said: upgrading to Akka.NET v1.5.52 or later is a good idea. ReferencesPlease view our latest network security documentation here: https://getakka.net/articles/remoting/security.html Affected versions
1.2.0
1.2.1
1.2.2
1.2.3
1.3.0
1.3.1
1.3.10
1.3.11
1.3.12
1.3.13
1.3.14
1.3.15
+ 141 more Show less
1.3.16
1.3.17
1.3.18
1.3.19
1.3.2
1.3.3
1.3.4
1.3.5
1.3.6
1.3.7
1.3.8
1.3.9
1.4.0
1.4.0-beta1
1.4.0-beta2
1.4.0-beta3
1.4.0-beta4
1.4.1
1.4.1-rc1
1.4.1-rc2
1.4.1-rc3
1.4.10
1.4.11
1.4.12
1.4.13
1.4.14
1.4.15
1.4.16
1.4.17
1.4.18
1.4.19
1.4.2
1.4.20
1.4.21
1.4.21-beta1
1.4.22
1.4.23
1.4.24
1.4.25
1.4.26
1.4.27
1.4.28
1.4.29
1.4.3
1.4.30
1.4.31
1.4.32
1.4.33
1.4.34
1.4.35
1.4.36
1.4.37
1.4.38
1.4.39
1.4.4
1.4.40
1.4.41
1.4.42
1.4.43
1.4.44
1.4.45
1.4.46
1.4.47
1.4.48
1.4.49
1.4.49-beta1
1.4.5
1.4.50
1.4.51
1.4.6
1.4.7
1.4.8
1.4.9
1.5.0
1.5.0-alpha1
1.5.0-alpha2
1.5.0-alpha3
1.5.0-alpha4
1.5.0-beta1
1.5.0-beta2
1.5.0-beta3
1.5.0-beta4
1.5.0-beta5
1.5.0-beta6
1.5.1
1.5.10
1.5.11
1.5.12
1.5.13
1.5.13-beta1
1.5.14
1.5.15
1.5.16
1.5.17
1.5.17.1
1.5.18
1.5.19
1.5.2
1.5.20
1.5.21
1.5.22
1.5.23
1.5.24
1.5.25
1.5.26
1.5.27
1.5.27-beta1
1.5.27-beta2
1.5.27.1
1.5.28
1.5.28-beta1
1.5.29
1.5.3
1.5.30
1.5.31
1.5.32
1.5.33
1.5.34
1.5.35
1.5.36
1.5.37
1.5.38
1.5.39
1.5.4
1.5.40
1.5.41
1.5.42
1.5.43
1.5.44
1.5.45
1.5.46
1.5.47
1.5.48
1.5.49
1.5.5
1.5.50
1.5.51
1.5.6
1.5.7
1.5.8
1.5.9
Fixed in
1.5.52
References
Updated Oct 07, 2025 · Source: OSV.dev |
1.5.44
patch
Dependencies (2)
|
|
1.5.43
patch
1 CVE
CVE-2025-61778
GHSA-jhpv-4q4f-43g5
Oct 07, 2025
Akka.Remote TLS did not properly implement certificate-based authentication
Critical
Network
Low
None
None
ImpactThis is a critical network security vulnerability for Akka.Remote users who have SSL / TLS enabled on their Akka.Remote connections and were expecting certificate-based authentication to be enforced on all peers attempting to join the network. In all versions of Akka.Remote from v1.2.0 to v1.5.51, TLS could be enabled via our The issue here is that for certificate-based authentication to work properly, ensuring that all members of the Akka.Remote network are secured with the same private key, Akka.Remote needed to implement mutual TLS. This was not the case before Akka.NET v1.5.52. If you are running Akka.NET inside a private network you fully control or you were never using TLS in the first place, then this bug has no impact on you. However: if you are using TLS to secure your network YOU MUST upgrade to Akka.NET V1.5.52 or later. Patcheshttps://github.com/akkadotnet/akka.net/pull/7847 - forces "fail fast" semantics if TLS is enabled but the private key is missing or invalid. Previous versions would only check that once connection attempts occurred. https://github.com/akkadotnet/akka.net/pull/7851 - critical fix: enforces mutual TLS (mTLS) by default, so both parties must be keyed using the same certificate. This fulfills the original security These updates have been shipped into Akka.NET v1.5.52: https://github.com/akkadotnet/akka.net/releases/tag/1.5.52 WorkaroundsIf your application isn't exposed publicly, then CVE-2025-61778 has no practical impact on your application. That being said: upgrading to Akka.NET v1.5.52 or later is a good idea. ReferencesPlease view our latest network security documentation here: https://getakka.net/articles/remoting/security.html Affected versions
1.2.0
1.2.1
1.2.2
1.2.3
1.3.0
1.3.1
1.3.10
1.3.11
1.3.12
1.3.13
1.3.14
1.3.15
+ 141 more Show less
1.3.16
1.3.17
1.3.18
1.3.19
1.3.2
1.3.3
1.3.4
1.3.5
1.3.6
1.3.7
1.3.8
1.3.9
1.4.0
1.4.0-beta1
1.4.0-beta2
1.4.0-beta3
1.4.0-beta4
1.4.1
1.4.1-rc1
1.4.1-rc2
1.4.1-rc3
1.4.10
1.4.11
1.4.12
1.4.13
1.4.14
1.4.15
1.4.16
1.4.17
1.4.18
1.4.19
1.4.2
1.4.20
1.4.21
1.4.21-beta1
1.4.22
1.4.23
1.4.24
1.4.25
1.4.26
1.4.27
1.4.28
1.4.29
1.4.3
1.4.30
1.4.31
1.4.32
1.4.33
1.4.34
1.4.35
1.4.36
1.4.37
1.4.38
1.4.39
1.4.4
1.4.40
1.4.41
1.4.42
1.4.43
1.4.44
1.4.45
1.4.46
1.4.47
1.4.48
1.4.49
1.4.49-beta1
1.4.5
1.4.50
1.4.51
1.4.6
1.4.7
1.4.8
1.4.9
1.5.0
1.5.0-alpha1
1.5.0-alpha2
1.5.0-alpha3
1.5.0-alpha4
1.5.0-beta1
1.5.0-beta2
1.5.0-beta3
1.5.0-beta4
1.5.0-beta5
1.5.0-beta6
1.5.1
1.5.10
1.5.11
1.5.12
1.5.13
1.5.13-beta1
1.5.14
1.5.15
1.5.16
1.5.17
1.5.17.1
1.5.18
1.5.19
1.5.2
1.5.20
1.5.21
1.5.22
1.5.23
1.5.24
1.5.25
1.5.26
1.5.27
1.5.27-beta1
1.5.27-beta2
1.5.27.1
1.5.28
1.5.28-beta1
1.5.29
1.5.3
1.5.30
1.5.31
1.5.32
1.5.33
1.5.34
1.5.35
1.5.36
1.5.37
1.5.38
1.5.39
1.5.4
1.5.40
1.5.41
1.5.42
1.5.43
1.5.44
1.5.45
1.5.46
1.5.47
1.5.48
1.5.49
1.5.5
1.5.50
1.5.51
1.5.6
1.5.7
1.5.8
1.5.9
Fixed in
1.5.52
References
Updated Oct 07, 2025 · Source: OSV.dev |
1.5.43
patch
Dependencies (2)
|
|
1.5.42
patch
1 CVE
CVE-2025-61778
GHSA-jhpv-4q4f-43g5
Oct 07, 2025
Akka.Remote TLS did not properly implement certificate-based authentication
Critical
Network
Low
None
None
ImpactThis is a critical network security vulnerability for Akka.Remote users who have SSL / TLS enabled on their Akka.Remote connections and were expecting certificate-based authentication to be enforced on all peers attempting to join the network. In all versions of Akka.Remote from v1.2.0 to v1.5.51, TLS could be enabled via our The issue here is that for certificate-based authentication to work properly, ensuring that all members of the Akka.Remote network are secured with the same private key, Akka.Remote needed to implement mutual TLS. This was not the case before Akka.NET v1.5.52. If you are running Akka.NET inside a private network you fully control or you were never using TLS in the first place, then this bug has no impact on you. However: if you are using TLS to secure your network YOU MUST upgrade to Akka.NET V1.5.52 or later. Patcheshttps://github.com/akkadotnet/akka.net/pull/7847 - forces "fail fast" semantics if TLS is enabled but the private key is missing or invalid. Previous versions would only check that once connection attempts occurred. https://github.com/akkadotnet/akka.net/pull/7851 - critical fix: enforces mutual TLS (mTLS) by default, so both parties must be keyed using the same certificate. This fulfills the original security These updates have been shipped into Akka.NET v1.5.52: https://github.com/akkadotnet/akka.net/releases/tag/1.5.52 WorkaroundsIf your application isn't exposed publicly, then CVE-2025-61778 has no practical impact on your application. That being said: upgrading to Akka.NET v1.5.52 or later is a good idea. ReferencesPlease view our latest network security documentation here: https://getakka.net/articles/remoting/security.html Affected versions
1.2.0
1.2.1
1.2.2
1.2.3
1.3.0
1.3.1
1.3.10
1.3.11
1.3.12
1.3.13
1.3.14
1.3.15
+ 141 more Show less
1.3.16
1.3.17
1.3.18
1.3.19
1.3.2
1.3.3
1.3.4
1.3.5
1.3.6
1.3.7
1.3.8
1.3.9
1.4.0
1.4.0-beta1
1.4.0-beta2
1.4.0-beta3
1.4.0-beta4
1.4.1
1.4.1-rc1
1.4.1-rc2
1.4.1-rc3
1.4.10
1.4.11
1.4.12
1.4.13
1.4.14
1.4.15
1.4.16
1.4.17
1.4.18
1.4.19
1.4.2
1.4.20
1.4.21
1.4.21-beta1
1.4.22
1.4.23
1.4.24
1.4.25
1.4.26
1.4.27
1.4.28
1.4.29
1.4.3
1.4.30
1.4.31
1.4.32
1.4.33
1.4.34
1.4.35
1.4.36
1.4.37
1.4.38
1.4.39
1.4.4
1.4.40
1.4.41
1.4.42
1.4.43
1.4.44
1.4.45
1.4.46
1.4.47
1.4.48
1.4.49
1.4.49-beta1
1.4.5
1.4.50
1.4.51
1.4.6
1.4.7
1.4.8
1.4.9
1.5.0
1.5.0-alpha1
1.5.0-alpha2
1.5.0-alpha3
1.5.0-alpha4
1.5.0-beta1
1.5.0-beta2
1.5.0-beta3
1.5.0-beta4
1.5.0-beta5
1.5.0-beta6
1.5.1
1.5.10
1.5.11
1.5.12
1.5.13
1.5.13-beta1
1.5.14
1.5.15
1.5.16
1.5.17
1.5.17.1
1.5.18
1.5.19
1.5.2
1.5.20
1.5.21
1.5.22
1.5.23
1.5.24
1.5.25
1.5.26
1.5.27
1.5.27-beta1
1.5.27-beta2
1.5.27.1
1.5.28
1.5.28-beta1
1.5.29
1.5.3
1.5.30
1.5.31
1.5.32
1.5.33
1.5.34
1.5.35
1.5.36
1.5.37
1.5.38
1.5.39
1.5.4
1.5.40
1.5.41
1.5.42
1.5.43
1.5.44
1.5.45
1.5.46
1.5.47
1.5.48
1.5.49
1.5.5
1.5.50
1.5.51
1.5.6
1.5.7
1.5.8
1.5.9
Fixed in
1.5.52
References
Updated Oct 07, 2025 · Source: OSV.dev |
1.5.42
patch
Dependencies (2)
|
|
1.5.41
patch
1 CVE
CVE-2025-61778
GHSA-jhpv-4q4f-43g5
Oct 07, 2025
Akka.Remote TLS did not properly implement certificate-based authentication
Critical
Network
Low
None
None
ImpactThis is a critical network security vulnerability for Akka.Remote users who have SSL / TLS enabled on their Akka.Remote connections and were expecting certificate-based authentication to be enforced on all peers attempting to join the network. In all versions of Akka.Remote from v1.2.0 to v1.5.51, TLS could be enabled via our The issue here is that for certificate-based authentication to work properly, ensuring that all members of the Akka.Remote network are secured with the same private key, Akka.Remote needed to implement mutual TLS. This was not the case before Akka.NET v1.5.52. If you are running Akka.NET inside a private network you fully control or you were never using TLS in the first place, then this bug has no impact on you. However: if you are using TLS to secure your network YOU MUST upgrade to Akka.NET V1.5.52 or later. Patcheshttps://github.com/akkadotnet/akka.net/pull/7847 - forces "fail fast" semantics if TLS is enabled but the private key is missing or invalid. Previous versions would only check that once connection attempts occurred. https://github.com/akkadotnet/akka.net/pull/7851 - critical fix: enforces mutual TLS (mTLS) by default, so both parties must be keyed using the same certificate. This fulfills the original security These updates have been shipped into Akka.NET v1.5.52: https://github.com/akkadotnet/akka.net/releases/tag/1.5.52 WorkaroundsIf your application isn't exposed publicly, then CVE-2025-61778 has no practical impact on your application. That being said: upgrading to Akka.NET v1.5.52 or later is a good idea. ReferencesPlease view our latest network security documentation here: https://getakka.net/articles/remoting/security.html Affected versions
1.2.0
1.2.1
1.2.2
1.2.3
1.3.0
1.3.1
1.3.10
1.3.11
1.3.12
1.3.13
1.3.14
1.3.15
+ 141 more Show less
1.3.16
1.3.17
1.3.18
1.3.19
1.3.2
1.3.3
1.3.4
1.3.5
1.3.6
1.3.7
1.3.8
1.3.9
1.4.0
1.4.0-beta1
1.4.0-beta2
1.4.0-beta3
1.4.0-beta4
1.4.1
1.4.1-rc1
1.4.1-rc2
1.4.1-rc3
1.4.10
1.4.11
1.4.12
1.4.13
1.4.14
1.4.15
1.4.16
1.4.17
1.4.18
1.4.19
1.4.2
1.4.20
1.4.21
1.4.21-beta1
1.4.22
1.4.23
1.4.24
1.4.25
1.4.26
1.4.27
1.4.28
1.4.29
1.4.3
1.4.30
1.4.31
1.4.32
1.4.33
1.4.34
1.4.35
1.4.36
1.4.37
1.4.38
1.4.39
1.4.4
1.4.40
1.4.41
1.4.42
1.4.43
1.4.44
1.4.45
1.4.46
1.4.47
1.4.48
1.4.49
1.4.49-beta1
1.4.5
1.4.50
1.4.51
1.4.6
1.4.7
1.4.8
1.4.9
1.5.0
1.5.0-alpha1
1.5.0-alpha2
1.5.0-alpha3
1.5.0-alpha4
1.5.0-beta1
1.5.0-beta2
1.5.0-beta3
1.5.0-beta4
1.5.0-beta5
1.5.0-beta6
1.5.1
1.5.10
1.5.11
1.5.12
1.5.13
1.5.13-beta1
1.5.14
1.5.15
1.5.16
1.5.17
1.5.17.1
1.5.18
1.5.19
1.5.2
1.5.20
1.5.21
1.5.22
1.5.23
1.5.24
1.5.25
1.5.26
1.5.27
1.5.27-beta1
1.5.27-beta2
1.5.27.1
1.5.28
1.5.28-beta1
1.5.29
1.5.3
1.5.30
1.5.31
1.5.32
1.5.33
1.5.34
1.5.35
1.5.36
1.5.37
1.5.38
1.5.39
1.5.4
1.5.40
1.5.41
1.5.42
1.5.43
1.5.44
1.5.45
1.5.46
1.5.47
1.5.48
1.5.49
1.5.5
1.5.50
1.5.51
1.5.6
1.5.7
1.5.8
1.5.9
Fixed in
1.5.52
References
Updated Oct 07, 2025 · Source: OSV.dev |
1.5.41
patch
Dependencies (2)
|
|
1.5.40
patch
1 CVE
CVE-2025-61778
GHSA-jhpv-4q4f-43g5
Oct 07, 2025
Akka.Remote TLS did not properly implement certificate-based authentication
Critical
Network
Low
None
None
ImpactThis is a critical network security vulnerability for Akka.Remote users who have SSL / TLS enabled on their Akka.Remote connections and were expecting certificate-based authentication to be enforced on all peers attempting to join the network. In all versions of Akka.Remote from v1.2.0 to v1.5.51, TLS could be enabled via our The issue here is that for certificate-based authentication to work properly, ensuring that all members of the Akka.Remote network are secured with the same private key, Akka.Remote needed to implement mutual TLS. This was not the case before Akka.NET v1.5.52. If you are running Akka.NET inside a private network you fully control or you were never using TLS in the first place, then this bug has no impact on you. However: if you are using TLS to secure your network YOU MUST upgrade to Akka.NET V1.5.52 or later. Patcheshttps://github.com/akkadotnet/akka.net/pull/7847 - forces "fail fast" semantics if TLS is enabled but the private key is missing or invalid. Previous versions would only check that once connection attempts occurred. https://github.com/akkadotnet/akka.net/pull/7851 - critical fix: enforces mutual TLS (mTLS) by default, so both parties must be keyed using the same certificate. This fulfills the original security These updates have been shipped into Akka.NET v1.5.52: https://github.com/akkadotnet/akka.net/releases/tag/1.5.52 WorkaroundsIf your application isn't exposed publicly, then CVE-2025-61778 has no practical impact on your application. That being said: upgrading to Akka.NET v1.5.52 or later is a good idea. ReferencesPlease view our latest network security documentation here: https://getakka.net/articles/remoting/security.html Affected versions
1.2.0
1.2.1
1.2.2
1.2.3
1.3.0
1.3.1
1.3.10
1.3.11
1.3.12
1.3.13
1.3.14
1.3.15
+ 141 more Show less
1.3.16
1.3.17
1.3.18
1.3.19
1.3.2
1.3.3
1.3.4
1.3.5
1.3.6
1.3.7
1.3.8
1.3.9
1.4.0
1.4.0-beta1
1.4.0-beta2
1.4.0-beta3
1.4.0-beta4
1.4.1
1.4.1-rc1
1.4.1-rc2
1.4.1-rc3
1.4.10
1.4.11
1.4.12
1.4.13
1.4.14
1.4.15
1.4.16
1.4.17
1.4.18
1.4.19
1.4.2
1.4.20
1.4.21
1.4.21-beta1
1.4.22
1.4.23
1.4.24
1.4.25
1.4.26
1.4.27
1.4.28
1.4.29
1.4.3
1.4.30
1.4.31
1.4.32
1.4.33
1.4.34
1.4.35
1.4.36
1.4.37
1.4.38
1.4.39
1.4.4
1.4.40
1.4.41
1.4.42
1.4.43
1.4.44
1.4.45
1.4.46
1.4.47
1.4.48
1.4.49
1.4.49-beta1
1.4.5
1.4.50
1.4.51
1.4.6
1.4.7
1.4.8
1.4.9
1.5.0
1.5.0-alpha1
1.5.0-alpha2
1.5.0-alpha3
1.5.0-alpha4
1.5.0-beta1
1.5.0-beta2
1.5.0-beta3
1.5.0-beta4
1.5.0-beta5
1.5.0-beta6
1.5.1
1.5.10
1.5.11
1.5.12
1.5.13
1.5.13-beta1
1.5.14
1.5.15
1.5.16
1.5.17
1.5.17.1
1.5.18
1.5.19
1.5.2
1.5.20
1.5.21
1.5.22
1.5.23
1.5.24
1.5.25
1.5.26
1.5.27
1.5.27-beta1
1.5.27-beta2
1.5.27.1
1.5.28
1.5.28-beta1
1.5.29
1.5.3
1.5.30
1.5.31
1.5.32
1.5.33
1.5.34
1.5.35
1.5.36
1.5.37
1.5.38
1.5.39
1.5.4
1.5.40
1.5.41
1.5.42
1.5.43
1.5.44
1.5.45
1.5.46
1.5.47
1.5.48
1.5.49
1.5.5
1.5.50
1.5.51
1.5.6
1.5.7
1.5.8
1.5.9
Fixed in
1.5.52
References
Updated Oct 07, 2025 · Source: OSV.dev |
1.5.40
patch
Dependencies (2)
|
|
1.5.39
patch
1 CVE
CVE-2025-61778
GHSA-jhpv-4q4f-43g5
Oct 07, 2025
Akka.Remote TLS did not properly implement certificate-based authentication
Critical
Network
Low
None
None
ImpactThis is a critical network security vulnerability for Akka.Remote users who have SSL / TLS enabled on their Akka.Remote connections and were expecting certificate-based authentication to be enforced on all peers attempting to join the network. In all versions of Akka.Remote from v1.2.0 to v1.5.51, TLS could be enabled via our The issue here is that for certificate-based authentication to work properly, ensuring that all members of the Akka.Remote network are secured with the same private key, Akka.Remote needed to implement mutual TLS. This was not the case before Akka.NET v1.5.52. If you are running Akka.NET inside a private network you fully control or you were never using TLS in the first place, then this bug has no impact on you. However: if you are using TLS to secure your network YOU MUST upgrade to Akka.NET V1.5.52 or later. Patcheshttps://github.com/akkadotnet/akka.net/pull/7847 - forces "fail fast" semantics if TLS is enabled but the private key is missing or invalid. Previous versions would only check that once connection attempts occurred. https://github.com/akkadotnet/akka.net/pull/7851 - critical fix: enforces mutual TLS (mTLS) by default, so both parties must be keyed using the same certificate. This fulfills the original security These updates have been shipped into Akka.NET v1.5.52: https://github.com/akkadotnet/akka.net/releases/tag/1.5.52 WorkaroundsIf your application isn't exposed publicly, then CVE-2025-61778 has no practical impact on your application. That being said: upgrading to Akka.NET v1.5.52 or later is a good idea. ReferencesPlease view our latest network security documentation here: https://getakka.net/articles/remoting/security.html Affected versions
1.2.0
1.2.1
1.2.2
1.2.3
1.3.0
1.3.1
1.3.10
1.3.11
1.3.12
1.3.13
1.3.14
1.3.15
+ 141 more Show less
1.3.16
1.3.17
1.3.18
1.3.19
1.3.2
1.3.3
1.3.4
1.3.5
1.3.6
1.3.7
1.3.8
1.3.9
1.4.0
1.4.0-beta1
1.4.0-beta2
1.4.0-beta3
1.4.0-beta4
1.4.1
1.4.1-rc1
1.4.1-rc2
1.4.1-rc3
1.4.10
1.4.11
1.4.12
1.4.13
1.4.14
1.4.15
1.4.16
1.4.17
1.4.18
1.4.19
1.4.2
1.4.20
1.4.21
1.4.21-beta1
1.4.22
1.4.23
1.4.24
1.4.25
1.4.26
1.4.27
1.4.28
1.4.29
1.4.3
1.4.30
1.4.31
1.4.32
1.4.33
1.4.34
1.4.35
1.4.36
1.4.37
1.4.38
1.4.39
1.4.4
1.4.40
1.4.41
1.4.42
1.4.43
1.4.44
1.4.45
1.4.46
1.4.47
1.4.48
1.4.49
1.4.49-beta1
1.4.5
1.4.50
1.4.51
1.4.6
1.4.7
1.4.8
1.4.9
1.5.0
1.5.0-alpha1
1.5.0-alpha2
1.5.0-alpha3
1.5.0-alpha4
1.5.0-beta1
1.5.0-beta2
1.5.0-beta3
1.5.0-beta4
1.5.0-beta5
1.5.0-beta6
1.5.1
1.5.10
1.5.11
1.5.12
1.5.13
1.5.13-beta1
1.5.14
1.5.15
1.5.16
1.5.17
1.5.17.1
1.5.18
1.5.19
1.5.2
1.5.20
1.5.21
1.5.22
1.5.23
1.5.24
1.5.25
1.5.26
1.5.27
1.5.27-beta1
1.5.27-beta2
1.5.27.1
1.5.28
1.5.28-beta1
1.5.29
1.5.3
1.5.30
1.5.31
1.5.32
1.5.33
1.5.34
1.5.35
1.5.36
1.5.37
1.5.38
1.5.39
1.5.4
1.5.40
1.5.41
1.5.42
1.5.43
1.5.44
1.5.45
1.5.46
1.5.47
1.5.48
1.5.49
1.5.5
1.5.50
1.5.51
1.5.6
1.5.7
1.5.8
1.5.9
Fixed in
1.5.52
References
Updated Oct 07, 2025 · Source: OSV.dev |
1.5.39
patch
Dependencies (2)
|
|
1.5.38
patch
1 CVE
CVE-2025-61778
GHSA-jhpv-4q4f-43g5
Oct 07, 2025
Akka.Remote TLS did not properly implement certificate-based authentication
Critical
Network
Low
None
None
ImpactThis is a critical network security vulnerability for Akka.Remote users who have SSL / TLS enabled on their Akka.Remote connections and were expecting certificate-based authentication to be enforced on all peers attempting to join the network. In all versions of Akka.Remote from v1.2.0 to v1.5.51, TLS could be enabled via our The issue here is that for certificate-based authentication to work properly, ensuring that all members of the Akka.Remote network are secured with the same private key, Akka.Remote needed to implement mutual TLS. This was not the case before Akka.NET v1.5.52. If you are running Akka.NET inside a private network you fully control or you were never using TLS in the first place, then this bug has no impact on you. However: if you are using TLS to secure your network YOU MUST upgrade to Akka.NET V1.5.52 or later. Patcheshttps://github.com/akkadotnet/akka.net/pull/7847 - forces "fail fast" semantics if TLS is enabled but the private key is missing or invalid. Previous versions would only check that once connection attempts occurred. https://github.com/akkadotnet/akka.net/pull/7851 - critical fix: enforces mutual TLS (mTLS) by default, so both parties must be keyed using the same certificate. This fulfills the original security These updates have been shipped into Akka.NET v1.5.52: https://github.com/akkadotnet/akka.net/releases/tag/1.5.52 WorkaroundsIf your application isn't exposed publicly, then CVE-2025-61778 has no practical impact on your application. That being said: upgrading to Akka.NET v1.5.52 or later is a good idea. ReferencesPlease view our latest network security documentation here: https://getakka.net/articles/remoting/security.html Affected versions
1.2.0
1.2.1
1.2.2
1.2.3
1.3.0
1.3.1
1.3.10
1.3.11
1.3.12
1.3.13
1.3.14
1.3.15
+ 141 more Show less
1.3.16
1.3.17
1.3.18
1.3.19
1.3.2
1.3.3
1.3.4
1.3.5
1.3.6
1.3.7
1.3.8
1.3.9
1.4.0
1.4.0-beta1
1.4.0-beta2
1.4.0-beta3
1.4.0-beta4
1.4.1
1.4.1-rc1
1.4.1-rc2
1.4.1-rc3
1.4.10
1.4.11
1.4.12
1.4.13
1.4.14
1.4.15
1.4.16
1.4.17
1.4.18
1.4.19
1.4.2
1.4.20
1.4.21
1.4.21-beta1
1.4.22
1.4.23
1.4.24
1.4.25
1.4.26
1.4.27
1.4.28
1.4.29
1.4.3
1.4.30
1.4.31
1.4.32
1.4.33
1.4.34
1.4.35
1.4.36
1.4.37
1.4.38
1.4.39
1.4.4
1.4.40
1.4.41
1.4.42
1.4.43
1.4.44
1.4.45
1.4.46
1.4.47
1.4.48
1.4.49
1.4.49-beta1
1.4.5
1.4.50
1.4.51
1.4.6
1.4.7
1.4.8
1.4.9
1.5.0
1.5.0-alpha1
1.5.0-alpha2
1.5.0-alpha3
1.5.0-alpha4
1.5.0-beta1
1.5.0-beta2
1.5.0-beta3
1.5.0-beta4
1.5.0-beta5
1.5.0-beta6
1.5.1
1.5.10
1.5.11
1.5.12
1.5.13
1.5.13-beta1
1.5.14
1.5.15
1.5.16
1.5.17
1.5.17.1
1.5.18
1.5.19
1.5.2
1.5.20
1.5.21
1.5.22
1.5.23
1.5.24
1.5.25
1.5.26
1.5.27
1.5.27-beta1
1.5.27-beta2
1.5.27.1
1.5.28
1.5.28-beta1
1.5.29
1.5.3
1.5.30
1.5.31
1.5.32
1.5.33
1.5.34
1.5.35
1.5.36
1.5.37
1.5.38
1.5.39
1.5.4
1.5.40
1.5.41
1.5.42
1.5.43
1.5.44
1.5.45
1.5.46
1.5.47
1.5.48
1.5.49
1.5.5
1.5.50
1.5.51
1.5.6
1.5.7
1.5.8
1.5.9
Fixed in
1.5.52
References
Updated Oct 07, 2025 · Source: OSV.dev |
1.5.38
patch
Dependencies (2)
|
|
1.5.37
patch
1 CVE
CVE-2025-61778
GHSA-jhpv-4q4f-43g5
Oct 07, 2025
Akka.Remote TLS did not properly implement certificate-based authentication
Critical
Network
Low
None
None
ImpactThis is a critical network security vulnerability for Akka.Remote users who have SSL / TLS enabled on their Akka.Remote connections and were expecting certificate-based authentication to be enforced on all peers attempting to join the network. In all versions of Akka.Remote from v1.2.0 to v1.5.51, TLS could be enabled via our The issue here is that for certificate-based authentication to work properly, ensuring that all members of the Akka.Remote network are secured with the same private key, Akka.Remote needed to implement mutual TLS. This was not the case before Akka.NET v1.5.52. If you are running Akka.NET inside a private network you fully control or you were never using TLS in the first place, then this bug has no impact on you. However: if you are using TLS to secure your network YOU MUST upgrade to Akka.NET V1.5.52 or later. Patcheshttps://github.com/akkadotnet/akka.net/pull/7847 - forces "fail fast" semantics if TLS is enabled but the private key is missing or invalid. Previous versions would only check that once connection attempts occurred. https://github.com/akkadotnet/akka.net/pull/7851 - critical fix: enforces mutual TLS (mTLS) by default, so both parties must be keyed using the same certificate. This fulfills the original security These updates have been shipped into Akka.NET v1.5.52: https://github.com/akkadotnet/akka.net/releases/tag/1.5.52 WorkaroundsIf your application isn't exposed publicly, then CVE-2025-61778 has no practical impact on your application. That being said: upgrading to Akka.NET v1.5.52 or later is a good idea. ReferencesPlease view our latest network security documentation here: https://getakka.net/articles/remoting/security.html Affected versions
1.2.0
1.2.1
1.2.2
1.2.3
1.3.0
1.3.1
1.3.10
1.3.11
1.3.12
1.3.13
1.3.14
1.3.15
+ 141 more Show less
1.3.16
1.3.17
1.3.18
1.3.19
1.3.2
1.3.3
1.3.4
1.3.5
1.3.6
1.3.7
1.3.8
1.3.9
1.4.0
1.4.0-beta1
1.4.0-beta2
1.4.0-beta3
1.4.0-beta4
1.4.1
1.4.1-rc1
1.4.1-rc2
1.4.1-rc3
1.4.10
1.4.11
1.4.12
1.4.13
1.4.14
1.4.15
1.4.16
1.4.17
1.4.18
1.4.19
1.4.2
1.4.20
1.4.21
1.4.21-beta1
1.4.22
1.4.23
1.4.24
1.4.25
1.4.26
1.4.27
1.4.28
1.4.29
1.4.3
1.4.30
1.4.31
1.4.32
1.4.33
1.4.34
1.4.35
1.4.36
1.4.37
1.4.38
1.4.39
1.4.4
1.4.40
1.4.41
1.4.42
1.4.43
1.4.44
1.4.45
1.4.46
1.4.47
1.4.48
1.4.49
1.4.49-beta1
1.4.5
1.4.50
1.4.51
1.4.6
1.4.7
1.4.8
1.4.9
1.5.0
1.5.0-alpha1
1.5.0-alpha2
1.5.0-alpha3
1.5.0-alpha4
1.5.0-beta1
1.5.0-beta2
1.5.0-beta3
1.5.0-beta4
1.5.0-beta5
1.5.0-beta6
1.5.1
1.5.10
1.5.11
1.5.12
1.5.13
1.5.13-beta1
1.5.14
1.5.15
1.5.16
1.5.17
1.5.17.1
1.5.18
1.5.19
1.5.2
1.5.20
1.5.21
1.5.22
1.5.23
1.5.24
1.5.25
1.5.26
1.5.27
1.5.27-beta1
1.5.27-beta2
1.5.27.1
1.5.28
1.5.28-beta1
1.5.29
1.5.3
1.5.30
1.5.31
1.5.32
1.5.33
1.5.34
1.5.35
1.5.36
1.5.37
1.5.38
1.5.39
1.5.4
1.5.40
1.5.41
1.5.42
1.5.43
1.5.44
1.5.45
1.5.46
1.5.47
1.5.48
1.5.49
1.5.5
1.5.50
1.5.51
1.5.6
1.5.7
1.5.8
1.5.9
Fixed in
1.5.52
References
Updated Oct 07, 2025 · Source: OSV.dev |
1.5.37
patch
Dependencies (2)
|
|
1.5.36
patch
1 CVE
CVE-2025-61778
GHSA-jhpv-4q4f-43g5
Oct 07, 2025
Akka.Remote TLS did not properly implement certificate-based authentication
Critical
Network
Low
None
None
ImpactThis is a critical network security vulnerability for Akka.Remote users who have SSL / TLS enabled on their Akka.Remote connections and were expecting certificate-based authentication to be enforced on all peers attempting to join the network. In all versions of Akka.Remote from v1.2.0 to v1.5.51, TLS could be enabled via our The issue here is that for certificate-based authentication to work properly, ensuring that all members of the Akka.Remote network are secured with the same private key, Akka.Remote needed to implement mutual TLS. This was not the case before Akka.NET v1.5.52. If you are running Akka.NET inside a private network you fully control or you were never using TLS in the first place, then this bug has no impact on you. However: if you are using TLS to secure your network YOU MUST upgrade to Akka.NET V1.5.52 or later. Patcheshttps://github.com/akkadotnet/akka.net/pull/7847 - forces "fail fast" semantics if TLS is enabled but the private key is missing or invalid. Previous versions would only check that once connection attempts occurred. https://github.com/akkadotnet/akka.net/pull/7851 - critical fix: enforces mutual TLS (mTLS) by default, so both parties must be keyed using the same certificate. This fulfills the original security These updates have been shipped into Akka.NET v1.5.52: https://github.com/akkadotnet/akka.net/releases/tag/1.5.52 WorkaroundsIf your application isn't exposed publicly, then CVE-2025-61778 has no practical impact on your application. That being said: upgrading to Akka.NET v1.5.52 or later is a good idea. ReferencesPlease view our latest network security documentation here: https://getakka.net/articles/remoting/security.html Affected versions
1.2.0
1.2.1
1.2.2
1.2.3
1.3.0
1.3.1
1.3.10
1.3.11
1.3.12
1.3.13
1.3.14
1.3.15
+ 141 more Show less
1.3.16
1.3.17
1.3.18
1.3.19
1.3.2
1.3.3
1.3.4
1.3.5
1.3.6
1.3.7
1.3.8
1.3.9
1.4.0
1.4.0-beta1
1.4.0-beta2
1.4.0-beta3
1.4.0-beta4
1.4.1
1.4.1-rc1
1.4.1-rc2
1.4.1-rc3
1.4.10
1.4.11
1.4.12
1.4.13
1.4.14
1.4.15
1.4.16
1.4.17
1.4.18
1.4.19
1.4.2
1.4.20
1.4.21
1.4.21-beta1
1.4.22
1.4.23
1.4.24
1.4.25
1.4.26
1.4.27
1.4.28
1.4.29
1.4.3
1.4.30
1.4.31
1.4.32
1.4.33
1.4.34
1.4.35
1.4.36
1.4.37
1.4.38
1.4.39
1.4.4
1.4.40
1.4.41
1.4.42
1.4.43
1.4.44
1.4.45
1.4.46
1.4.47
1.4.48
1.4.49
1.4.49-beta1
1.4.5
1.4.50
1.4.51
1.4.6
1.4.7
1.4.8
1.4.9
1.5.0
1.5.0-alpha1
1.5.0-alpha2
1.5.0-alpha3
1.5.0-alpha4
1.5.0-beta1
1.5.0-beta2
1.5.0-beta3
1.5.0-beta4
1.5.0-beta5
1.5.0-beta6
1.5.1
1.5.10
1.5.11
1.5.12
1.5.13
1.5.13-beta1
1.5.14
1.5.15
1.5.16
1.5.17
1.5.17.1
1.5.18
1.5.19
1.5.2
1.5.20
1.5.21
1.5.22
1.5.23
1.5.24
1.5.25
1.5.26
1.5.27
1.5.27-beta1
1.5.27-beta2
1.5.27.1
1.5.28
1.5.28-beta1
1.5.29
1.5.3
1.5.30
1.5.31
1.5.32
1.5.33
1.5.34
1.5.35
1.5.36
1.5.37
1.5.38
1.5.39
1.5.4
1.5.40
1.5.41
1.5.42
1.5.43
1.5.44
1.5.45
1.5.46
1.5.47
1.5.48
1.5.49
1.5.5
1.5.50
1.5.51
1.5.6
1.5.7
1.5.8
1.5.9
Fixed in
1.5.52
References
Updated Oct 07, 2025 · Source: OSV.dev |
1.5.36
patch
Dependencies (2)
|
|
1.5.35
patch
1 CVE
CVE-2025-61778
GHSA-jhpv-4q4f-43g5
Oct 07, 2025
Akka.Remote TLS did not properly implement certificate-based authentication
Critical
Network
Low
None
None
ImpactThis is a critical network security vulnerability for Akka.Remote users who have SSL / TLS enabled on their Akka.Remote connections and were expecting certificate-based authentication to be enforced on all peers attempting to join the network. In all versions of Akka.Remote from v1.2.0 to v1.5.51, TLS could be enabled via our The issue here is that for certificate-based authentication to work properly, ensuring that all members of the Akka.Remote network are secured with the same private key, Akka.Remote needed to implement mutual TLS. This was not the case before Akka.NET v1.5.52. If you are running Akka.NET inside a private network you fully control or you were never using TLS in the first place, then this bug has no impact on you. However: if you are using TLS to secure your network YOU MUST upgrade to Akka.NET V1.5.52 or later. Patcheshttps://github.com/akkadotnet/akka.net/pull/7847 - forces "fail fast" semantics if TLS is enabled but the private key is missing or invalid. Previous versions would only check that once connection attempts occurred. https://github.com/akkadotnet/akka.net/pull/7851 - critical fix: enforces mutual TLS (mTLS) by default, so both parties must be keyed using the same certificate. This fulfills the original security These updates have been shipped into Akka.NET v1.5.52: https://github.com/akkadotnet/akka.net/releases/tag/1.5.52 WorkaroundsIf your application isn't exposed publicly, then CVE-2025-61778 has no practical impact on your application. That being said: upgrading to Akka.NET v1.5.52 or later is a good idea. ReferencesPlease view our latest network security documentation here: https://getakka.net/articles/remoting/security.html Affected versions
1.2.0
1.2.1
1.2.2
1.2.3
1.3.0
1.3.1
1.3.10
1.3.11
1.3.12
1.3.13
1.3.14
1.3.15
+ 141 more Show less
1.3.16
1.3.17
1.3.18
1.3.19
1.3.2
1.3.3
1.3.4
1.3.5
1.3.6
1.3.7
1.3.8
1.3.9
1.4.0
1.4.0-beta1
1.4.0-beta2
1.4.0-beta3
1.4.0-beta4
1.4.1
1.4.1-rc1
1.4.1-rc2
1.4.1-rc3
1.4.10
1.4.11
1.4.12
1.4.13
1.4.14
1.4.15
1.4.16
1.4.17
1.4.18
1.4.19
1.4.2
1.4.20
1.4.21
1.4.21-beta1
1.4.22
1.4.23
1.4.24
1.4.25
1.4.26
1.4.27
1.4.28
1.4.29
1.4.3
1.4.30
1.4.31
1.4.32
1.4.33
1.4.34
1.4.35
1.4.36
1.4.37
1.4.38
1.4.39
1.4.4
1.4.40
1.4.41
1.4.42
1.4.43
1.4.44
1.4.45
1.4.46
1.4.47
1.4.48
1.4.49
1.4.49-beta1
1.4.5
1.4.50
1.4.51
1.4.6
1.4.7
1.4.8
1.4.9
1.5.0
1.5.0-alpha1
1.5.0-alpha2
1.5.0-alpha3
1.5.0-alpha4
1.5.0-beta1
1.5.0-beta2
1.5.0-beta3
1.5.0-beta4
1.5.0-beta5
1.5.0-beta6
1.5.1
1.5.10
1.5.11
1.5.12
1.5.13
1.5.13-beta1
1.5.14
1.5.15
1.5.16
1.5.17
1.5.17.1
1.5.18
1.5.19
1.5.2
1.5.20
1.5.21
1.5.22
1.5.23
1.5.24
1.5.25
1.5.26
1.5.27
1.5.27-beta1
1.5.27-beta2
1.5.27.1
1.5.28
1.5.28-beta1
1.5.29
1.5.3
1.5.30
1.5.31
1.5.32
1.5.33
1.5.34
1.5.35
1.5.36
1.5.37
1.5.38
1.5.39
1.5.4
1.5.40
1.5.41
1.5.42
1.5.43
1.5.44
1.5.45
1.5.46
1.5.47
1.5.48
1.5.49
1.5.5
1.5.50
1.5.51
1.5.6
1.5.7
1.5.8
1.5.9
Fixed in
1.5.52
References
Updated Oct 07, 2025 · Source: OSV.dev |
1.5.35
patch
Dependencies (2)
|
|
1.5.34
patch
1 CVE
CVE-2025-61778
GHSA-jhpv-4q4f-43g5
Oct 07, 2025
Akka.Remote TLS did not properly implement certificate-based authentication
Critical
Network
Low
None
None
ImpactThis is a critical network security vulnerability for Akka.Remote users who have SSL / TLS enabled on their Akka.Remote connections and were expecting certificate-based authentication to be enforced on all peers attempting to join the network. In all versions of Akka.Remote from v1.2.0 to v1.5.51, TLS could be enabled via our The issue here is that for certificate-based authentication to work properly, ensuring that all members of the Akka.Remote network are secured with the same private key, Akka.Remote needed to implement mutual TLS. This was not the case before Akka.NET v1.5.52. If you are running Akka.NET inside a private network you fully control or you were never using TLS in the first place, then this bug has no impact on you. However: if you are using TLS to secure your network YOU MUST upgrade to Akka.NET V1.5.52 or later. Patcheshttps://github.com/akkadotnet/akka.net/pull/7847 - forces "fail fast" semantics if TLS is enabled but the private key is missing or invalid. Previous versions would only check that once connection attempts occurred. https://github.com/akkadotnet/akka.net/pull/7851 - critical fix: enforces mutual TLS (mTLS) by default, so both parties must be keyed using the same certificate. This fulfills the original security These updates have been shipped into Akka.NET v1.5.52: https://github.com/akkadotnet/akka.net/releases/tag/1.5.52 WorkaroundsIf your application isn't exposed publicly, then CVE-2025-61778 has no practical impact on your application. That being said: upgrading to Akka.NET v1.5.52 or later is a good idea. ReferencesPlease view our latest network security documentation here: https://getakka.net/articles/remoting/security.html Affected versions
1.2.0
1.2.1
1.2.2
1.2.3
1.3.0
1.3.1
1.3.10
1.3.11
1.3.12
1.3.13
1.3.14
1.3.15
+ 141 more Show less
1.3.16
1.3.17
1.3.18
1.3.19
1.3.2
1.3.3
1.3.4
1.3.5
1.3.6
1.3.7
1.3.8
1.3.9
1.4.0
1.4.0-beta1
1.4.0-beta2
1.4.0-beta3
1.4.0-beta4
1.4.1
1.4.1-rc1
1.4.1-rc2
1.4.1-rc3
1.4.10
1.4.11
1.4.12
1.4.13
1.4.14
1.4.15
1.4.16
1.4.17
1.4.18
1.4.19
1.4.2
1.4.20
1.4.21
1.4.21-beta1
1.4.22
1.4.23
1.4.24
1.4.25
1.4.26
1.4.27
1.4.28
1.4.29
1.4.3
1.4.30
1.4.31
1.4.32
1.4.33
1.4.34
1.4.35
1.4.36
1.4.37
1.4.38
1.4.39
1.4.4
1.4.40
1.4.41
1.4.42
1.4.43
1.4.44
1.4.45
1.4.46
1.4.47
1.4.48
1.4.49
1.4.49-beta1
1.4.5
1.4.50
1.4.51
1.4.6
1.4.7
1.4.8
1.4.9
1.5.0
1.5.0-alpha1
1.5.0-alpha2
1.5.0-alpha3
1.5.0-alpha4
1.5.0-beta1
1.5.0-beta2
1.5.0-beta3
1.5.0-beta4
1.5.0-beta5
1.5.0-beta6
1.5.1
1.5.10
1.5.11
1.5.12
1.5.13
1.5.13-beta1
1.5.14
1.5.15
1.5.16
1.5.17
1.5.17.1
1.5.18
1.5.19
1.5.2
1.5.20
1.5.21
1.5.22
1.5.23
1.5.24
1.5.25
1.5.26
1.5.27
1.5.27-beta1
1.5.27-beta2
1.5.27.1
1.5.28
1.5.28-beta1
1.5.29
1.5.3
1.5.30
1.5.31
1.5.32
1.5.33
1.5.34
1.5.35
1.5.36
1.5.37
1.5.38
1.5.39
1.5.4
1.5.40
1.5.41
1.5.42
1.5.43
1.5.44
1.5.45
1.5.46
1.5.47
1.5.48
1.5.49
1.5.5
1.5.50
1.5.51
1.5.6
1.5.7
1.5.8
1.5.9
Fixed in
1.5.52
References
Updated Oct 07, 2025 · Source: OSV.dev |
1.5.34
patch
Dependencies (2)
|
|
1.5.33
patch
1 CVE
CVE-2025-61778
GHSA-jhpv-4q4f-43g5
Oct 07, 2025
Akka.Remote TLS did not properly implement certificate-based authentication
Critical
Network
Low
None
None
ImpactThis is a critical network security vulnerability for Akka.Remote users who have SSL / TLS enabled on their Akka.Remote connections and were expecting certificate-based authentication to be enforced on all peers attempting to join the network. In all versions of Akka.Remote from v1.2.0 to v1.5.51, TLS could be enabled via our The issue here is that for certificate-based authentication to work properly, ensuring that all members of the Akka.Remote network are secured with the same private key, Akka.Remote needed to implement mutual TLS. This was not the case before Akka.NET v1.5.52. If you are running Akka.NET inside a private network you fully control or you were never using TLS in the first place, then this bug has no impact on you. However: if you are using TLS to secure your network YOU MUST upgrade to Akka.NET V1.5.52 or later. Patcheshttps://github.com/akkadotnet/akka.net/pull/7847 - forces "fail fast" semantics if TLS is enabled but the private key is missing or invalid. Previous versions would only check that once connection attempts occurred. https://github.com/akkadotnet/akka.net/pull/7851 - critical fix: enforces mutual TLS (mTLS) by default, so both parties must be keyed using the same certificate. This fulfills the original security These updates have been shipped into Akka.NET v1.5.52: https://github.com/akkadotnet/akka.net/releases/tag/1.5.52 WorkaroundsIf your application isn't exposed publicly, then CVE-2025-61778 has no practical impact on your application. That being said: upgrading to Akka.NET v1.5.52 or later is a good idea. ReferencesPlease view our latest network security documentation here: https://getakka.net/articles/remoting/security.html Affected versions
1.2.0
1.2.1
1.2.2
1.2.3
1.3.0
1.3.1
1.3.10
1.3.11
1.3.12
1.3.13
1.3.14
1.3.15
+ 141 more Show less
1.3.16
1.3.17
1.3.18
1.3.19
1.3.2
1.3.3
1.3.4
1.3.5
1.3.6
1.3.7
1.3.8
1.3.9
1.4.0
1.4.0-beta1
1.4.0-beta2
1.4.0-beta3
1.4.0-beta4
1.4.1
1.4.1-rc1
1.4.1-rc2
1.4.1-rc3
1.4.10
1.4.11
1.4.12
1.4.13
1.4.14
1.4.15
1.4.16
1.4.17
1.4.18
1.4.19
1.4.2
1.4.20
1.4.21
1.4.21-beta1
1.4.22
1.4.23
1.4.24
1.4.25
1.4.26
1.4.27
1.4.28
1.4.29
1.4.3
1.4.30
1.4.31
1.4.32
1.4.33
1.4.34
1.4.35
1.4.36
1.4.37
1.4.38
1.4.39
1.4.4
1.4.40
1.4.41
1.4.42
1.4.43
1.4.44
1.4.45
1.4.46
1.4.47
1.4.48
1.4.49
1.4.49-beta1
1.4.5
1.4.50
1.4.51
1.4.6
1.4.7
1.4.8
1.4.9
1.5.0
1.5.0-alpha1
1.5.0-alpha2
1.5.0-alpha3
1.5.0-alpha4
1.5.0-beta1
1.5.0-beta2
1.5.0-beta3
1.5.0-beta4
1.5.0-beta5
1.5.0-beta6
1.5.1
1.5.10
1.5.11
1.5.12
1.5.13
1.5.13-beta1
1.5.14
1.5.15
1.5.16
1.5.17
1.5.17.1
1.5.18
1.5.19
1.5.2
1.5.20
1.5.21
1.5.22
1.5.23
1.5.24
1.5.25
1.5.26
1.5.27
1.5.27-beta1
1.5.27-beta2
1.5.27.1
1.5.28
1.5.28-beta1
1.5.29
1.5.3
1.5.30
1.5.31
1.5.32
1.5.33
1.5.34
1.5.35
1.5.36
1.5.37
1.5.38
1.5.39
1.5.4
1.5.40
1.5.41
1.5.42
1.5.43
1.5.44
1.5.45
1.5.46
1.5.47
1.5.48
1.5.49
1.5.5
1.5.50
1.5.51
1.5.6
1.5.7
1.5.8
1.5.9
Fixed in
1.5.52
References
Updated Oct 07, 2025 · Source: OSV.dev |
1.5.33
patch
Dependencies (2)
|
|
1.5.32
patch
1 CVE
CVE-2025-61778
GHSA-jhpv-4q4f-43g5
Oct 07, 2025
Akka.Remote TLS did not properly implement certificate-based authentication
Critical
Network
Low
None
None
ImpactThis is a critical network security vulnerability for Akka.Remote users who have SSL / TLS enabled on their Akka.Remote connections and were expecting certificate-based authentication to be enforced on all peers attempting to join the network. In all versions of Akka.Remote from v1.2.0 to v1.5.51, TLS could be enabled via our The issue here is that for certificate-based authentication to work properly, ensuring that all members of the Akka.Remote network are secured with the same private key, Akka.Remote needed to implement mutual TLS. This was not the case before Akka.NET v1.5.52. If you are running Akka.NET inside a private network you fully control or you were never using TLS in the first place, then this bug has no impact on you. However: if you are using TLS to secure your network YOU MUST upgrade to Akka.NET V1.5.52 or later. Patcheshttps://github.com/akkadotnet/akka.net/pull/7847 - forces "fail fast" semantics if TLS is enabled but the private key is missing or invalid. Previous versions would only check that once connection attempts occurred. https://github.com/akkadotnet/akka.net/pull/7851 - critical fix: enforces mutual TLS (mTLS) by default, so both parties must be keyed using the same certificate. This fulfills the original security These updates have been shipped into Akka.NET v1.5.52: https://github.com/akkadotnet/akka.net/releases/tag/1.5.52 WorkaroundsIf your application isn't exposed publicly, then CVE-2025-61778 has no practical impact on your application. That being said: upgrading to Akka.NET v1.5.52 or later is a good idea. ReferencesPlease view our latest network security documentation here: https://getakka.net/articles/remoting/security.html Affected versions
1.2.0
1.2.1
1.2.2
1.2.3
1.3.0
1.3.1
1.3.10
1.3.11
1.3.12
1.3.13
1.3.14
1.3.15
+ 141 more Show less
1.3.16
1.3.17
1.3.18
1.3.19
1.3.2
1.3.3
1.3.4
1.3.5
1.3.6
1.3.7
1.3.8
1.3.9
1.4.0
1.4.0-beta1
1.4.0-beta2
1.4.0-beta3
1.4.0-beta4
1.4.1
1.4.1-rc1
1.4.1-rc2
1.4.1-rc3
1.4.10
1.4.11
1.4.12
1.4.13
1.4.14
1.4.15
1.4.16
1.4.17
1.4.18
1.4.19
1.4.2
1.4.20
1.4.21
1.4.21-beta1
1.4.22
1.4.23
1.4.24
1.4.25
1.4.26
1.4.27
1.4.28
1.4.29
1.4.3
1.4.30
1.4.31
1.4.32
1.4.33
1.4.34
1.4.35
1.4.36
1.4.37
1.4.38
1.4.39
1.4.4
1.4.40
1.4.41
1.4.42
1.4.43
1.4.44
1.4.45
1.4.46
1.4.47
1.4.48
1.4.49
1.4.49-beta1
1.4.5
1.4.50
1.4.51
1.4.6
1.4.7
1.4.8
1.4.9
1.5.0
1.5.0-alpha1
1.5.0-alpha2
1.5.0-alpha3
1.5.0-alpha4
1.5.0-beta1
1.5.0-beta2
1.5.0-beta3
1.5.0-beta4
1.5.0-beta5
1.5.0-beta6
1.5.1
1.5.10
1.5.11
1.5.12
1.5.13
1.5.13-beta1
1.5.14
1.5.15
1.5.16
1.5.17
1.5.17.1
1.5.18
1.5.19
1.5.2
1.5.20
1.5.21
1.5.22
1.5.23
1.5.24
1.5.25
1.5.26
1.5.27
1.5.27-beta1
1.5.27-beta2
1.5.27.1
1.5.28
1.5.28-beta1
1.5.29
1.5.3
1.5.30
1.5.31
1.5.32
1.5.33
1.5.34
1.5.35
1.5.36
1.5.37
1.5.38
1.5.39
1.5.4
1.5.40
1.5.41
1.5.42
1.5.43
1.5.44
1.5.45
1.5.46
1.5.47
1.5.48
1.5.49
1.5.5
1.5.50
1.5.51
1.5.6
1.5.7
1.5.8
1.5.9
Fixed in
1.5.52
References
Updated Oct 07, 2025 · Source: OSV.dev |
1.5.32
patch
Dependencies (2)
|
|
1.5.31
patch
1 CVE
CVE-2025-61778
GHSA-jhpv-4q4f-43g5
Oct 07, 2025
Akka.Remote TLS did not properly implement certificate-based authentication
Critical
Network
Low
None
None
ImpactThis is a critical network security vulnerability for Akka.Remote users who have SSL / TLS enabled on their Akka.Remote connections and were expecting certificate-based authentication to be enforced on all peers attempting to join the network. In all versions of Akka.Remote from v1.2.0 to v1.5.51, TLS could be enabled via our The issue here is that for certificate-based authentication to work properly, ensuring that all members of the Akka.Remote network are secured with the same private key, Akka.Remote needed to implement mutual TLS. This was not the case before Akka.NET v1.5.52. If you are running Akka.NET inside a private network you fully control or you were never using TLS in the first place, then this bug has no impact on you. However: if you are using TLS to secure your network YOU MUST upgrade to Akka.NET V1.5.52 or later. Patcheshttps://github.com/akkadotnet/akka.net/pull/7847 - forces "fail fast" semantics if TLS is enabled but the private key is missing or invalid. Previous versions would only check that once connection attempts occurred. https://github.com/akkadotnet/akka.net/pull/7851 - critical fix: enforces mutual TLS (mTLS) by default, so both parties must be keyed using the same certificate. This fulfills the original security These updates have been shipped into Akka.NET v1.5.52: https://github.com/akkadotnet/akka.net/releases/tag/1.5.52 WorkaroundsIf your application isn't exposed publicly, then CVE-2025-61778 has no practical impact on your application. That being said: upgrading to Akka.NET v1.5.52 or later is a good idea. ReferencesPlease view our latest network security documentation here: https://getakka.net/articles/remoting/security.html Affected versions
1.2.0
1.2.1
1.2.2
1.2.3
1.3.0
1.3.1
1.3.10
1.3.11
1.3.12
1.3.13
1.3.14
1.3.15
+ 141 more Show less
1.3.16
1.3.17
1.3.18
1.3.19
1.3.2
1.3.3
1.3.4
1.3.5
1.3.6
1.3.7
1.3.8
1.3.9
1.4.0
1.4.0-beta1
1.4.0-beta2
1.4.0-beta3
1.4.0-beta4
1.4.1
1.4.1-rc1
1.4.1-rc2
1.4.1-rc3
1.4.10
1.4.11
1.4.12
1.4.13
1.4.14
1.4.15
1.4.16
1.4.17
1.4.18
1.4.19
1.4.2
1.4.20
1.4.21
1.4.21-beta1
1.4.22
1.4.23
1.4.24
1.4.25
1.4.26
1.4.27
1.4.28
1.4.29
1.4.3
1.4.30
1.4.31
1.4.32
1.4.33
1.4.34
1.4.35
1.4.36
1.4.37
1.4.38
1.4.39
1.4.4
1.4.40
1.4.41
1.4.42
1.4.43
1.4.44
1.4.45
1.4.46
1.4.47
1.4.48
1.4.49
1.4.49-beta1
1.4.5
1.4.50
1.4.51
1.4.6
1.4.7
1.4.8
1.4.9
1.5.0
1.5.0-alpha1
1.5.0-alpha2
1.5.0-alpha3
1.5.0-alpha4
1.5.0-beta1
1.5.0-beta2
1.5.0-beta3
1.5.0-beta4
1.5.0-beta5
1.5.0-beta6
1.5.1
1.5.10
1.5.11
1.5.12
1.5.13
1.5.13-beta1
1.5.14
1.5.15
1.5.16
1.5.17
1.5.17.1
1.5.18
1.5.19
1.5.2
1.5.20
1.5.21
1.5.22
1.5.23
1.5.24
1.5.25
1.5.26
1.5.27
1.5.27-beta1
1.5.27-beta2
1.5.27.1
1.5.28
1.5.28-beta1
1.5.29
1.5.3
1.5.30
1.5.31
1.5.32
1.5.33
1.5.34
1.5.35
1.5.36
1.5.37
1.5.38
1.5.39
1.5.4
1.5.40
1.5.41
1.5.42
1.5.43
1.5.44
1.5.45
1.5.46
1.5.47
1.5.48
1.5.49
1.5.5
1.5.50
1.5.51
1.5.6
1.5.7
1.5.8
1.5.9
Fixed in
1.5.52
References
Updated Oct 07, 2025 · Source: OSV.dev |
1.5.31
patch
Dependencies (2)
|