Unless your job description specifically says, "Mitigate security vulnerabilities in code before deploying to production.", this is not your job. Your job is to do what your boss tells you to do
This depends on your company, the organizational structure, and what your job actually is.
If your boss asks you to do something that you can clearly demonstrate is illegal or against explicit company policy, and you have it in writing from the boss confirming they know about it, and to ignore the company's own policies ---- without the proper approvals from higher levels of management, then it might be time to visit HR, in order to report the policy violation so the HR staff can investigate/mediate.
Some companies may very well have policies that say "No employee may deploy new software with any known security problems to a public-facing server."
Frankly, I don't see what business a Senior Architect has doing deploying any code supplied by another department.
Deploying software is clearly a system admin job, not a software developer job.
If dealing with the security issues, or approving the release is not your job --- then you should not be standing in your team's way, or your boss' way.
You might want to request a 4-way meeting with your boss, someone in QA, and someone in security, about the issue,
and make sure the issues are in the relevant departments' radars, so that they will be addressed.