Setting an AES-GCM-SIV IV shorter than the expected nonce length via the `EVP CipherInit ex()` function (or equivalent provider cipher initialization) may trigger a heap out-of-bounds read. This occurs because the software copies the caller-supplied IV into its internal state using the expected nonce size instead of the actual length provided. If a longer IV is supplied, the implementation silently truncates the trailing bytes instead of rejecting the input. This truncation breaks the binding between the IV and the authentication tag, allowing an attacker who knows a message and its tag to forge messages under a different IV if the initial bytes match. The issue specifically affects applications using an IV length other than the standard 12 bytes for AES-GCM-SIV. The out-of-bounds read is processed within the `ossl aes gcm siv init()` function.