GitHub has introduced a set of four security advisory permissions that can be attached to custom repository roles. Organization owners can now delegate advisory work—such as drafting, commenting, and publishing security reports—without elevating users to repository administrators or granting the organization‑wide security manager role.
What changed in GitHub permissions
Four distinct actions are now available under the Security tab when defining a custom repository role:
- View security advisories: Allows reading draft advisories, their status, and comments.
- Create, Edit, and Manage security advisories: Includes view rights plus the ability to create and edit advisories, comment, manage collaborators, and spin up a temporary private fork.
- Accept private vulnerability reports and close or reopen security advisories: Requires either the view permission or the create‑edit‑manage set.
- Publish security advisories and request CVEs: Also builds on view or create‑edit‑manage rights.
Roles can be scoped to individual repositories, so teams only receive the access they need for the repos they maintain.
Why the change matters to engineering teams
AI, cloud, DevOps/SRE, and security engineers often need to collaborate on vulnerability triage without exposing full repository control. By separating advisory duties from admin duties, teams can:
- Reduce the blast radius of credential or permission misuse.
- Maintain auditability of who created, edited, or published an advisory.
- Enable private vulnerability reporting workflows that stay confined to the relevant repository.
Operational and security considerations
While the new permissions tighten access, a few constraints remain:
- Merging changes from a temporary private fork still requires a repository administrator or a security manager.
- Users with any of the new permissions cannot delete a temporary private fork.
- Confidential comments are visible only to users who have the Create, Edit, and Manage permission *and* write access to the repository.
- The feature is limited to organizations on plans that support custom repository roles, including GitHub Enterprise Cloud.
Because the permissions apply to both repository security advisories and private vulnerability reports, teams should map existing advisory processes to the new role model to avoid accidental over‑granting.
Related CloudNinjas coverage: DevOps.
What This Means For Practitioners
Review your current advisory workflow and identify the minimal set of actions each participant needs. Then:
- Create custom repository roles that combine the appropriate security advisory permissions.
- Assign those roles to users or teams on a per‑repository basis.
- Ensure that any merge of a temporary private fork is performed by an administrator or security manager.
- Validate that your organization’s plan includes custom repository role support.
Monitoring role assignments and temporary fork activity will help maintain the intended separation of duties while still enabling efficient vulnerability handling.
