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.
No analysis available yet.
Remediation
No remediation available yet.
Tracking
Sign in to view the affected projects.
Advisories
| Source | ID | Title |
|---|---|---|
EUVD |
EUVD-2025-25521 | hippo4j Includes Hard Coded Secret Key in JWT Creation |
Github GHSA |
GHSA-48cg-9c55-j2q7 | hippo4j Includes Hard Coded Secret Key in JWT Creation |
References
History
Fri, 22 Aug 2025 14:15:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Weaknesses | CWE-798 | |
| Metrics |
cvssV3_1
|
Thu, 21 Aug 2025 20:45:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| 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. | |
| References |
|
Subscriptions
No data.
Status: PUBLISHED
Assigner: mitre
Published:
Updated: 2025-08-22T13:56:21.230Z
Reserved: 2025-06-16T00:00:00.000Z
Link: CVE-2025-51606
Updated: 2025-08-22T13:55:54.861Z
Status : Deferred
Published: 2025-08-21T21:15:35.650
Modified: 2026-04-15T00:35:42.020
Link: CVE-2025-51606
No data.
OpenCVE Enrichment
No data.
Weaknesses
EUVD
Github GHSA