{"answers":{"affected":"4 open source packages ship an affected version, including Akka.Cluster and Akka.Remote.","exploited":"There is no known exploitation of CVE-2025-61778 in the wild and no public exploit code.","fix":"Upgrade Akka.Cluster to 1.5.52 or later.","what":"CVE-2025-61778 is a critical authentication bypass vulnerability in akkadotnet akka.net, published on 6 Oct 2025. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2025-61778 and fix it if it is affected.\n\nWhat it is: CVE-2025-61778 is a critical authentication bypass vulnerability in akkadotnet akka.net, published on 6 Oct 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2025-61778 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- Akka.Cluster (NuGet): affected from 1.2.0; fixed in 1.5.52\n- Akka.Cluster (NuGet): affected from 1.2.0; fixed in 1.5.52\n- Akka.Remote (NuGet): affected from 1.2.0; fixed in 1.5.52\n- Akka.Remote (NuGet): affected from 1.2.0; fixed in 1.5.52\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2025-61778/ (Markdown: https://insights.sbomify.com/CVE-2025-61778/index.md)","id":"CVE-2025-61778","markdown":"https://insights.sbomify.com/CVE-2025-61778/index.md","name":"CVE-2025-61778","record":{"aliases":["GHSA-jhpv-4q4f-43g5"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["security_bypass","data_read"],"network_reachable":"yes","non_default_config":true,"product_category":"Akka.NET library","requires_auth":"none","summary":"Untrusted parties can connect to Akka.NET clusters using TLS because mutual authentication was not enforced, allowing unauthorized communication.","user_interaction":"not_required","vuln_class":"auth_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":9.3,"severity":"critical","source":"cna","vector":"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","version":"4.0"},"cwes":[{"id":"CWE-306","name":"Missing Authentication for Critical Functionality"},{"id":"CWE-295","name":"Improper Certificate Validation"},{"id":"CWE-290","name":"Authentication Bypass by Spoofing"}],"description":"Akka.NET is a .NET port of the Akka project from the Scala / Java community. 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. Those who run Akka.NET inside a private network that they fully control or who were never using TLS in the first place are now affected by the bug. However, those who use TLS to secure their networks must upgrade to Akka.NET V1.5.52 or later. One patch 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. The second patch, a critical fix, enforces mutual TLS (mTLS) by default, so both parties must be keyed using the same certificate. As a workaround, avoid exposing the application publicly to avoid the vulnerability having a practical impact on one's application. However, upgrading to version 1.5.52 is still recommended by the maintainers.","ecosystems":["NuGet"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"Akka.Remote TLS did not properly implement certificate-based authentication","id":"CVE-2025-61778","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"NuGet","product":null,"products":[],"type":"auth_bypass","year":"2025"},"n_packages":4,"n_references":5,"next":{"headline":"Trustee's attestation-policy endpoint is not protected by admin autentication","id":"CVE-2025-61779"},"packages":[{"ecosystem":"NuGet","fixed":["1.5.52"],"introduced":["1.2.0"],"last_affected":[],"package":"Akka.Cluster","purl":null,"source":"GHSA-jhpv-4q4f-43g5"},{"ecosystem":"NuGet","fixed":["1.5.52"],"introduced":["1.2.0"],"last_affected":[],"package":"Akka.Cluster","purl":"pkg:nuget/Akka.Cluster","source":"GHSA-jhpv-4q4f-43g5"},{"ecosystem":"NuGet","fixed":["1.5.52"],"introduced":["1.2.0"],"last_affected":[],"package":"Akka.Remote","purl":null,"source":"GHSA-jhpv-4q4f-43g5"},{"ecosystem":"NuGet","fixed":["1.5.52"],"introduced":["1.2.0"],"last_affected":[],"package":"Akka.Remote","purl":"pkg:nuget/Akka.Remote","source":"GHSA-jhpv-4q4f-43g5"}],"prev":{"headline":"FlagForge Allows Unauthenticated Badge Template API Access","id":"CVE-2025-61777"},"products":["akka.net"],"published":"2025-10-06","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"yes","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2025-10-06","vendors":["akkadotnet"]},"summary":"Untrusted parties can connect to Akka.NET clusters using TLS because mutual authentication was not enforced, allowing unauthorized communication.","url":"https://insights.sbomify.com/CVE-2025-61778/"}