I have attached an additional zip that sort of has a workaround that might help point to the cause ...

Apparently envers does not translate an embeddable to it's own property but rather it translates every individual property of the embeddable to a property on the parent class that has the embeddable property immediately.

So, embeddable NameInfo with property firstName and lastName on the entity Person with the property nameInfo will not actually get the nameInfo property on the envers model for querying, rather it will get 2 "virtual" properties called nameInfo_firstName and nameInfo_lastName ... which does not make sense since what is expected would be nameInfo.firstName and nameInfo.lastName.

We found a similar ticket complaining about the metadata seperator here: https://hibernate.atlassian.net/browse/HHH-9108