Loading...
Skip to main content

CVE-2025-61778 — Vulnerability in Akka.Cluster — CVE Details

CRITICAL

Akka.Remote TLS did not properly implement certificate-based authentication

Published October 7, 2025Updated October 7, 2025Source: osv

Summary

### Impact This 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 `akka.remote.dot-netty.tcp` transport and this would correctly enforce private key validation on the server-side of inbound connections. Akka.Remote, however, never asked the outbound-connecting client to present ITS certificate - therefore it's possible for untrusted parties to connect to a private key'd Akka.NET cluster and begin communicating with it **without any certificate**. 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. ### Patches https://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 ### Workarounds If 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. ### References Please view our latest network security documentation here: https://getakka.net/articles/remoting/security.html

Advisory Timeline

  • First published October 7, 2025 (370 days ago).
  • Last revised October 7, 2025 — 0 days after initial publication.

Remediation

Upgrade to the fixed version using your package manager.

NuGet
Update Akka.Cluster to 1.5.52 or later
dotnet add package Akka.Cluster --version 1.5.52
NuGet
Update Akka.Remote to 1.5.52 or later
dotnet add package Akka.Remote --version 1.5.52

After upgrading, run your dependency scanner again to confirm the vulnerability is resolved.

Affected Packages (2)

Affects 1 ecosystem: nuget (2).

PackageEcosystemAffectedFixed In
Akka.Cluster
nuget
1.2.0, 1.2.1, 1.2.2, 1.2.3 (+149 more)1.5.52
Akka.Remote
nuget
1.2.0, 1.2.1, 1.2.2, 1.2.3 (+149 more)1.5.52

Vulnerability Classification

Common Weakness Enumeration (CWE) identifiers for this vulnerability type.

CVSS Score Breakdown

What the CVSS (Common Vulnerability Scoring System) 9.1 score means for each attack dimension.

Attack Vector
Network
Attack Complexity
Low
Privileges Required
None
User Interaction
None
Scope
—
Confidentiality
—
Integrity
—
Availability
—

CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N

Frequently Asked Questions

What is CVE-2025-61778?
Akka.Remote TLS did not properly implement certificate-based authentication This vulnerability has been assigned a severity rating of CRITICAL (CVSS score: 9.1/10).
How do I check if my project is affected by CVE-2025-61778?
CVE-2025-61778 affects Akka.Cluster and Akka.Remote. Use GeekWala's free vulnerability scanner to check your dependencies against CVE-2025-61778 and 200,000+ other known vulnerabilities.

Severity & Exploitability

CVSS Score
9.1

Exploitation is straightforward and causes maximum impact. Patch immediately.

Also Known As

GHSA-jhpv-4q4f-43g5

Related CVEs

Check if you're affected

Scan your dependencies to see if this vulnerability affects your projects.

Scan Your Dependencies