crypton-x509-validation versions from 1.6.12 up to but not including 1.10.2 improperly validate IP addresses in certificates by ignoring the iPAddress subjectAltName (SAN) when no dNSName SAN is present. This causes clients to accept certificates with a commonName (CN) matching the target IP but an iPAddress SAN pointing elsewhere, violating expected SAN precedence rules. The flaw allows impersonation if a trusted CA issues such a certificate, typically possible only with private or enterprise CAs. The issue is fixed in version 1.10.2.