Authenticated code execution via unsafe YAML deserialization
Published Dec 8, 2025 · Updated Dec 11, 2025
Insecure deserialization in HummerRisk 1.5.0 and earlier allows remote authenticated users to execute code via /rule/add. The endpoint deserializes attacker-supplied YAML with bundled SnakeYAML 1.33 without restricting constructed types, enabling arbitrary file writes. A normal user account is sufficient, and overwriting /etc/crontab yields command execution with control of the server.
Summary
What happened
Insecure deserialization in HummerRisk 1.5.0 and earlier allows remote authenticated users to execute code via /rule/add. The endpoint deserializes attacker-supplied YAML with bundled SnakeYAML 1.33 without restricting constructed types, enabling arbitrary file writes. A normal user account is sufficient, and overwriting /etc/crontab yields command execution with control of the server.
The record
- CVE
- CVE-2025-63721
- Published
- Dec 8, 2025
- Updated
- Dec 11, 2025
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-502, T1190
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Dec 8, 2025CVE publishedPublication date reported by the CVE source.
- Dec 11, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
- CVE-2025-63721 proof of conceptfunctional · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo