CVE-2025-10220
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedUse of Unmaintained Third Party Components (CWE-1104) in the NuGet dependency components in AxxonSoft Axxon One VMS 2.0.0 through 2.0.4 on Windows allows a remote attacker to execute arbitrary code or bypass security features via exploitation of vulnerable third-party packages such as Google.Protobuf, DynamicData, System.Runtime.CompilerServices.Unsafe, and others.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceAxxonSoft Axxon One VMS versions 2.0.0-2.0.4 contain unmaintained and vulnerable NuGet packages (Google.Protobuf, DynamicData, System.Runtime.CompilerServices.Unsafe, and others) that can be exploited by remote attackers for arbitrary code execution or security feature bypass.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data>= 2.0.0, <= 2.0.4CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify if Axxon One VMS is installedLook for Axxon One in installed programs - check Windows Programs and Features, or look for Axxon One installation directory (commonly in C:\Program Files\AxxonSoft\ or C:\Program Files (x86)\AxxonSoft\)Affected if Axxon One VMS software is found on the system
-
Determine installed Axxon One versionRight-click the Axxon One application icon, select Properties, and check the Details tab for Version information; or check the version in Add/Remove ProgramsAffected if The displayed version falls within the range 2.0.0 to 2.0.4 inclusive
-
Confirm vulnerable NuGet packages are presentInspect the Axxon One installation folder for NuGet package DLL files, specifically looking for Google.Protobuf.dll, DynamicData.dll, System.Runtime.CompilerServices.Unsafe.dll, or check any dependency documentation if availableAffected if These NuGet DLL files exist in the installation directory and the version in step 2 is 2.0.0-2.0.4
-
Check if Axxon One server is network-exposedVerify if the Axxon One server service is listening on network ports (common ports: 8080, 8443, or configured service ports) using netstat or by checking if the server component is running and accessible from networkAffected if The Axxon One server is running and accessible over the network while version is 2.0.0-2.0.4
The environment is affected if Axxon One VMS version 2.0.0, 2.0.1, 2.0.2, 2.0.3, or 2.0.4 is installed and the vulnerable NuGet packages are present in the installation.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataUpdate all vulnerable NuGet dependencies to their latest patched versions, or upgrade to a newer version of AxxonSoft Axxon One VMS that addresses these supply chain vulnerabilities.
- Consultation6.0 h
- Implementation12.0 h
- Testing10.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $8,928.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-10220 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-10220 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data