Skip to content
Fencer Vulns
high 8.1

CVE-2017-1000034 json

Akka Java Serialization vulnerability

published 2017-07-13 9 y ago modified 2026-06-17 4 mo ago also GHSA-mm57-9j6q-rxm2 , EUVD-2018-0642

cvss
8.1
version 3.0, NVD
cisa kev
Not listed
not in CISA's catalog
epss
6.2%
EPSS 6.2% chance of exploitation in 30 days, percentile 93%
public exploits
0
none known

Summary

Akka versions <=2.4.16 and 2.5-M1 are vulnerable to a java deserialization attack in its Remoting component resulting in remote code execution in the context of the ActorSystem.

Patch / fix

  • maven com.typesafe.akka:akka-actor 2.4.17

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2017-1000034 updated cvss 7.5

akka-actor: Java deserialization issue in the Remoting component

  • Red Hat OpenStack Platform 8 (Liberty) opendaylight Red Hat OpenStack Platform 9 (Mitaka) opendaylight Red Hat OpenStack Platform 10 (Newton) opendaylight Red Hat OpenStack Platform 11 (Ocata) opendaylight
    affected: no fix planned “Will not fix”
  • Red Hat OpenStack Platform 12 (Pike) opendaylight
    not affected: vulnerable code not present

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

Exploit prediction

6.19% chance of exploitation in the next 30 days, higher than 93% of all scored CVEs (FIRST EPSS, 2026-11-08).

CVSS scores

assigned by version score vector
NVD 3.0 8.1 CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H
NVD 2.0 9.3 AV:N/AC:M/Au:N/C:C/I:C/A:C
GitHub 3.0 8.1 CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H

Affected packages

ecosystem package affected fixed in
maven com.typesafe.akka:akka-actor
<2.4.17
2.4.17

Classification

Weakness
  • CWE-502 Deserialization of Untrusted Data

References

Sources

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.