Java and Go

Undefined behavior is behavior "for which the standard imposes no requirements." Since Go is not a formally standardized language, the concept of undefined behavior does not really apply to it as such, because there is no standard imposing any requirements in the first place.

You could certainly call it "unpredictable behavior," but it's likely more precise and informative to just call it "heap corruption" and be done with it.