I'm not quite sure what benefits dynamic linking is supposed to offer by way of security over static, other than when you upgrade a library due to a security weakness you don't have to relink everything.
Static linking would protect against attacks on linkers but dynamic linking offers so many non-security benefits that it's hard to ignore.
Having said that, I always keep a statically compiled busybox on any Linux host I run in case something goes wrong with glibc. Too many bad memories from broken RedHat upgrades from years back.
I just keep a live CD/USB on hand. A lot easier, and it gives the benefit of a graphical boot that can even access the internet to download further fixes.
But I agree, live distros have saved my life (or at least my data) on a number of occasions!
having 20 random-version-bundled copies of libxml2 for example would make upgrading it a massive pain.
i think this actually a better example of setuid binaries burning you more so than dynamic linkers.
Botan is a cryptographic library, it is on version 1.8.10, however its library is at 1.8.2, which means if the application was compiled against version 1.8.3 it will work just as well with 1.8.10 as it would with 1.8.2 as none of the binary interface has changed.
Also many fixes DON'T involve breaking the ABI, generally it is a fix within a function so the function return type, name and parameters stay the same as such the ABI is not broken as that is all that matters, you can change the function all you want so long as it still returns the same thing as before.
Yes it works very well in practice, and makes development much nicer, as libraries around my product can easily be updated without me having to update anything.
Not sure what the Gentoo guys are doing differently.
Perhaps upstream is doing some magic. Like applying patches to the distros official version and making sure it's compatible before distributing a binary.