Hi Silvio,
this log comes from the suricata default rules. Prio 3 says in this case no connection was blocked. But it shows that s.th. went wrong/ some element is not configured correctly. So no reason to be scared.
I am not happy with this change, but as I understood it is the actual version of suricata that cause it.
You might ref to: https://community.ipfire.org/t/disable-default-suricata-rules/8137 to have a look at a concerning conversation.
BR Wayne