The LLMs find the security issues, the LLMs will write the reports and the LLMs will fix and patch them.
I guess its time for all of us to step aside, leave space for somebody who knowns what they are doing, and go fishing...
And this way only LLMs can learn from these vulnerabilities, making it even more likely that the next one will be found by an LLM.
We're all living in the story of mel.
At first, there were just big logic blocks and storage that did as they were told.
Later, in hardware, there were all sorts of optimizations built in where the logic would do its own thing -- so you'd get caches and speculative execution and even on-the-fly conversion from one instruction set to another.
This abstraction was also piled onto the runtime -- you'd write machine code, then assembly, then higher level languages; eventually you'd run in interpreted or just-in-time generated bytecode (hello to Java from UCSD p-System from the 70s and Burroughs machines in the 60s). And of course... operating systems...
Now, we've got machines reading source code (and machine code, and everything in between) and they've got some ability to thing the thing to make it thing. Sometimes correctly (enough to pass existing tests) and sometimes without the ability to express to the human what the thing they thinged was.
But, we're all living in the land of mel and for some it's always been better to go fishing than to pretend to participate.