Overview
The vulnerability CVE-2025-10220 has been identified in AxxonSoft Axxon One VMS versions 2.0.0 through 2.0.4, a widely used video management software. This vulnerability stems from the use of unmaintained third-party components (CWE-1104) in the software’s NuGet dependency components, and has serious implications for user security. A successful exploitation of this vulnerability could allow a remote attacker to execute arbitrary code or bypass security features, posing a significant threat to the confidentiality, integrity, and availability of user data and systems.
Vulnerability Summary
CVE ID: CVE-2025-10220
Severity: Critical (CVSS 9.8)
Attack Vector: Network
Privileges Required: None
User Interaction: None
Impact: System compromise and potential data leakage
Affected Products
Share secrets securely
Ameeba is private infrastructure for communication and sensitive work built on encrypted identity instead of exposed corporate identity systems.
Passwords, credentials, confidential files, screenshots, internal discussions, sensitive AI context, and private coordination should not become exposed across ordinary communication platforms.
- • Encrypted identity
- • Private Spaces for organizations and teams
- • End-to-end encrypted chat, calls, files, and notes
- • Sensitive AI work and protected collaboration
- • Built for information that cannot leak
Our mission is to secure human work alongside AI.
Product | Affected Versions
AxxonSoft Axxon One VMS | 2.0.0 through 2.0.4
How the Exploit Works
The exploit takes advantage of the unmaintained third-party packages used within AxxonSoft’s NuGet dependency components, including Google.Protobuf, DynamicData, System.Runtime.CompilerServices.Unsafe, and others. An attacker can exploit these vulnerable third-party packages to inject and execute arbitrary code on the system running the software, or manipulate the system to bypass inherent security features. This exploit can be performed remotely, meaning an attacker does not need physical access to the system to carry out the attack.
Conceptual Example Code
The following is a conceptual example of how the vulnerability might be exploited. In this scenario, an attacker sends a malicious payload via an HTTP POST request to a vulnerable endpoint, which could potentially allow the attacker to execute arbitrary code or bypass security features.
POST /vulnerable/endpoint HTTP/1.1
Host: target.example.com
Content-Type: application/json
{ "malicious_payload": "exploit_specific_code" }In this example, “exploit_specific_code” would be substituted with the actual malicious code tailored to exploit the specific vulnerable third-party package. This type of attack requires a deep understanding of the vulnerable packages and how they interact with the rest of the system.
Mitigation and Prevention
Users of the affected AxxonSoft Axxon One VMS software versions are strongly advised to apply the vendor patch immediately to fix this vulnerability. In the absence of a patch, a Web Application Firewall (WAF) or Intrusion Detection System (IDS) can be used as temporary mitigation to help detect or block exploit attempts. However, these are not permanent solutions and a patch should be applied as soon as it becomes available to ensure the security of the system.