CVE-2025-51606 Details
Description
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.
A vulnerability exists in hippo4j versions 1.0.0 through 1.5.0, where a hard-coded secret key is used in the creation of JSON Web Tokens (JWTs). This flaw enables attackers with access to the source code or compiled binary to forge valid access tokens, impersonating any user, including those with privileged roles such as 'admin'. The issue poses a critical security risk in environments where JWTs are relied upon for authentication and authorization.
Metrics
CVSS 4.0 Severity and Vector Strings:
CVSS 3.x Severity and Vector Strings:
No data available for CVSS Version 2.0 on this CVE.
Volerion
Assessed Aug 21, 2025CISA-ADP
Assessed Aug 22, 2025References to Advisories, Solutions, and Tools
By selecting these links, you will be leaving this site. These are references gathered from the official CVE record and are not endorsed by Volerion.
| URL | Source(s) | Tag(s) |
|---|---|---|
| https://github.com/ShenxiuSec/cve-proofs/blob/main/POC-20250610-01.md | [email protected] | ExploitTechnical Analysis |
Weakness Enumeration
| CWE-ID | CWE Name | Source |
|---|---|---|
| CWE-798 | Use of Hard-coded Credentials | CISA-ADP |
Affected Products
| Product | Versions |
|---|---|
| hippo4j | >= 1.0.0, <= 1.5.0 (semver) |
CPE
Remediation
| |
Change History
4 change records found show changes
| Date | Action | Recorded By |
|---|---|---|
| Jun 17, 2026 | CVE Modified | [email protected] |
| Jun 17, 2026 | CVE Modified | CISA-ADP |
| Aug 22, 2025 | CVE Modified | CISA-ADP |
| Aug 21, 2025 | New CVE Received | [email protected] |
Volerion