Back in the day Haiku didn't do the hostname check in its TLS code. Browser, command line tools, package updates, everything just ignored hostnames - so it would have apparently secure HTTPS fetches, but under the hood if you can interpose and hand Haiku a certificate you got for say your personal blog from Let's Encrypt, that checks out fine even though the name doesn't match - so you could impersonate Haiku's update servers. They did, after many years, fix that particular issue, but lots of similar bugs remain, you're primarily hoping nobody tries anything.
Who cares. OS stuff is easy to replace. The real problem is that it can also destroy any user data... just like every binary on Linux or Windows.