CVE-2026-7858 remediation guide
Dassault Systèmes Teamwork Cloud - Standard Edition, Teamwork Cloud - Business Edition, Teamwork Cloud - Business Pro Edition
A Deserialization of Untrusted Data vulnerability affecting Teamwork Cloud from No Magic Release 2022x through No Magic Release 2026x and Magic Collaboration Studio from CATIA Magic Release 2022x through CATIA Magic Release 2026x could lead to an unauthenticated remote code execution.
A verified fixed-version field is not available. Use the linked NVD and supporting references, then confirm the vendor-supported path before changing production systems.
Identify the affected asset
Confirm whether Dassault Systèmes Teamwork Cloud - Standard Edition, Teamwork Cloud - Business Edition, Teamwork Cloud - Business Pro Edition is installed, record the deployed version and installation path, and identify exposed interfaces.
- Record the product name, package or appliance identifier, and installed version.
- Identify internet-facing, administrative, API, and internal access paths.
- Preserve the pre-change configuration and relevant service logs.
Validate the affected-version match
Compare the deployed version with the affected range: >= No Magic Release 2022x Golden <= No Magic Release 2022x Refresh2 HF3, >= No Magic Release 2024x Golden <= No Magic Release 2024x Refresh3 HF1, >= No Magic Release 2026x Golden <= No Magic Release 2026x Golden HF2, >= CATIA Magic Release 2022x Golden <= CATIA Magic Release 2022x Refresh2 HF3, >= CATIA Magic Release 2024x Golden <= CATIA Magic Release 2024x Refresh3 HF1, >= CATIA Magic Release 2026x Golden <= CATIA Magic Release 2026x Golden HF2. Treat incomplete inventory results as unresolved.
Prioritize with independent signals
The CVSS severity warrants an early asset and exposure review. Combine this signal with asset criticality, exposure, compensating controls, and business impact.
Apply supported remediation
Follow the vendor advisory or supported update path. Current fixed-version status: No verified fixed-version field is available yet. Preserve configuration and rollback material before change.
Verify the result
Confirm the resulting version, service health, authentication and access paths, monitoring coverage, and relevant security logs.
- Confirm the expected version and package state.
- Run a functional health check for critical service paths.
- Review authentication, error, application, and security monitoring logs.
- Reassess exposure if the supported fix cannot be applied.
Operational boundary
This page does not replace the vendor advisory, support contract, change-management process, or recovery plan. Do not infer that an asset is unaffected from an incomplete inventory query or a missing fixed-version field.