AI might have found thousands of possible attack vectors, but the patches don't need to take anything offline. Engineering is understanding how things and systems work, operate, and using skill, and knowledge to maintain or better those things / systems. Engineering is not, “AI told us we have an issue, let's push wildly untested or under tested code / fixes into a system we don't understand, and can't manage.”.
The old saying: “If it's not broke, don't fix it.”, is showing why it was always bad advice! It's not broke now, but in 5, 10, 15+ years, will it be broke, and do we need better management and oversight of the system? Think about your favourite framework or language, if it's EOL, do you keep using it? When does an EOL status concern you? Angular, for instance, is in v22, if you're running v18, are you going to push so you're on v20, or v21? If you're on v15, would update?
You're seeing the excuses pile up, X was decades old, not designed for our modern systems, and workflows, and now those AI patches which weren't reviewed, are the bull in a china shop. It wasn't broke, no one took the time to understand, improve, and polish the system, and now it's not only broken, it's stuck in a state it's constantly failing and being band aided together with duct tape, and prayer.