oss-sec mailing list archives
Re: Coordinated Disclosure in the LLM Age
From: ROI AI <sales () roiai ca>
Date: Wed, 20 May 2026 23:51:18 -0700
Also the entire nonsense about making the found issues public - this is absurd and just exacerbates the asymmetry problem. By keeping the reports private, the OSS teams can deal with the issues more on their timeline. By making them public, they add timeline pressure and enable attackers. Why are you making it harder on yourself? It is the opposite of what you want to do. If it's giving CVE credit to people who've taken the time and tokens to report these issues that concerns you, than just bundle the issues in one CVE. ROI AI From: ROI AI <sales () roiai ca> To: "oss-security"<oss-security () lists openwall com> Date: Wed, 20 May 2026 22:26:21 -0700 Subject: Re: [oss-security] Coordinated Disclosure in the LLM Age People are shooting the messengers here. The fact is - we are going through a generational security event due to the advancement of LLMs. It is also both trivial and extremely effective to use Agentic analysis to filter security reports. As for 'duplicates', people are claiming this when I have seen little evidence. I reported a dozen or so to one major project and no one has yet claimed invalid or duplicate. Moreover, if 'duplicates' are found, then that is a good signal for prioritization. Let's stop talking about how the vulns are found and start fixing them with urgency. ROI AI From: Alan Coopersmith < mailto:alan.coopersmith () oracle com > To: < mailto:oss-security () lists openwall com > Date: Wed, 20 May 2026 10:52:37 -0700 Subject: Re: [oss-security] Coordinated Disclosure in the LLM Age On 4/28/26 07:58, Jeremy Stanley wrote:
I'm sorely tempted, both due to the increased volume and the risk of premature disclosure, to just assume that any vulnerability reported as a result of research using an LLM is trivially discoverable by others, and give up trying to pretend there's any point to working it under embargo.
Other maintainers under similar floods seem to agree: Linux kernel: - https://lkml.org/lkml/2026/5/17/896 - https://docs.kernel.org/process/security-bugs.html DNS servers (BIND, Unbound, PowerDNS): - https://indico.dns-oarc.net/event/56/contributions/1233/ - https://indico.dns-oarc.net/event/56/contributions/1233/attachments/1180/2539/presentation.pdf -- -Alan Coopersmith- mailto:alan.coopersmith () oracle com Oracle Solaris Engineering - https://blogs.oracle.com/solaris Confidential communication. No warranties or commitments unless in a signed agreement. If received in error, notify sender and delete. Unauthorized use prohibited.
Current thread:
- Re: Coordinated Disclosure in the LLM Age, (continued)
- Re: Coordinated Disclosure in the LLM Age Greg KH (Apr 30)
- Re: Coordinated Disclosure in the LLM Age Douglas Bagnall (May 21)
- Re: Coordinated Disclosure in the LLM Age Lucas Holt (Apr 29)
- Re: Coordinated Disclosure in the LLM Age Jeremy Stanley (Apr 29)
- Re: Coordinated Disclosure in the LLM Age Brian May (Apr 29)
- Re: Coordinated Disclosure in the LLM Age Tim Shephard (May 11)
- Sv: Coordinated Disclosure in the LLM Age Markus Klyver (May 15)
- Sv: Coordinated Disclosure in the LLM Age ROI AI (May 15)
- Sv: Coordinated Disclosure in the LLM Age Markus Klyver (May 15)
- Re: Coordinated Disclosure in the LLM Age Alan Coopersmith (May 20)
- Re: Coordinated Disclosure in the LLM Age ROI AI (May 21)
- Re: Coordinated Disclosure in the LLM Age ROI AI (May 21)
- Re: Coordinated Disclosure in the LLM Age ROI AI (May 21)
