Vulnerabilities in pkg:maven/cn.hippo4j/hippo4j-core

PACKAGE
Advisory Identifier: GHSA-48cg-9c55-j2q7
Share
Advisory Summary

CVE-2025-51606 is a HIGH (CVSS 8.8) hippo4j includes hard coded secret vulnerability (CWE-798: Use of Hard-coded Credentials) affecting Hippo4j core libraries in the Maven ecosystem. The issue involves hippo4j includes hard coded secret key in jwt creation. Remediation is available in the latest vendor maintenance releases.

2 Known Advisory Record(s)
Package Vulnerability Intelligence

pkg:maven/cn.hippo4j/hippo4j-core

2 Known Advisory Record(s)

Vulnerability advisories affecting package pkg:maven/cn.hippo4j/hippo4j-core. Select an advisory below to view technical details or fixes.

Advisory ID CVE / NVD Severity Summary
GHSA-48cg-9c55-j2q7 CVE-2025-51606 HIGH hippo4j Includes Hard Coded Secret Key in JWT Creation
GHSA-xg89-vvwp-9c27 CVE-2023-27095 MODERATE Exposure of Sensitive Information in OpenGoofy Hippo4j

CVE-2025-51606 at a Glance

CVE Identifier CVE-2025-51606
GHSA Identifier GHSA-48cg-9c55-j2q7
Severity HIGH
CVSS v3.1 Base Score 8.8
CWE Classification CWE-798: Use of Hard-coded Credentials
Affected Product Hippo4j core
Package Ecosystem Maven
Published Date
Last Updated

Security Impact

CVSS: 8.8

The security impact metrics below are parsed directly from the CVSS v3.1 vector string (CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H).

Attack Vector Network (AV:N)
Attack Complexity Low (AC:L)
Privileges Required Low (PR:L)
User Interaction None (UI:N)
Scope Unchanged (S:U)
Confidentiality High (C:H)
Integrity High (I:H)
Availability High (A:H)

How to Fix CVE-2025-51606

To remediate this vulnerability, upgrade all affected Hippo4j core dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.

cn.hippo4j:hippo4j-core fixed: Latest secure release 
<dependency>
    <groupId>cn.hippo4j</groupId>
    <artifactId>hippo4j-core</artifactId>
    <version>Latest secure release</version>
</dependency>
Verify Direct and Transitive Dependencies

Run the following command in your project directory to verify that all resolved dependencies use the patched release: 

mvn dependency:tree -Dincludes=cn.hippo4j

How to Check if You Are Affected

To determine whether your Java application is affected by CVE-2025-51606, inspect your build dependencies using the Maven Dependency Plugin:

mvn dependency:tree -Dincludes=cn.hippo4j

Analyze the terminal output to locate any version of Hippo4j core in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than the patched release), your application is affected.

Note: The mvn dependency:tree -Dincludes=cn.hippo4j command inspects the resolved dependency graph declared in your project's POM files; it does not perform automated security scanning or inspect runtime dynamic classpaths. Always verify runtime container classpaths and shaded JARs.

Technical Details

Vulnerability Mechanism & Technical Analysis

This vulnerability is classified under CWE-798: Use of Hard-coded Credentials, where the product contains hard-coded credentials, such as a password or cryptographic key. In Hippo4j core, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.

Source Advisory Statement

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.

CVE-2025-51606 Affected Hippo4j core Versions

1 component(s)
Product / Package Ecosystem Affected Versions Fixed Version
cn.hippo4j:hippo4j-core
maven/cn.hippo4j/hippo4j-core
Maven
≥ 1.0.0
≤ 1.5.0

References

NVD — CVE-2025-51606 NVD
https://nvd.nist.gov/vuln/detail/CVE-2025-51606
Hippo4j core Source Repository REPOSITORY
https://github.com/ShenxiuSec/cve-proofs/blob/main/POC-20250610-01.md
Hippo4j core Source Repository REPOSITORY
https://github.com/opengoofy/hippo4j
Hippo4j core Source Repository REPOSITORY
https://github.com/opengoofy/hippo4j/blob/7d78be3cab526501ad876495862f4cec108da2af/threadpool/server/auth/src/main/java/cn/hippo4j/auth/security/JwtTokenManager.java#L51

Frequently Asked Questions

What is CVE-2025-51606?
CVE-2025-51606 is a security vulnerability in Hippo4j core involving hippo4j Includes Hard Coded Secret Key in JWT Creation under CWE-798: Use of Hard-coded Credentials.
Which Hippo4j core versions are affected?
Affected versions include releases prior to current release patches across affected packages: cn.hippo4j:hippo4j-core.
What version fixes CVE-2025-51606?
Upgrading to current release patches (or the latest patched release for your respective branch) resolves the vulnerability.
Is hippo4j-core affected?
Yes, cn.hippo4j:hippo4j-core is affected in releases prior to Latest secure release. Upgrade your dependency to Latest secure release or later.
What is the CVSS score of CVE-2025-51606?
CVE-2025-51606 has a CVSS v3.1 base score of 8.8 (HIGH) with vector string CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H.
What CWE is associated with CVE-2025-51606?
CVE-2025-51606 is classified under CWE-798: Use of Hard-coded Credentials (The product contains hard-coded credentials, such as a password or cryptographic key.).
How can I check Maven dependencies for CVE-2025-51606?
Run the dependency tree command: 'mvn dependency:tree -Dincludes=cn.hippo4j'. This command lists direct and transitive dependencies in your build configuration so you can verify if a vulnerable version is resolved.
Machine-readable OSV JSON OSV v1.5 Schema
Normalized schema output
View Raw JSON 
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-48cg-9c55-j2q7",
  "modified" : "2025-08-22T20:30:13Z",
  "published" : "2025-08-21T21:32:08Z",
  "aliases" : [ "CVE-2025-51606" ],
  "summary" : "hippo4j Includes Hard Coded Secret Key in JWT Creation",
  "details" : "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.",
  "severity" : [ {
    "type" : "CVSS_V3",
    "score" : "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H"
  } ],
  "affected" : [ {
    "package" : {
      "ecosystem" : "Maven",
      "name" : "cn.hippo4j:hippo4j-core"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "1.0.0"
      }, {
        "last_affected" : "1.5.0"
      } ]
    } ]
  } ],
  "references" : [ {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2025-51606"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/ShenxiuSec/cve-proofs/blob/main/POC-20250610-01.md"
  }, {
    "type" : "PACKAGE",
    "url" : "https://github.com/opengoofy/hippo4j"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/opengoofy/hippo4j/blob/7d78be3cab526501ad876495862f4cec108da2af/threadpool/server/auth/src/main/java/cn/hippo4j/auth/security/JwtTokenManager.java#L51"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-798" ],
    "severity" : "HIGH",
    "github_reviewed" : true,
    "github_reviewed_at" : "2025-08-22T20:30:13Z",
    "nvd_published_at" : "2025-08-21T21:15:35Z"
  }
}