There is an error in the stack management when compiling the `IR` for `sha3 64`. Concretely, the `height` variable is miscalculated. The vulnerability can't be triggered without writing the `IR` by hand, meaning it cannot be triggered from regular Vyper code. `sha3 64` is used for retrieval in mappings. No flow that would cache the `key` was found, so the issue shouldn't be possible to trigger when compiling the compiler-generated `IR`. This issue isn't triggered during normal compilation of Vyper code, so the impact is low.