Security fixes should not require handing someone the keys to your entire GitHub repository. As of November 20, 2026, organization owners can delegate security advisory work through more focused custom repository roles.
That means a trusted maintainer can help triage private vulnerability reports without automatically becoming a repository administrator or an organization-wide security manager.
What changed?
GitHub has made four security advisory permissions generally available for eligible organizations:
- View security advisories: read draft advisories, status information and comments.
- Create, Edit, and Manage: create or edit advisories, comment, manage collaborators and create temporary private forks.
- Accept reports and close or reopen advisories: control vulnerability-report triage; this requires View or Create/Edit/Manage access.
- Publish advisories and request CVEs: handle disclosure and identifier requests; this also requires View or Create/Edit/Manage access.
How to use it
If you own an eligible GitHub organization, open its custom repository role settings and create or edit a role. Under Security, select only the advisory permissions the team needs.
Assign that role to the relevant users or teams on the specific repositories they maintain. For example, a security triage team might need to view and accept reports, while a smaller release team receives permission to publish advisories.
This is especially useful when different teams maintain different services: a vulnerability report for one project should not automatically grant access to every other project’s private disclosures.
Important limits
- This feature requires an organization plan that supports custom repository roles, including GitHub Enterprise Cloud. Do not assume every free or personal repository has it.
- Merging changes from a temporary private fork still requires a repository administrator or security manager.
- These new permissions do not allow deleting a temporary private fork.
- Confidential comments require Create/Edit/Manage permission and repository write access.
Practical takeaway: review who currently has administrator or security manager access solely to handle vulnerability reports. Where supported, replace unnecessary broad access with a narrower custom role, and test the resulting workflow before relying on it.
