The fact that the website hasn’t been updated since 2020 and still has an open CVE shines the light on Flatpak’s attention to security.
Regarding point 3, if that’s true, then why are all of the most-dowloaded packages on Flathub mislabelled as ‘sandboxed’ when they have full write access to a user’s home directory? That isn’t a sandbox.
Flatpak currently has a 7.2 vulnerability that has gone unaddressed since 2017. The maximum vulnerability rating is a 9, so this is quite major.
The fact that the website hasn’t been updated since 2020 and still has an open CVE shines the light on Flatpak’s attention to security.
Regarding point 3, if that’s true, then why are all of the most-dowloaded packages on Flathub mislabelled as ‘sandboxed’ when they have full write access to a user’s home directory? That isn’t a sandbox.
Flatpak currently has a 7.2 vulnerability that has gone unaddressed since 2017. The maximum vulnerability rating is a 9, so this is quite major.
https://www.cvedetails.com/vulnerability-list.php?vendor_id=16613&product_id=&version_id=&page=1&hasexp=0&opdos=0&opec=0&opov=0&opcsrf=0&opgpriv=0&opsqli=0&opxss=0&opdirt=0&opmemc=0&ophttprs=0&opbyp=0&opfileinc=0&opginf=0&cvssscoremin=3&cvssscoremax=0&year=0&month=0&cweid=0&order=1&trc=9&sha=14fe55bfe41eaaaaca8e742bde18bc6938f88a3e
Maybe you should have read the entries in the link you posted
Text about the 7.2 vulnerability from 2017:
That version was tagged in git on July 20th, 2017