Sources
Does this affect the applications or just bridge?
Uncertain if an EOL 18 months old QT is vulnerable enough to merit stop using proton-bridge until it has up-to-date QT. Regardless, this is just disappointing to see from Proton.
I have often brushed off their half-baked, inconsistent features between platforms as, them being a small team that can’t do everything at once. Keeping up with dependencies is pretty simple with Github and bots, let a bot make PR’s, review and update.
At bare minimum they should use LTS release of QT to get security updates if features are not needed.
This type of security negligence is how software become vulnerable for exploitation.
Update: Proton Mail Bridge can now run on QT 6.8 in version 3.15.0