The problem is solved. It was a configuration/user error from my side.

I added a category later on and did not remove the guest-privileges from this category. And coincidentally this was the category, I experienced the reported behaviour with. After fixing the permissions, all is fine now.

Thread may be marked solved/deleted.