This is likely caused by one of two common issues with how this specific CVE is detected:
Version String Mismatch: The vulnerability feed specifies the patched version as 16.0.35907.0. If the Windows registry or package manager reports your installed version as 16.0.35907 (without the trailing .0), Wazuh's strict version matching may flag it as a false positive.
Lingering Binaries (SSMS): If VSTA was installed as a bundled component of SQL Server Management Studio (SSMS), updating SSMS does not automatically patch the underlying VSTA binaries. Vulnerable files may still exist on disk and be detected by Syscollector.
To verify, check the Wazuh Dashboard (Modules > Inventory > Packages) for that specific VM to see the exact version string and installation path being reported.
If it is just missing the .0, it is a false positive. If it points to older files, you will need to download and run the standalone VSTA 2019 patch directly from Microsoft to overwrite the lingering binaries.