Text of peps.python.org › pep-0811 as Styx crawled it on Nov 19, 2026. The page may have changed since. Only its words are kept, without pictures or layout, and only the first part of a long page.

Open the live page

PEP 811 – Defining Python Security Response Team membership and responsibilities | peps.python.org

PEP 811 – Defining Python Security Response Team membership and responsibilities PEP 811 – Defining Python Security Response Team membership and responsibilities Author : Seth Michael Larson <seth at python.org> Sponsor : Gregory P. Smith <greg at krypto.org> Discussions-To : Discourse thread Status : Active Type : Process Topic : Governance Created : 22-Oct-2025 Post-History : 06-Oct-2025 , 28-Oct-2025 Resolution : 04-Dec-2025 Table of Contents Abstract Motivation Limit access to pre-disclosure vulnerability reports Onboarding new contributors to the PSRT Lack of defined ownership for vulnerability reports Aligning with vulnerability disclosure timelines Rationale Steering Council and activity determine membership Using GitHub Security Advisories (GHSA) Specification PSRT Membership Policy PSRT Admins Responsibilities of PSRT members Responsibilities of PSRT Admins GitHub Security Advisories and GitHub Team Continue using security@python.org mailing list Rejected Ideas Should inactive members be more aggressively pruned?

Copyright Abstract This PEP proposes formalizing the membership and responsibilities policies of the Python Security Response Team (PSRT). The PSRT is a “highly trusted cabal of Python developers” which handles security vulnerability disclosures to the security@python.org mailing list. The PSRT receives access to known vulnerabilities affecting CPython and pip before they’re disclosed to the public. This information is sensitive and if leaked could harm Python users through zero-day attacks, where an attacker has access to exploitable vulnerabilities before defenders are notified of fixes and given a chance to upgrade.

However, the PSRT often needs help from core developers in particular subject areas to remediate vulnerabilities. This PEP proposes defined membership and obligations for the PSRT, including a new “Coordinator” role, and proposes adopting GitHub Security Advisories (GHSAs) as the canonical reporting, tracking, and collaboration method between the PSRT, reporters, and core developers for vulnerabilities. Motivation Limit access to pre-disclosure vulnerability reports Vulnerability report information prior to disclosure is sensitive, Python users can be substantially harmed if vulnerabilities are exploited.

For this reason it’s critical to limit access to information to only people involved in the remediation of the vulnerability at hand. The historical approach to collaboration on patch development was to manually add GitHub users to a private python/psrt repository which is a mirror of the python/cpython repository. This approach didn’t allow filtering particular collaborators for specific vulnerabilities, meaning all collaborators had access to all reports and patches.

This manual process discouraged bringing on core developers outside the PSRT to collaborate, which can make patch development more difficult. This limitation also meant vulnerability reporters weren’t able to collaborate on patches, either. Onboarding new contributors to the PSRT Unlike most open-source contributions, the work of the PSRT doesn’t happen in the open. Instead, most work occurs privately by a trusted group to limit access to undisclosed vulnerability reports.

Given the sensitive nature of this work, it appears opaque from the outside, and it’s difficult to get started as a newcomer and to understand the expectations of the group. In practice this has meant that relatively few new members join the PSRT, which over time could negatively impact the group’s ability to triage reports and develop remediations with the core team. Lack of defined ownership for vulnerability reports Currently PSRT reports don’t have a clear “owner” of who is ensuring the incident or report continues moving towards a resolved state.

This is especially an issue in the context of a mailing list, where it’s difficult to know whether an issue is being responded to by someone else already or whether your determination on a report is the same as others within the PSRT. Ideally, similar to issues, pull requests, and PEPs, one defined person would be responsible for moving the mitigation task forward to completion. This allows that person to contribute and make decisions on the task without fear of “stepping on toes”.

Aligning with vulnerability disclosure timelines Vulnerability reporting best practices recommend a 90 day timeline between the initial disclosure and when a report is made public to balance the needs of users, the project, and the reporter. Many vulnerability reporting organizations already use this timeline and will disclose vulnerabilities publicly even if the project doesn’t create their own mitigation. To avoid reports getting stuck, forgotten, or published publicly without a remediation this PEP recommends aligning to the 90 days between initial disclosure and publishing an advisory.

Rationale Steering Council and activity determine membership The PSRT has no mechanism for deciding who to admit to or remove from the PSRT. Combined with the security-sensitive nature of the work it can be difficult to decide who should be admitted, but there must be a system responsible for evaluating PSRT membership. This PEP proposes limiting PSRT membership only to active coordinators of security vulnerabilities, members involved in oversight (Steering Council), and members who need information about security releases (Release Managers).

Activity is recommended as the metric for membership to avoid adding additional risk without any additional benefit to projects by having reports being triaged and coordinated. Using GitHub Security Advisories (GHSA) This PEP proposes adopting GitHub Security Advisories as the system to accept vulnerability reports due to its tight integration with services already in use by relevant projects. CPython and pip already use GitHub for source control, issues, pull requests, continuous integration (CI), and as a part of the release process.

GHSA supports the following features which are desirable for a vulnerability reporting and management platform: Managing GitHub teams and accounts as “collaborators” per-report rather than per-project or globally. Managing non-PSRT collaborators per-report using GitHub accounts. “Pull request”-like user interface for developing remediations. Tracking reporter, coordinator, credits, submission time, CVE ID, and severity for each report within the UI.

Programmatic API for integrating with other services (like CVE) and bots. However, features that are missing from GHSA are: Ability to privately run vulnerability remediation branches on CI. Multiple API endpoints are missing for the GHSA, such as retrieving and creating comments on a GHSA report. These missing features have been reported to GitHub and none are blocking the adoption of GHSA. Some work will need to be done to work around the lack of a complete API for the GHSA feature.

Specification PSRT Membership Policy The PSRT will run nominations similar to core team nominations , where a nomination of a new member is brought to the PSRT by an existing PSRT member and then that nomination is voted on by existing PSRT members. New members are expected to be drawn from core developers, triagers, or PSF staff. It is granted by receiving at least two-thirds positive votes from a vote of existing PSRT members that is open for one week and is not vetoed by the Steering Council.

A list of PSRT members will be published publicly and kept up-to-date by PSRT admins. Once per year the Steering Council will receive a report of inactive members of the PSRT with the recommendation to remove the inactive users from the PSRT. “Inactive” is defined here as a member who hasn’t coordinated or commented on a vulnerability report in the past year since the last report was generated. The Steering Council may remove members of the PSRT with a simple vote.

Members of the PSRT who are a Release Manager or Steering Council me

The rest of this page is on the live site.