{"answers":{"affected":"2 open source packages ship an affected version, including cn.hippo4j:hippo4j-core.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-51606 exists.","fix":"No fix has been published for CVE-2025-51606 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-51606 is a high-severity vulnerability in n/a, published on 21 Aug 2025. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2025-51606 and fix it if it is affected.\n\nWhat it is: CVE-2025-51606 is a high-severity vulnerability in n/a, published on 21 Aug 2025. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-51606 exists.\n\nAffected packages and fixed versions:\n- cn.hippo4j:hippo4j-core (Maven): affected from 1.0.0 up to 1.5.0; no fix listed\n- cn.hippo4j:hippo4j-core (Maven): affected from 1.0.0 up to 1.5.0; no fix listed\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2025-51606/ (Markdown: https://insights.sbomify.com/CVE-2025-51606/index.md)","id":"CVE-2025-51606","markdown":"https://insights.sbomify.com/CVE-2025-51606/index.md","name":"CVE-2025-51606","record":{"aliases":["GHSA-48cg-9c55-j2q7"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["account_takeover","privilege_escalation"],"network_reachable":"yes","non_default_config":false,"product_category":"Java JWT library","requires_auth":"low_privilege","summary":"Attackers can forge valid JWTs using a hard-coded secret key to impersonate any user, including administrators, in applications using this library.","user_interaction":"not_required","vuln_class":"hardcoded_credentials"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[],"cvss":{"score":8.8,"severity":"high","source":"cisa-adp","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-798","name":"Use of Hard-coded Credentials"}],"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.","ecosystems":["Maven"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":false,"headline":"hippo4j Includes Hard Coded Secret Key in JWT Creation","id":"CVE-2025-51606","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Maven","product":null,"products":[],"type":"hardcoded_credentials","year":"2025"},"n_packages":2,"n_references":1,"next":{"headline":"Null dereference in n/a","id":"CVE-2025-51619"},"packages":[{"ecosystem":"Maven","fixed":[],"introduced":["1.0.0"],"last_affected":["1.5.0"],"package":"cn.hippo4j:hippo4j-core","purl":null,"source":"GHSA-48cg-9c55-j2q7"},{"ecosystem":"Maven","fixed":[],"introduced":["1.0.0"],"last_affected":["1.5.0"],"package":"cn.hippo4j:hippo4j-core","purl":"pkg:maven/cn.hippo4j/hippo4j-core","source":"GHSA-48cg-9c55-j2q7"}],"prev":{"headline":"Security feature bypass in n/a","id":"CVE-2025-51605"},"products":["n/a"],"published":"2025-08-21","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"poc","technical_impact":"total"},"state":"PUBLISHED","updated":"2025-08-22","vendors":["n/a"]},"summary":"Attackers can forge valid JWTs using a hard-coded secret key to impersonate any user, including administrators, in applications using this library.","url":"https://insights.sbomify.com/CVE-2025-51606/"}