Its a floating point precision issue.
Why would you or anyone expect anything to work at a distance of 10km from origin anyway?
No. There is no chance this is “getting fixed”.
You need to rebase the world around the player whenever your distance exceeds the precision you need.
The same system used in ue4 is still very likely acrive in 5. And if its not you can probably use the blueprint calls to rebase manually.