The bug was was recently fixed here:
… but the bug affects bytestring-0.11.0.0 through bytestring-0.11.3.1 (and the fix still hasn't been published to Hackage). For reference, ghc-9.2 and ghc-9.4 ship by default with bytestring versions that are affected by this bug.
From reading through related issues it seems like the full impact of the bug is not completely known, but it is known to affect warp servers (which includes servant and yesod servers):
I'm curious if we're unknowingly hitting this at work