Got the same issue Here!
Date 2025-04-26
Workbench 8.0.40
MySQL 8.4.5
It looks like during the process of wizard importing CSV data or even on single row entering data, it will put a bXXXXX (XXXXX as being your data) in front of the wanted BINARY(1) data.

It will also put a b in front of all next data, even if data type was defined in the table editor carefully.

Moving BINARY(1) data in middle of attributes, note all next attributes:
INSERT INTO `noteluq`.`Cours` (`no_cours`, `cours_nom`, `credit`, `cycle`, `actif`, `departement`, `temps_actif`) VALUES ('ADM 1010', 'ADMIN DE GRANDS', '3', '1', b'1', b'ADMIN', b'0001');

The work around I found is moving your (hopefully only) binary attribute to the end of all attributes.

after correction:
INSERT INTO `noteluq`.`Cours` (`no_cours`, `cours_nom`, `credit`, `cycle`, `departement`, `temps_actif`, `actif`) VALUES ('ADM 1010', 'ADMIN DE TI CULS', '3', '1', 'ADMIN', '0001', b'1');

INSERT INTO `noteluq`.`Cours` (`no_cours`, `cours_nom`, `credit`, `cycle`, `departement`, `temps_actif`, `temps_retrait`, `actif`) VALUES ('ADM 1020', 'ADMIN DE GRANDS', '3', '1', 'ADMIN', '0001', '0004', b'0');

The import data table wizard seemed affected by the order data in table has been set. When I try to import data, even I put "actif" at the very end of attributes and save, it appears elsewhere. and creates an error While loading data.

Hope these informations helps