Vulnerability in N/a

CVE-2025-51606

hippo4j 1.0.0 to 1.5.0, uses a hard-coded secret key in its JWT (JSON Web Token) creation. This allows attackers with access to the source code or compiled binary to forge valid access tokens and impersonate any user, including privileged ones such as "admin". The vulnerability poses a critical security risk in systems where authentication and authorization rely on the integrity of JWTs.

Published · last modified .

CVSS v3 metric

CVSS v3 base score 8.8 (High). Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H.

EPSS exploit prediction

EPSS: 0.004 (26.6th percentile), scored .

Very low probability of exploitation in the next 30 days; routine patching cadence is appropriate. 27th percentile — 26.6% of CVEs in the catalogue have a lower EPSS than this one. How to read EPSS.

EPSS trend (30 days)EPSS over the last 30 days for CVE-2025-51606: held from 0.003 to 0.004.

EPSS over last 30 days · oldest: 0.003 · newest: 0.004 · change: +0.000

Weakness classification (CWE)

Public proof-of-concept exploits

References

Frequently asked questions

What is CVE-2025-51606?
CVE-2025-51606 is a high-severity vulnerability in N/a, classified under Use of Hard-coded Credentials. CVSS score: 8.8/10. Published 2025-08-21.
How severe is CVE-2025-51606?
High severity. CVSS v3 base score is 8.8 out of 10.
Is CVE-2025-51606 known to be exploited?
2 public proof-of-concept repositories are indexed. Not currently listed in the CISA KEV catalog.