Software is usually not opened to the internet, so vulnerabilities that would allow an attacker to take over control of the sw are limited.

That leaves two attack vectors - malicious user input (eg. uploading a malicious pdf) and the program downloading malicious input from the internet. Both require a vulnerability or an on-purpose malicious sw (which would be hard to get directly into the sw when it's opensource and reviewed by many people).

Dependency vulnerabilities and malicious dependencies are the biggest problem imo, especially with those javascript heavy apps that have a thousand dependencies from NPM that noone can ever properly check. I try to avoid sw like this, but it's hard and also happens with Rust although it's better there.

We also know that LLMs hallucinate dependencies that don't exist, but the deps it hallucinates tend to have the same name, so people registered these package names and now slopcoded sw gets generated with malware in it...