ZDF
Sign inSign up

Vulnerabilities

Vulnerability · CVE-2025-51606

hippo4j 1.0.0 to 1.5.0, uses a hard-coded secret key in its JWT (JSON Web Token) creation.

Published Aug 21, 2025 · catalog updated Aug 22, 2025 · hippo4j 1.0.0 to 1.5.0,

Check if you run it

No confirmed exploitation is on record for CVE-2025-51606. EPSS is 0.35%. Act only if a listed version of hippo4j 1.0.0 to 1.5.0, is installed.

Gaps on this record

  • The stored product name is a package slug. The name on this page is taken from the title (hippo4j 1.0.0 to 1.5.0,).
  • No version range is stored. A customer cannot check an installed version against this record.
  • No vendor fix or required action is stored. Compare the linked advisory before you change production.
Severity
High8.8
Known exploitation
Not in CISA/VulnCheck KEV
EPSS
0.35%
Remediation
Vendor / distro source
Affected products
vendor n/a n/a n/a

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.

Are you affected?

Enter the version you run. The result uses only the ranges stored on this record.

The check returns affected, not affected, or incomplete. It does not guess a version that is missing from the record.

  • vendor n/a n/a n/an/a

How to fix CVE-2025-51606

What to do

Three questions, each answered from this record only. Confirm the vendor advisory before you patch.

Should you patch?

No confirmed exploitation is on record for CVE-2025-51606. EPSS is 0.35%. Act only if a listed version of hippo4j 1.0.0 to 1.5.0, is installed.

Which versions are affected?

Compare what you have installed with n/a n/a n/a n/a. Compare the installed version with the linked vendor advisory before you change production.

What should an analyst verify?

No weakness class is stored. EPSS 0.35%. There is no CISA KEV listing. No Exploit-DB or Metasploit reference is linked. Use the source links for the original advisory.

Code

The project this record applies to. Exploit listings stay in References.

Timeline

Detection, updates, and resolution for this record.

  1. Aug 21, 2025 · EUVD

    Detected

    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.

  2. Aug 22, 2025 · EUVD

    Updated

    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.

Sources

  • CVE.orgVulnerability recordCVE-2025-51606

    Official CVE identifier

    cve.org
  • FIRST EPSSExploitation probabilityCVE-2025-51606

    30-day exploitation probability 0.35%

    first.org
  • EUVDVulnerability recordEUVD-2025-25521

    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 p

    euvd.enisa.europa.eu

References

Freshness

Last verified in this catalog Oct 23, 2026. Significant claims (KEV, EPSS, CVSS, affected ranges) come from the source rows above — open the original publisher for the authoritative advisory.