CVE-2025-51606

Published Aug 21, 2025 CVSS 3.1 · 8.8 High EPSS < 1% KEV · Not listed
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.

Remediation

No solution or workaround provided in the CVE record

Tracking

Sign in to view the affected projects.

Advisories

Source ID Title
EUVD EUVD EUVD-2025-25521 hippo4j Includes Hard Coded Secret Key in JWT Creation
Github GHSA Github GHSA GHSA-48cg-9c55-j2q7 hippo4j Includes Hard Coded Secret Key in JWT Creation
History
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'}

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

Subscriptions

No data.

Weaknesses

Sources

Status
PUBLISHED
Assigner
mitre
Published
Updated
Aug 22, 2025, 1:56 PM
Reserved
Jun 16, 2025, 12:00 AM
Status
Deferred
Published
Aug 21, 2025, 9:15 PM
Modified
Jun 17, 2026, 9:35 AM