CVE-2026-49494 remediation guide
Xcitium (formerly Comodo Security Solutions) Comodo Internet Security, Xcitium Client Security (XCS)
Xcitium Client Security (XCS) before 13.8.2.10019 and Comodo Internet Security (CIS) through 12.3.4.8162 (fix expected by 2026 Q3) contain an integer underflow vulnerability in the firewall driver Inspect.sys that allows remote unauthenticated attackers to crash the system by sending a crafted IPv6 packet with a declared payload length smaller than the sum of its extension-header lengths. The unsigned 64-bit payload-length value underflows to a near-maximal integer, triggering an out-of-bounds read and oversized memcpy in the Windows kernel at DISPATCH_LEVEL, resulting in a blue screen of d...
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 Xcitium (formerly Comodo Security Solutions) Comodo Internet Security, Xcitium Client Security (XCS) 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: <= 12.3.4.8162, < 13.8.2.10019. 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.