hippo4j 1.0.0 to 1.5.0, uses a hard-coded secret key in its JWT (JSON Web Token) creation.
Key facts
- Attack vector
- Network
- Privileges required
- Low
- User interaction
- None
- Attack complexity
- Low
- Impact type
- Security bypass
- Confidentiality · integrity · availability
- High · High · High
- Fix status
- No fix listed
Attack profile from CVSS 3.1 · CISA ADP. Fix status from CNA and GitHub. Impact type from CWE-798.
Summary
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.
Why it matters now
SSVC decision points
CISA ADP · SSVC 2.0.3
- Exploitation
- Poc
- Automatable
- No
- Technical impact
- Total
The decision (Track, Attend, Act) also depends on your mission and well-being impact; see CISA's SSVC guide.
Affected products
| Vendor | Product | Affected versions | Fixed in | Status | Source |
|---|---|---|---|---|---|
| — | — | all versions | — | No fix listed | CNA |
| — | cn.hippo4j:hippo4j-core (Maven) | 1.0.0 – 1.5.0 | — | No fix listed | GHSA-48cg-9c55-j2q7 |
- — Vendor— Affected all versions Fixed in — No fix listed CNA
- cn.hippo4j:hippo4j-core (Maven) Vendor— Affected 1.0.0 – 1.5.0 Fixed in — No fix listed GHSA-48cg-9c55-j2q7
Remediation
No fixed version listed by the sources yet.
Timeline
- 2026-10-02 Threatist record created from CVE-2025-51606
- 2026-10-03 Alias added: GHSA-48cg-9c55-j2q7
References
Sources
- CVE-2025-51606 · CVE Program
- CVE-2025-51606 · NVD
- FIRST EPSS
- GHSA-48cg-9c55-j2q7 · GitHub Advisory Database · CC BY 4.0
This product uses the NVD API but is not endorsed or certified by the NVD. Sources and licences