We also stumbled upon this bug in every tested version of Hibernate 5+, even the newest for date, 5.4.4.
In Hibernate 4.3.7 it works without problem, so it’s regression.