Ah yes, great catch. It's a bug in ValidatorImpl#isValidationRequired() where we don't handle class-level corrects correctly and accidentally validate them during validateValue().