CVE-2025-51606
hippo4j 1.0.0 to 1.5.0, uses a hard-coded secret key in its JWT …
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.
What to do now
- Check your exposureFind out whether the affected software runs anywhere in your environment, including systems of suppliers.
- UpdateInstall the version in which the vendor fixed the vulnerability. The references lead to the advisory.
- Set the orderSystems that can be reached from the internet come first, then the rest.
References
- github.com/ShenxiuSec/cve-proofs/blob/main/POC-20250610-01.md
- nvd.nist.gov/vuln/detail/CVE-2025-51606
- github.com/opengoofy/hippo4j/blob/7d78be3cab526501ad876495862f4cec108da2af/threadpool/serv
- github.com/advisories/GHSA-48cg-9c55-j2q7
- nvd.nist.gov/vuln/detail/CVE-2025-51606
- cve.org/CVERecord?id=CVE-2025-51606
Data: CVE list and the NVD. This product uses data from the NVD API but is not endorsed or certified by the NVD.