Import an Advisory from GitHub

Last modified by Simon Urli on 2026/11/13 10:24

Steps

Import a security advisory drafted on GitHub into the Security Advisory Application instead of creating it in the wiki. The application imports the GitHub advisories of the repositories an administrator listed for import, once a day.

  1. Create the security advisory on GitHub, from the "Security" tab of a repository listed for import, and keep it as a draft.
  2. Wait for the daily import, or ask an administrator to import it right away: on the "Single Advisory Import Tool" page, linked as "this tool" on the application home page, they enter the "Advisory URL" and click "Import advisory".

    The Single Advisory Import Tool page, with the Advisory URL field filled with a GitHub advisory URL and the Import advisory button

  3. The advisory appears in the list of the application home page as a draft, with its title, description, product, CVSS vector, CVE identifier and impacted packages taken from GitHub, a link to the GitHub advisory, and assigned to the XWiki user mapped to one of its GitHub users. An advisory already published on GitHub is imported as disclosed instead.

    An imported advisory in the Draft status, assigned to the XWiki user mapped to its GitHub user, with its Advisory Link pointing to the GitHub advisory

FAQ

How do I keep my changes to an imported advisory?

Check "Prevent override" on the advisory. Otherwise, each time the advisory is updated on GitHub, the next import replaces its title, description, product, CVSS vector, CVE identifier, impacted packages and "compute embargo" with the GitHub data, keeping only its status and assignee. With "Prevent override" checked, the import skips the advisory entirely, so later changes made on GitHub are not imported either.

Get Connected