Can't see it exploitable. You're writing some bytes after the allocated object memory. Java objects live in heap. The order will be completely undefined and GC moves objects around. So the best case you just write some bytes into next object, corrupting it in some way. There are millions of objects in any Java program and the program behaviour will be completely non-predicatable if you corrupt the objects. Most likely JVM will eventually crash if you corrupt object header.
This is definitely exploitable. The Java heap is not super different than a normal heap in this regard.
this is exactly how so many other exploits already work, it's definitely exploitable, just difficult
Attacker controlled writes along with heap grooming allows for exploitation. Very common practice.
You can read the article to understand how heap layout is made more predictable.