Does CMake/make have the ability to make my Linux operating system unstable?

30 years ago, I've started C++. Mostly under DOS, Windows 3.1 and 95. I've wrote some for 10 years. Then Java replaced it at work, for about 20 years. Now C++ in coming back in the front of the scene. I'm enjoying it but the whole environment has changed. It's with stdlib that I have to work now, and learn some changes that came from C++ 98 where I left it, up to C++ 23 where it is now. My main troubles, however, aren't with the language itself. But the CMake scripts and their complexities that make builds complex to understand, and sometimes: to perform. Generating make script itself, a lot of sub projects, sometimes being helped by Conan or another tool. It's difficult to figure all it can do. But what is making me asking a question in this Unix/Linux S.E. and not StackOverflow, is that I had to generate and adapt a somewhat long C++ project (a generation coming from OpenApi generator for pistache server) few months ago. During some changes I was attempting, I went on trouble with a gir1 library that was generated by an underlying sub project, for a purpose it only knows, whose .so.1 wasn't able to link to .so or something like that, and where I was figuring that the underlying make scripts could be able/willing to put their .so binary to /usr/local/bin or to some place where it could attempt to replace the binary currently used by my Debian 12. Or that, if I dared attempting to run my CMake command with a sudo, this could happen. Are my fears true? May I put my OS definitively in trouble with a bad compilation, replacing a genuine component by a dev one? Does such risk exist and, in general, for any project involving make builder, I have to be careful, Or is there some kind of protection on my operating system that prevent this absolutely?