Vulnerable non-default builds enable WOLFCRYPT_BACKEND when built with WOLFCRYPT=1. In that path, src/Volume/Pkcs5Kdf.cpp passes the configured iteration count to derive_key_sha256() and derive_key_sha512() in src/Crypto/wolfCrypt.c, but the backend discards it and calls wc_HKDF() rather than a PBKDF2-HMAC implementation. HKDF does not provide VeraCrypt's iteration loop, so changing PIM or the iteration count does not increase SHA-256/SHA-512 volume-header derivation cost. An attacker who obtains an affected container, disk image, or volume header can therefore test password guesses offline at a substantially lower computational cost than intended. The supported affected scope is limited to the opt-in wolfCrypt build path; official precompiled binaries and ordinary distribution packages use the standard PBKDF2 backend. The advisory's implementation detail establishes the incorrect KDF selection and ignored parameter, but it does not establish that every custom build using other backend combinations is affected.