Skip to main content
Mallory
← Back to News
standards-framework-updateai-platform-security

GNOME Cuts Vulnerability Disclosure Window Amid Surge in AI-Generated Reports

Regulatory & Policy · 7 sources · Updated 4mo ago · First seen Jul 20, 2026

GNOME Cuts Vulnerability Disclosure Window Amid Surge in AI-Generated Reports

GNOME is changing its security-report handling process after volunteer maintainers were flooded with AI-assisted vulnerability submissions. For issues reported on or after August 1, 2026, the project will reduce its disclosure deadline from 90 days to 30 days, with security lead Michael Catanzaro saying the shorter window better reflects GNOME’s workflow because valid issues are typically fixed within one to three weeks, while others often remain unresolved.

GNOME said it will apply the same rules to AI-assisted and human-written reports, but projects that prohibit AI-generated content will no longer receive forwarded reports when submissions contain AI- or LLM-generated findings; those issues will instead be closed in the tracker, though maintainers may still be notified. Catanzaro, who has overseen GNOME security issue tracking since 2020 with Red Hat support, also said he will stop tracking newly reported issues in November 2026 and fully step away by December 1 unless an experienced community successor is found.

What this changes for youSee the reporting duties and controls this puts on the clock.
Get the context
Event timeline

How this story unfolded

Events from the most recent confirmed update back to the earliest known activity.

5 events · Jul 20, 2026 – Jul 21, 2026
  1. Jul 21, 20264mo ago

    Catanzaro expects to finish GNOME security tracking role

    Help Net Security reported that Catanzaro plans to finish the role by 2026-12-01 unless a successor is found.

    AI-generated reports push GNOME to shorten its disclosure window - Help Net Security
  2. Jul 20, 20264mo ago

    Catanzaro plans to stop taking new GNOME security issues

    Catanzaro said he will stop tracking newly reported GNOME security issues on 2026-11-01 and is seeking experienced community members to take over the role.

    GNOME Changes Security Disclosure Policies Due To AI-Generated Reports - Phoronix
  3. Jul 20, 20264mo ago

    GNOME sets 30-day disclosure window for new reports

    GNOME said it will shorten its vulnerability disclosure deadline from 90 days to 30 days for issues reported on or after 2026-08-01. The change was described as better matching GNOME's workflow because valid issues are usually fixed within weeks.

    GNOME Changes Security Disclosure Policies Due To AI-Generated Reports - Phoronix
  4. Jul 20, 20264mo ago

    GNOME updates vulnerability handling due to AI-generated reports

    GNOME announced changes to its security-report process in response to a steady flow of AI- or LLM-generated vulnerability submissions. The project said it will apply the same rules to AI-assisted and human-written reports, while changing how AI-generated findings are forwarded to projects that prohibit such content.

    GNOME Changes Security Disclosure Policies Due To AI-Generated Reports - Phoronix
  5. Jul 20, 20264mo ago

    Michael Catanzaro begins leading GNOME security issue tracking

    Michael Catanzaro said he has managed GNOME's security issue tracking since November 2020, with support from Red Hat.

    GNOME Changes Security Disclosure Policies Due To AI-Generated Reports - Phoronix
Linked entities

Related entities

Vulnerabilities, threat actors, malware, products, organizations, and breaches Mallory has linked to this story.

Open in app →

Organizations

1 linked
Gnome
Do you run this?See what this changes for your reporting obligations and which controls it puts on the clock.
Get the Regulatory Context
Mallory platform

See the full picture, correlated to your attack surface.

This page covers what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which threat actors are using it right now, and what to deploy next.

Exposure mappingMap indicators from this story to your assets and identify affected systems in minutes.
Threat actor evidenceEvery observed campaign, victim, and pivot linked to actors named in this story.
Associated malwareMalware, exploits, and IOCs connected to the activity described here.
Detection signaturesYARA, Sigma, and Snort rules deployed to your SIEM as soon as they’re published.
Scheduled alertsGet matching new stories delivered to your team as they break, not the next morning.
AI threadsAsk questions about this story and take action on the answers.