Mariadb Galera cluster fails when replicating from Mysql 5.7 on use of CREATE USER command

Tested on 10.6.17-12 Enterprise and on 10.11.7 Community.
Setup:
HOST: mysql, mysql 5.7.44 binlog_format=ROW
HOST: m1, mariadb 10.6 GALERA NODE replicating from HOST mysql, Using_Gtid: No (log file and position)
HOST: m2 mariadb 10.6 GALERA NODE
HOST: m3 mariadb 10.6 GALERA NODE
As instructed in documentation here:
https://mariadb.com/kb/en/mariadb-vs-mysql-compatibility/#mysql-57

Whenever "CREATE/ALTER/DROP USER" command is run, the command appears in binlog of mysql server in STATEMENT format, even if it is run with BINLOG_FORMAT=ROW. This replicates to m1 which is mariadb (tested with 10.6 and 10.11).

Error on m1:

2024-05-15 20:16:20 2 [ERROR] WSREP: Vote 0 (success) on 056d8405-1319-11ef-be9f-e3a9809ab84a:358 is inconsistent with group. Leaving cluster.

Error on m2 and m3:

2024-05-15 20:16:19 1 [ERROR] Error in Log_event::read_log_event(): 'Found invalid event in binary log', data_len: 42, event_type: -94

2024-05-15 20:16:19 1 [ERROR] WSREP: applier could not read binlog event, seqno: 358, len: 427

When mariadb is NOT a Galera, and it is replicating from mysql, CREATE USER on mysql does NOT break anything.

When mariadb is Galera and only the ONE node is running, and it is replicating from mysql, CREATE USER on mysql does NOT break anything.
● If a joining node does a full SST, it can join the cluster
● If a joining node starts up and attempts to join the cluster, applying binlogs to catch up, it fails