Machine-written summary
Summary written by Claude Haiku from the source advisory. Not reviewed by a person.
Versions 1.0.0 through 1.5.0 of hippo4j (cn.hippo4j:hippo4j-core) use a hard-coded secret key when creating JSON Web Tokens. An attacker who can read the source code or compiled binary can forge valid access tokens and impersonate any user, including admin accounts. No fixed version is listed.
Not analysed yet
We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.
Severity and exploitation
| Score | Rating | CVSS | Vector | Source |
|---|---|---|---|---|
| 8.8 | High | 3.1 | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H | GitHub Advisory Database |
- CISA KEV Not listed.
- EPSS 0.0039, the 33rd percentile, on 13 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.
Timeline
- 31 Oct 2026, 15:10 UTC First seen by agentprime
- 31 Oct 2026, 15:10 UTC Confirmed by OSV
Sources
- GitHub Advisory Database: GHSA-48cg-9c55-j2q7
- OSV: GHSA-48cg-9c55-j2q7
- nvd.nist.gov/vuln/detail/CVE-2025-51606
- github.com/ShenxiuSec/cve-proofs/blob/main/POC-20250610-01.md
- github.com/opengoofy/hippo4j
- github.com/opengoofy/hippo4j/blob/7d78be3cab526501ad876495862f4cec108da2af/threadpool/server/auth/src/main/java/cn/hippo4j/auth/security/JwtTokenManager.java#L51