Version skew is the condition where different systems in the same environment are running different software builds at the same time. It often happens during staged rollouts, when one platform or device group updates before another. In security operations, that mixed state matters because “patched” does not mean “fully patched” if some endpoints are still on an older build.
Cyber attackers look for version skew because it creates a temporary gap in protection. A flaw fixed on Windows may still exist on Linux or on machines that have not restarted yet, giving an attacker a narrow window to target the weaker subset. Defenders use inventory, build checks, and update compliance monitoring to spot skew quickly, especially for browsers, agents, and other internet-facing software. In practice, version skew is a rollout risk and a detection signal: it shows where exposure may still remain even after a fix is available.