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.
History

Fri, 22 Aug 2025 14:15:00 +0000

Type Values Removed Values Added
Weaknesses CWE-798
Metrics cvssV3_1

{'score': 8.8, 'vector': 'CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H'}

ssvc

{'options': {'Automatable': 'no', 'Exploitation': 'poc', 'Technical Impact': 'total'}, 'version': '2.0.3'}


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

cve-icon MITRE

Status: PUBLISHED

Assigner: mitre

Published:

Updated: 2025-08-22T13:56:21.230Z

Reserved: 2025-06-16T00:00:00.000Z

Link: CVE-2025-51606

cve-icon Vulnrichment

Updated: 2025-08-22T13:55:54.861Z

cve-icon NVD

Status : Awaiting Analysis

Published: 2025-08-21T21:15:35.650

Modified: 2025-08-22T18:08:51.663

Link: CVE-2025-51606

cve-icon Redhat

No data.

cve-icon OpenCVE Enrichment

No data.