Python Security Response Team (PSRT)
Skip to content Back to top View this page Edit this page Python Security Response Team (PSRT) ¶ The Python Security Response Team (PSRT) is responsible for handling vulnerability reports for CPython and pip. To report security issues: https://www.python.org/dev/security/ Members ¶ The PSRT publishes a full list of members and admins, included in the table below: Name GitHub username Notes Barry Warsaw warsaw Admin Bénédikt Tran picnixz Damian Shaw notatallshaw Donald Stufft dstufft Dustin Ingram di Emma Smith emmatyping Glyph Lefkowitz glyph Gregory P.
Smith gpshead Hugo van Kemenade hugovk Release Manager Jacob Coffee JacobCoffee Admin Jelle Zijlstra JelleZijlstra Kirill Podoprigora eclips4 Ned Deily ned-deily Admin, Release Manager Pablo Galindo Salgado pablogsal Release Manager Petr Viktorin encukou Pradyun Gedam pradyunsg Savannah Ostrowski savannahostrowski Release Manager Serhiy Storchaka serhiy-storchaka Seth Larson sethmlarson Admin Stan Ulbrych StanFromIreland Admin Steve Dower zooba Release Manager Tania Allard trallard Thomas Wouters Yhg1s Release Manager Victor Stinner vstinner William Woodruff woodruffw See also the members emeritus list .
How can I join the PSRT? ¶ Anyone can join the PSRT following a nomination process similar to core team nominations . Nomination for a new member is brought to the PSRT by an existing PSRT member and then this nomination is voted on by existing PSRT members. The nomination succeeds if the nomination receives at least two-thirds positive votes from a vote of existing PSRT members that is open for one week and not vetoed by the Steering Council.
Every six months the Steering Council will receive a report of inactive PSRT members with the recommendation to remove the inactive users from the PSRT. “Inactive” is defined as a member who hasn’t coordinated or commented on a vulnerability report in the past six months since the last report was generated. The Steering Council may remove members of the PSRT with a simple vote. Release Managers must be members of the PSRT for the duration of their term.
Steering Council members and the release team experts may join the PSRT if they wish. All of these members may remain in the PSRT regardless of inactivity in vulnerability reports. When a member leaves these roles, their PSRT membership becomes a regular membership subject to the inactivity policy above. PSRT admins are not exempt from the inactivity policy and are included in the report of inactive members. Responsibilities of PSRT members ¶ Below are the responsibilities of PSRT members: Being knowledgeable about typical software vulnerability report handling processes, such as CVE IDs, patches, coordinated disclosure, embargoes.
Not sharing or acting on embargoed information about the reported vulnerability. Examples of disallowed behavior include sharing information with colleagues or publicly deploying unpublished mitigations or patches ahead of the advisory publication date. Acting as a “Coordinator” of vulnerability reports that are submitted to projects. A Coordinator’s responsibility is to move a report through the PSRT process to a “finished” state, either rejected or as a published advisory and mitigation, within the industry standard timeline of 90 days.
As a Coordinator, involving relevant core team members or triagers where necessary to make a determination whether a report is a vulnerability and developing a patch. Coordinators are encouraged to involve members of the core team to make the best decision for each report rather than working in isolation. As a Coordinator, calculating the severity using CVSSv4 and authoring advisories to be shared on security-announce@python.org .
These advisories are used for CVE records by the PSF CVE Numbering Authority . Coordinators that can no longer move a report forwards for any reason must delegate their Coordinator role to someone else in the PSRT. Responsibilities of PSRT admins ¶ PSRT members who are designated as admins by the Steering Council have the following additional responsibilities: Triaging the security@python.org mailing list. Managing PSRT membership access including the GitHub team, the mailing list, and Discord channel, to ensure they are synchronized with the canonical list of PSRT members.
On a yearly basis, providing the Steering Council with a report including a list of inactive PSRT members. Running nomination elections, including counting final votes and giving the Steering Council an opportunity to veto nominations via email. Triaging a vulnerability report ¶ PSRT members coordinate reports from when they are first submitted to a “finished” state. Finished states include marking a report as a “non-issue”, opening a public issue on GitHub, or a merged patch with an accompanying CVE and advisory to security-announce@python.org .
Reports should reach a finished state within 90 days of being received by the PSRT. Reports enter the system through security@python.org or on a project GitHub Security Advisory (GHSA) ticketing system. For projects that use GHSA, reports to security@python.org should have reporters re-open their report using GHSA . ┌────────────────────────┐ │ Received a report... │ └──┬──────────────────┬──┘ │ │ ┌────────────▼──────────────┐ ┌─▼──────────┐ │ ..via security@python.org │ │ ..via GHSA │ └────────────┬──────────────┘ └─┬──────────┘ │ │ ┌────────────▼──────────────┐ │ │ PSRT admin reviews email │ │ └───┬───────────────────┬───┘ │ │ │ │ ┌───▼────┐ ┌────▼───┐ │ │ Reject │ │ Accept │ │ └────────┘ └────┬───┘ │ │ │ ┌───────────────────────▼───┐ │ │ PSRT asks reporter to │ │ │ open via GHSA │ │ └────────────┬──────────────┘ │ │ │ ┌──▼──────────────────▼──┐ │ GHSA in state 'Triage' │ └────────────────────────┘ New report in GitHub Security Advisories (GHSA) ¶ Once a report is in GHSA, a “Coordinator” must be assigned to be responsible for moving the report through the process.
The “Coordinator” role is assigned using a “Credit” in a GHSA ticket (Select Edit > Credit > Add a GitHub username and the ‘Coordinator’ role). Important Assigning the “Coordinator” role to each GHSA ticket is important, as this metadata records whether a PSRT member is “active” according to PEP 811 to avoid being removed due to inactivity. If a GHSA ticket is idle for three days without a coordinator assigned, a PSRT member who is not a Release Manager or Steering Council member will be automatically assigned as coordinator by the PSRT bot .
If a coordinator can’t complete the process they must find a replacement coordinator in the PSRT and re-assign the GHSA ticket. ┌────────────────────────┐ │ GHSA in state 'Triage' │ └─┬────────────────────┬─┘ │ │ ┌──────────────────▼─────────┐ ┌────────▼───────────────────┐ │ │ │ After 3 days idle, │ │ PSRT member volunteers │ │ Coordinator is assigned │ │ as Coordinator │ │ automatically by bot │ └───────────────�
The rest of this page is on the live site.