CVE-2025-51606: hippo4j Includes Hard Coded Secret Key in JWT Creation
(updated )
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
- github.com/ShenxiuSec/cve-proofs/blob/main/POC-20250610-01.md
- github.com/advisories/GHSA-48cg-9c55-j2q7
- github.com/opengoofy/hippo4j
- github.com/opengoofy/hippo4j/blob/7d78be3cab526501ad876495862f4cec108da2af/threadpool/server/auth/src/main/java/cn/hippo4j/auth/security/JwtTokenManager.java
- nvd.nist.gov/vuln/detail/CVE-2025-51606
Code Behaviors & Features
Detect and mitigate CVE-2025-51606 with GitLab Dependency Scanning
Secure your software supply chain by verifying that all open source dependencies used in your projects contain no disclosed vulnerabilities. Learn more about Dependency Scanning →