That's not completely correct actually (haven't looked at the bug though).
dnsmasq by default binds on 0.0.0.0 which will include (127.0.0.2), so even if Network Manager moves to using 127.0.0.2, which I believe is a good idea, it should still ship a dnsmasq.d config file containing "bind-interfaces" so that dnsmasq only binds 127.0.0.1 on the loopback interface instead of all the IPs.
That's not completely correct actually (haven't looked at the bug though).
dnsmasq by default binds on 0.0.0.0 which will include (127.0.0.2), so even if Network Manager moves to using 127.0.0.2, which I believe is a good idea, it should still ship a dnsmasq.d config file containing "bind-interfaces" so that dnsmasq only binds 127.0.0.1 on the loopback interface instead of all the IPs.