I figured it out, it looks like an issue upstream which is being handled by the Vagrant team, with a manual workaround available