I'm not a Ruby fan, but wouldn't finding those buffer overflows make it
more secure? Now that they've been found, they're fixed. (Sure, it could be indicative of overall careless design, but I don't think that's the case here. A few silly mistakes, now no longer a problem.)
Finally, Ruby has more than one implementation. Finding a hole in one implementation says nothing about the language overall.