CVE-2025-51606 - CVE House
Back to Database
Status published Unknown CVE-2025-51606

hippo4j 1.0.0 to 1.5.0, uses a hard-coded secret key in...

Vulnerability 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.

Impact Analysis

Refer to official advisory for detailed impact metrics.

Remediation

Ensure systems are updated to the latest vendor-supplied patch levels.

THREAT MONITOR

Am I Vulnerable?

Launch our assessment wizard to check if your infrastructure is exposed to • CVE-2025-51606

Credits & Attribution

No credits recorded in the NVD database.

References

More from n/a

View All →
CVE-2025-9910
Versions of the package jsondiffpatch before 0.7.2 are vulnerable to...
Low 2.3
CVE-2025-9802
RemoteClinic profile.php sql injection
Medium 5.1
CVE-2025-9799
Langfuse Webhook promptRouter.ts promptChangeEventSourcing server-side request forgery
Low 2.3
CVE-2025-9775
RemoteClinic edit-my-profile.php unrestricted upload
Medium 6.9
CVE-2025-9774
RemoteClinic edit-patient.php information disclosure
Medium 5.3

Affected Vendor

Affected Software

Unknown
Vulnerable Versions:
Unknown

Timeline

Official Publish: August 21st, 2025
Last Modified: August 22nd, 2025
Added to House: July 22nd, 2026

CVSS Vectors

No vector data available

Weaknesses (CWE)

No CWE data available

MITRE ATT&CK TTPs

No associated TTPs found for this vulnerability.