Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
High, CVSS 8.8

hippo4j Includes Hard Coded Secret Key in JWT Creation

CVE-2025-51606GHSA-48cg-9c55-j2q7

What to do

Vendor response not established. Follow the primary source's mitigation guidance and check back for a fix.

This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.

Add to your agent

Affected packages

  • Maven cn.hippo4j:hippo4j-core

    Affected
    >= 1.0.0, <= 1.5.0
    Fixed in
    no fixed version recorded

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS
8.8 · CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
EPSS
  • CVE-2025-51606: 0.35% estimated exploitation activity in the next 30 days; percentile 29.09 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description

As published by the source; long descriptions are shortened.

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.

Dates and revisions
Published by the source
Last modified by the source
Source last checked
  1. Revision 1 · created ·

    Published from ghsa record GHSA-48cg-9c55-j2q7

Agent brief

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2025-51606

Advisory: hippo4j Includes Hard Coded Secret Key in JWT Creation
IDs: CVE-2025-51606, GHSA-48cg-9c55-j2q7
Record: https://patchnext.com/advisories/cve-2025-51606 (revision 1, source checked 26 Oct 2026, 16:39 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 8.8)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor response not established. A vendor fix does not mean a deployment is fixed.

## Affected components
- Maven cn.hippo4j:hippo4j-core: affected >= 1.0.0, <= 1.5.0

## Suggested inspection (read-only)
- Maven cn.hippo4j:hippo4j-core: check the installed version with your package manager.

## Supported action
No complete vendor fix is recorded. Follow the primary source's mitigation guidance and check this record again before closing anything.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on cn.hippo4j:hippo4j-core.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-48cg-9c55-j2q7 (GitHub-reviewed advisory GHSA-48cg-9c55-j2q7 lists affected ranges: Maven cn.hippo4j:hippo4j-core >=1.0.0 <=1.5.0)

Commands are suggestions: review each one before running it.

Loading voting…