There are lots of bugs in lots of software, and lots of them get ignored when reported.
I personally aware of multiple security vulnerabilities in major pieces of software that everyone has heard of, which I very quickly and easily stumbled on while working on this software as an AWS engineer several years ago. I had never used an LLM of any kind at the time.
I presented my findings both internally and externally, and the reactions ranged from shrugs to delays to hostility towards me for "getting distracted" or "being overly negative."
Those bugs that I discovered still exist, last time I checked.
- why was this not a secure vulnerability report, why was it public?
- why was this closed [by the submitter]?
For the second question, I suspect it's because they were told a different fix was coming.
I know I have opened a lot of PRs where the only result is I get bot spam in my email and no project reaction, so I close the PR to stop the bot spam; if nobody from Oracle has reacted in 2 months it seems unlikely anyone will.
Nowadays I’ve stopped opening “cold-call” PRs like this. I find a way to chat with a maintainer first and anchor what I want to do (“I hit this bug, would you take a PR to fix it? I was thinking it could be solved by x, would that work?”
Much much better outcomes that way.
Because it was seen as a crash not an RCE. AI's power has been chaining simple crashes into exploits. But that's not generally going to be true.