PT-2025-40934 · Akka+1 · Akka+1
Aaronontheweb
·
Published
2025-10-06
·
Updated
2025-10-10
·
CVE-2025-61778
CVSS v4.0
9.3
Critical
| Vector | AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N |
Name of the Vulnerable Software and Affected Versions
Akka.NET versions 1.2.0 through 1.5.51
Description
Akka.NET, a .NET port of the Akka project, has an issue where the Akka.Remote component did not implement mutual TLS (mTLS) in versions 1.2.0 through 1.5.51. When TLS was enabled via the
akka.remote.dot-netty.tcp transport, the server correctly validated private keys for inbound connections, but it did not require clients to present their certificates. This allowed untrusted parties to connect to a cluster secured with a private key and begin communicating without authentication. The issue was addressed by enforcing mTLS by default, requiring both parties to be keyed using the same certificate. A patch was also implemented to enforce "fail fast" semantics if TLS is enabled but the private key is missing or invalid. The vulnerability affects those running Akka.NET inside a private network or those who were not using TLS.Recommendations
Upgrade to Akka.NET version 1.5.52 or later.
As a workaround, avoid exposing the application publicly.
Exploit
Fix
Missing Authentication
Authentication Bypass by Spoofing
Improper Certificate Validation
Found an issue in the description? Have something to add? Feel free to write us 👾
Related Identifiers
Affected Products
Akka
Akka.Net