Vulnerability reports are not special anymore(words.filippo.io)
325 points by goranmoomin 13 hours ago | 176 comments
tl;dr: Open source maintainers have traditionally treated vulnerability reports as special obligations—owing responsiveness and credit to researchers in exchange for their scarce insight and confidentiality. But in 2026, LLMs have made vuln discovery cheap and abundant, shifting the bottleneck from finding bugs to triaging them, while also eroding the value of embargoes since attackers can run the same tools. The author argues maintainers should now focus on rapid triage, remediation, and prevention (possibly via LLM analysis in CI), reserving "special" treatment only for high-severity reports or trusted researchers.
HN Discussion:
  • Spam and low-quality vuln reports overwhelm maintainers, validating the need to deprioritize them
  • Current LLM-driven flood is temporary; bugs will get fixed and reports will become special again
  • ~The problem demands engineering solutions like memory-safe languages to eliminate bug classes entirely
  • Low-quality vuln reports and bad incentives predate LLMs; nothing fundamentally new here
  • ~Concern about commercialization and hype-driven dynamics distorting the vulnerability disclosure space