Evidence-linked product lifecycle intelligenceSUPPORT · SECURITY · RETIREMENT
← Search results
CVE-LINKED INVENTORY7 SECURITY RECORDS

AxxonSoft

AxxonOne C-Werk

Affected and fixed version statements observed in the public BlackTree CVE catalogue. These statements describe vulnerability scope, not publisher support entitlement.

Lifecycle evidence status

This identity is present in BlackTree CVE records, but no product-specific publisher support or retirement history is currently registered in Lifecycle.

A missing support date does not mean the product is supported. CVE publication dates and affected-version ranges must not be interpreted as EOL dates.

CVE-observed version history

CVEPublishedAffected versionsFixed version informationPublisher evidence
CVE-2025-10227 10 Sep 2025 AxxonOne C-Werk: ≤ 2.0.8 Upgrade to Axxon One (C-Werk) 2.0.8 or later, where AES-256 encryption of object archive is implemented. Update reference ↗
CVE-2025-10226 10 Sep 2025 ≤ 2.0.8 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2025-10225 10 Sep 2025 AxxonOne C-Werk: ≤ 2.0.6 Upgrade to Axxon One (C-Werk) with OpenSSL 3.0.13 or later, where session key management logic was refactored to avoid unsafe memory reallocations. Update reference ↗
CVE-2025-10224 10 Sep 2025 ≤ 2.0.2 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2025-10223 10 Sep 2025 AxxonOne C-Werk: ≤ 2.0.3 Upgrade to 2.0.3 or later, where Web UI enforces forced logout when role changes occur. Update reference ↗
CVE-2025-10222 10 Sep 2025 AxxonOne C-Werk: 2.0.0 ≤ 2.0.1 Upgrade to Axxon One 2.0.2 (C-Werk) or later, where the diagnostic export tool has been refactored to exclude licensing-related sensitive variables. Update reference ↗
CVE-2025-10220 10 Sep 2025 AxxonOne C-Werk: 2.0.0 ≤ 2.0.4 Update to Axxon One VMS 2.0.5 or later, where vulnerable NuGet dependencies have been upgraded to secure versions (e.g., Google.Protobuf 3.31.0, DynamicData 9.3.2, System.Runtime.CompilerServices.Unsafe 6.1.2). Update reference ↗

How this record is maintained

The CVE inventory is reconciled automatically from cve.blacktree.nl. Exact identity matches link to existing Lifecycle product or package histories. Unmatched products stay in a prioritised publisher-source research queue, and Lifecycle marks the date gap instead of inferring a support boundary from vulnerability data.