Skip to content
Fencer Intel
medium 6.0

CVE-2025-53393 json

akka-cluster-metrics uses Java serialization for cluster metrics

published last yr. modified 4mo ago also EUVD-2025-19463 , GHSA-358m-fq53-hp87

cvss
6.0
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
0.2%
EPSS 0.2% chance of exploitation in 30 days, percentile 13%
public exploits
0
none known

Summary

In Akka through 2.10.6, akka-cluster-metrics uses Java serialization for cluster metrics.

Patch / fix

Is CVE-2025-53393 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

CISA SSVC

Exploitation
none
Automatable
no
Technical impact
partial
Assessed
last yr.

Exploit prediction

0.23% chance of exploitation in the next 30 days, higher than 13% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by version score vector
CNA 3.1 6.0 CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:L/I:L/A:L
GitHub 3.1 6.0 CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:L/I:L/A:L

Affected packages

ecosystem package affected fixed in
maven com.typesafe.akka:akka-cluster-metrics_3
<=2.10.6
 no fix listed
maven com.typesafe.akka:akka-cluster-metrics_2.13
<=2.10.6
 no fix listed

Affected products

  • Akka Akka

Classification

Weakness
  • CWE-502 Deserialization of Untrusted Data

References

Sources

Fencer Intel 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.

CPEs and fixed versions use Anchore's correction of NVD's data: Added CPE configurations because not yet analyzed by NVD.