GNOME Security

The GNOME project is undergoing significant changes in its security tracking process. Michael Catanzaro, who has been managing GNOME's security issue tracking since November 2020, is stepping away from this role. He has been handling this responsibility largely by himself, with support from Red Hat.

Changes in Security Tracking

As of November 1, 2026, Michael will stop tracking newly reported security issues and focus on issues already in the pipeline before that date. By December 1, he anticipates that every disclosure deadline tied to the remaining batch will have passed, marking the end of his involvement in handling issues.

Additionally, GNOME is altering how it handles vulnerability reports. Due to the rise of AI-generated security submissions, the disclosure deadline for issues reported on or after August 1, 2026, is now 30 days, reduced from 90 days.

Impact on Projects

Projects that ban AI-generated contributions need to be aware of these changes. Any security issues submitted to GNOME Security won't be forwarded to such projects, given the significant AI involvement in today's submissions. Instead, the report will be closed in GNOME Security's tracker, and the project's maintainers will be contacted directly.

Future of GNOME Security Tracking

Michael is currently looking for an experienced member of the GNOME community to take over the security tracking role. The ideal candidate should already be familiar with the project and its workflow. The new tracker will inherit the existing workflow, which includes a form on security.org that funnels submissions to a security team.

• Acknowledge new reports within two business days
• Open a confidential issue on GitLab for each submission
• Assign the issue to the relevant project maintainer
• Manually update a basic wiki page on GNOME's GitLab instance to track security issues

Comparison with Other Linux Projects

Other Linux projects, such as Ubuntu, Fedora, and Red Hat, have more advanced security tracking systems in place. For example, Ubuntu publishes searchable and filterable security notices tied to CVE IDs, while Fedora and Red Hat use Bugzilla for tracking.

Conclusion

Technology teams are watching gnome security closely because changes in this space often arrive faster than internal policies can adapt.

For product and engineering leaders, the practical question is how this could reshape roadmaps, vendor choices, and security reviews over the next few quarters.

Organizations that document lessons early tend to respond more calmly when similar patterns appear again.

In many companies, the first impact shows up in planning meetings: teams reassess priorities, revisit risk registers, and check whether existing tooling still fits.

Smaller businesses feel these shifts too. A single platform change or market move can affect customer trust, delivery timelines, and hiring plans.

The most resilient teams treat stories like this as input for quarterly reviews rather than one-day headlines.

If your business depends on modern software, ERP, VoIP, or customer-facing apps, staying informed helps you separate noise from decisions that require action.

Looking ahead, disciplined follow-through matters: assign owners, set review dates, and measure whether your response improved outcomes.

Security and compliance stakeholders should ask whether current controls still match the pace of change described in this update.

Operations leaders can reduce friction by translating the headline into a short internal brief with clear next steps for each department.

Customer support teams may see early signals through tickets, outages, or policy questions long before leadership reviews are scheduled.

Finance and procurement groups should note whether licensing, vendor risk, or implementation costs need revisiting after this development.

Training programs benefit from timely updates so staff understand what changed, what did not change, and what requires escalation.

Architecture reviews are a practical place to test assumptions, especially when new tools, platforms, or threats enter the conversation.

Documentation quality often determines how quickly a company recovers from surprises; capture decisions while context is still clear.

Technology teams are watching gnome security closely because changes in this space often arrive faster than internal policies can adapt.

For product and engineering leaders, the practical question is how this could reshape roadmaps, vendor choices, and security reviews over the next few quarters.

Organizations that document lessons early tend to respond more calmly when similar patterns appear again.

In many companies, the first impact shows up in planning meetings: teams reassess priorities, revisit risk registers, and check whether existing tooling still fits.

Smaller businesses feel these shifts too. A single platform change or market move can affect customer trust, delivery timelines, and hiring plans.

The most resilient teams treat stories like this as input for quarterly reviews rather than one-day headlines.

The changes in GNOME's security tracking process highlight the need for a more efficient and effective system. As the project moves forward, it will be important to find a suitable replacement for Michael and to continue improving the security tracking workflow to ensure the security and integrity of the GNOME project.