You can access any advisory in the GitHub Advisory Database.
Navigate to https://github.com/advisories.
Optionally, to filter the list, use any of the drop-down menus.
Tip: You can use the sidebar on the left to explore GitHub-reviewed and unreviewed advisories separately.
Click an advisory to view details. By default, you will see GitHub-reviewed advisories for security vulnerabilities. To show malware advisories, use
type:malwarein the search bar.
The database is also accessible using the GraphQL API. By default, queries will return GitHub-reviewed advisories for security vulnerabilities unless you specify
type:malware. For more information, see the "
security_advisory webhook event."
You can suggest improvements to any advisory in the GitHub Advisory Database. For more information, see "Editing security advisories in the GitHub Advisory Database."
You can search the database, and use qualifiers to narrow your search. For example, you can search for advisories created on a certain date, in a specific ecosystem, or in a particular library.
Date formatting must follow the ISO8601 standard, which is
YYYY-MM-DD (year-month-day). You can also add optional time information
THH:MM:SS+00:00 after the date, to search by the hour, minute, and second. That's
T, followed by
HH:MM:SS (hour-minutes-seconds), and a UTC offset (
When you search for a date, you can use greater than, less than, and range qualifiers to further filter results. For more information, see "Understanding the search syntax."
|type:reviewed will show GitHub-reviewed advisories for security vulnerabilities.|
|type:malware will show GitHub-reviewed advisories for malware.|
|type:unreviewed will show unreviewed advisories.|
|GHSA-49wp-qq6x-g2rf will show the advisory with this GitHub Advisory Database ID.|
|CVE-2020-28482 will show the advisory with this CVE ID number.|
|ecosystem:npm will show only advisories affecting NPM packages.|
|severity:high will show only advisories with a high severity level.|
|affects:lodash will show only advisories affecting the lodash library.|
|cwe:352 will show only advisories with this CWE number.|
|credit:octocat will show only advisories credited to the "octocat" user account.|
|sort:created-asc will sort by the oldest advisories first.|
|sort:created-desc will sort by the newest advisories first.|
|sort:updated-asc will sort by the least recently updated first.|
|sort:updated-desc will sort by the most recently updated first.|
|is:withdrawn will show only advisories that have been withdrawn.|
|created:2021-01-13 will show only advisories created on this date.|
|updated:2021-01-13 will show only advisories updated on this date.|
For any GitHub-reviewed advisory in the GitHub Advisory Database, you can see which of your repositories are affected by that security vulnerability or malware. To see a vulnerable repository, you must have access to Dependabot alerts for that repository. For more information, see "About Dependabot alerts."
- Navigate to https://github.com/advisories.
- Click an advisory.
- At the top of the advisory page, click Dependabot alerts.
- Optionally, to filter the list, use the search bar or the drop-down menus. The "Organization" drop-down menu allows you to filter the Dependabot alerts per owner (organization or user).
- For more details about the advisory, and for advice on how to fix the vulnerable repository, click the repository name.