CVE-2025-63721

CVE-2025-63721 is a high-severity vulnerability in Hummerrisk with a CVSS 3.x base score of 8.8. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low. The underlying weakness is classified as CWE-502.

Key facts

Description

HummerRisk thru v1.5.0 is using a vulnerable Snakeyaml component, allowing attackers with normal user privileges to hit the /rule/add API and thereby achieve RCE and take over the server.

Frequently asked questions

What is CVE-2025-63721?
HummerRisk thru v1.5.0 is using a vulnerable Snakeyaml component, allowing attackers with normal user privileges to hit the /rule/add API and thereby achieve RCE and take over the server.
How severe is CVE-2025-63721?
CVE-2025-63721 has a CVSS 3.x base score of 8.8, rated high severity. It is exploitable over network with low attack complexity, requires low privileges and no user interaction. Impact on confidentiality is high, integrity high, and availability high.
Is CVE-2025-63721 being actively exploited?
It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 0% (34th percentile), an estimate of the probability of exploitation in the next 30 days.
What products are affected by CVE-2025-63721?
CVE-2025-63721 affects Hummerrisk. See the affected-products list for the exact vulnerable versions.
How do I fix CVE-2025-63721?
Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its high severity, prioritise patching exposed systems.
Does CVE-2025-63721 have an EU (EUVD) identifier?
Yes. CVE-2025-63721 is tracked in the ENISA EU Vulnerability Database (EUVD) as EUVD-2025-201789.
When was CVE-2025-63721 published?
CVE-2025-63721 was published on 2025-12-08 and last updated on 2026-06-17.

References

Affected products (1)

More vulnerabilities in Hummerrisk

All CVEs affecting Hummerrisk →

Other CWE-502 (Deserialization of Untrusted Data) vulnerabilities

Browse all CWE-502 (Deserialization of Untrusted Data) vulnerabilities →