Akka vulnerabilitiesRanked by how likely they are to be used.
Akka is made by Lightbend. We track 1 published vulnerability listed under that exact name, across 18 versions. None of them is on the list of flaws known to be exploited today. Lightbend lists newer releases under their own names, such as Akka HTTP, so check those pages too.
We keep watching the known-exploited list.
Is Akka listed under other names? Yes.
Lightbend also lists Akka under more specific names, such as Akka HTTP and Akka Actor. Flaws listed only under those names are counted on their own pages, not here. If you run one of these, open its page for its own exploited flaws.
Which Akka vulnerabilities are being exploited?
This is the list that matters most: flaws criminals are using now.
None of Akka's published vulnerabilities is on the list of flaws known to be exploited today. We keep watching that list.
Which Akka flaws are most likely to be used?
Ranked by the latest exploit-likelihood forecast: the chance each flaw is used in an attack in the next 30 days. A high severity score on its own doesn't tell you that. Flaws shared by many other makers' products are left out.
- 1.2%CVE-2018-16115Critical
Lightbend Akka 2.5.x before 2.5.16 allows message disclosure and modification because of an RNG error.
Running Akka? We'll keep checking.
Looking flaws up one at a time doesn't scale. Tell us what you run once, and we tell you which flaws matter to you, in what order, and keep watching for new ones.
- Tell us what you runPick your software from a list, or let us work it out from your website.
- We match it to every flawOver 400,000 published flaws, checked against your list.
- Ranked by real-world riskA 0 to 100 score, led by evidence criminals are using it.
- Told as soon as we knowAn alert by email, in the app or by webhook to your own tools.
Free plan, no card needed. Nothing to install.
1 new flaw affects software Acme tracks
Lightbend Akka 2.5.x before 2.5.16 allows message disclosure and modification because of an RNG error. A random number generator is used in Akka Remoting for TLS (both classic and Artery Remoting). Akka allows configuration of custom random number generators. For historical reasons, Akka included the AES128CounterSecureRNG and AES256CounterSecureRNG random number generators. The implementations had a bug that caused the generated numbers to be repeated after only a few bytes. The custom RNG implementations were not configured by default but examples in the documentation showed (and therefore implicitly recommended) using the custom ones. This can be used by an attacker to compromise the communication if these random number generators are enabled in configuration. It would be possible to eavesdrop, replay, or modify the messages sent with Akka Remoting/Cluster.
- Matched to
- Akka on Acme's software list
- What to do
- Plan in the vendor’s update
Sent to the alert recipients Acme chose. Also in the app and to Acme's webhook.
We track 1 published vulnerability listed under the name Akka, across 18 versions.
None of Akka's vulnerabilities is on the list of flaws known to be exploited today.
Lightbend also lists Akka under more specific names, such as Akka HTTP and Akka Actor. Flaws listed only under those names are counted on their own pages, not here. Open the release you run to see its own list.
Create a Precursor Intelligence account and track Akka. We match it against every published flaw, give each one a risk score from 0 to 100 and keep watching, so you hear about new ones as soon as we know, by email, in the app or by webhook.