Before anybody starts to get too excited about the OpenVPN vulnerabilities Microsoft are doing a publicity tour for, they need authentication and are client side - so nothing particularly risky.
To be clear about this, there are 4 CVEs - 3 are for the OpenVPN *client* on Windows, and 1 is for the Android client.
I don’t know why the MS blog post is going on about binaries on millions of routers, as those are the OpenVPN *server* - which is different.
The RCE one here is against the client, not server, and needs you to be on a VPN with a compromised host doing SMB/RPC traffic back to your system (you have Windows Firewall, though) and know creds on your system.
It’s valid research and people should apply updates as usual, ie no panic.
It would be good if Microsoft could turn their researchers attention to their own products, where gaping holes exist in things like legacy (still enabled) components in Windows OS, Office etc etc.
Or maybe just look at the long list of known issues in SmartScreen, DWM etc etc rather than waiting for Kaspersky to tell them after people have already been owned.