Sorry, but why?
Why should someone discovering a bug in an enormously complex piece of software have any responsibility for assessing the security implications of that bug?
If the maintainers wanted to make it private they could have done so.
> The stub stores past the logical output length before returning to Java, corrupting the heap.
That's obviously a security vulnerability. If they didn't understand that, how did they even find it?
> The stub stores past the logical output length before returning to Java, corrupting the heap.
It was obviously a security vulnerability. That the project didn't immediately re-write then close the PR and admonish submitter is astounding.
The takeaway from this is not "the submitter was wrong", it's "we need to move off of openjdk yesterday".