CVE-2025-63721: secrisk · n/a
Affects secriskSource CVE Database V5
Not known to be exploited · CVSS 9.8 Critical : upgrade to 1.5.1 as a priority.
Data as of 26 Oct 2026, 06:26 UTC
- EPSS
- 0.4% chance of exploitation in 30 days – higher than 41% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 1.5.1
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:HExploitation evidence
Disclosed: evidence found.
CVE published 8 Dec 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-26.
What to do
Upgrade k1ng0fic3/secrisk to 1.5.1.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
GitHubk1ng0fic3/secriskpkg:github/k1ng0fic3/secriskOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
1. Immediately restrict network access to the /rule/add API endpoint by implementing strict firewall rules or network segmentation to limit exposure only to trusted users or systems. 2. Implement strong authentication and authorization controls around the API to ensure only fully trusted users can access it. 3. Monitor logs and network traffic for unusual or suspicious activity targeting the /rule/add endpoint, including unexpected YAML payloads or anomalous API calls. 4. Employ runtime application self-protection (RASP) or web application firewalls (WAF) with custom rules to detect and block malicious deserialization attempts. 5. 6. If patching is not immediately possible, consider disabling or limiting the functionality of the /rule/add API temporarily. 7. Conduct thorough security assessments and penetration testing focused on deserialization vulnerabilities within your environment. 8. Educate development and operations teams about the risks of unsafe deserialization and secure coding practices to prevent similar issues in the future.
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.