How severe is GHSA-jhpv-4q4f-43g5?

No CVSS score has been assigned to GHSA-jhpv-4q4f-43g5 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-jhpv-4q4f-43g5?

GHSA-jhpv-4q4f-43g5 affects the following packages: Akka.Remote (NuGet), Akka.Cluster (NuGet). Ecosystems affected: NuGet.

How do I fix GHSA-jhpv-4q4f-43g5?

Update Akka.Remote to 1.5.52 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-jhpv-4q4f-43g5 is resolved across your whole dependency graph.

How do I detect GHSA-jhpv-4q4f-43g5 in my NuGet dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for Akka.Remote, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate GHSA-jhpv-4q4f-43g5 if there is no patch (or I can't update yet)?

Put an independent control in front of the weakness: restrict the affected endpoint or interface to trusted networks, require an additional authentication factor or proxy-level check, and invalidate existing sessions and credentials in case the flaw has already been used.

Is GHSA-jhpv-4q4f-43g5 actively exploited in the wild?

No public exploit code has been indexed for GHSA-jhpv-4q4f-43g5 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for GHSA-jhpv-4q4f-43g5?

GHSA-jhpv-4q4f-43g5 has an EPSS (Exploit Prediction Scoring System) score of 0.3%, placing it in the 24th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is GHSA-jhpv-4q4f-43g5?

GHSA-jhpv-4q4f-43g5 is classified as CWE-290 (CWE-290), CWE-295 (CWE-295), Missing Authentication (CWE-306). These weakness types describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was GHSA-jhpv-4q4f-43g5 published, and has it been updated?

GHSA-jhpv-4q4f-43g5 was published on October 7, 2025 and was last updated on October 7, 2025. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

.NET NuGet

Not in CISA KEV

Akka.Remote TLS did not properly implement certificate-based authenticationGHSA-jhpv-4q4f-43g5

Fix: akkadotnet/akka.net#7847

GHSA-jhpv-4q4f-43g5 is a CWE-290 vulnerability in Akka.Remote. A fix is available for Akka.Remote — see the affected versions and patch details below.

Also known asCVE-2025-61778

Published

Oct 7, 2025

Updated

Oct 7, 2025

Affected

2 pkgs

Patched

2 / 2

Exploits

None indexed

Exploitation data as of Nov 6, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

No confirmed exploitation observed yet

CISA assesses this as automatable — exploitation doesn’t require manual, per-target effort, which raises the odds of mass scanning and opportunistic attacks.
CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for GHSA-jhpv-4q4f-43g5.

EPSS Exploitation Probability

via FIRST.org ↗

0.3%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs24th percentile — riskier than 24% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

Real-World Exposure

2 pkgs affected

.NETAkka.Remote.NETAkka.Cluster

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects NuGet packages — download data is not available via public APIs for these ecosystems.

Description

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

Affected Packages

2 total 2 fixed

Ecosystem	Package	Vulnerable range	Fix
.NETNuGet	`Akka.Remote`	≥ 1.2.0&&< 1.5.52	1.5.52`dotnet add package Akka.Remote --version 1.5.52`
.NETNuGet	`Akka.Cluster`	≥ 1.2.0&&< 1.5.52	1.5.52`dotnet add package Akka.Cluster --version 1.5.52`

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for Akka.Remote, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update Akka.Remote to 1.5.52 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-jhpv-4q4f-43g5 is resolved across your whole dependency graph.
Workarounds
Put an independent control in front of the weakness: restrict the affected endpoint or interface to trusted networks, require an additional authentication factor or proxy-level check, and invalidate existing sessions and credentials in case the flaw has already been used.

Frequently Asked Questions

### 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

O3 Security · Impact-Aware SCA

Is GHSA-jhpv-4q4f-43g5 in your dependencies?

Find it across NuGet, including transitive dependencies.

Scan my dependencies How O3 SCA works