GitHub Advisory Database
The GitHub Advisory Database is GitHub's free, public database of security advisories for open source packages, each with a GHSA ID. It is the data behind Dependabot alerts.
Last updated: November 13, 2026
The GitHub Advisory Database is a public database of security advisories for open source software, browsable at github.com/advisories. Each advisory gets a GHSA ID, names the affected package and version ranges and, when one exists, the first fixed version. Dependabot uses it to decide which of your dependencies to alert you about. The data is published under CC-BY 4.0 in the github/advisory-database repository, one file per advisory in the OSV format.
Three kinds of advisory
GitHub's documentation splits the database into three kinds:
| Kind | Where it comes from | Checked by GitHub | Dependabot alerts |
|---|---|---|---|
| Reviewed | Maintainers, the NVD and other sources, mapped to a package | Yes, for validity and completeness | Yes |
| Unreviewed | Published automatically from the NVD feed | No | No |
| Malware | The npm security team and OpenSSF Malicious Packages | Not applicable; there is no safe version | Yes, when malware alerts are enabled |
A reviewed advisory is the useful one for dependency scanning: a GitHub curator has tied it to a package in a supported ecosystem, with affected ranges and a fixed version. An unreviewed advisory is often a CVE that has not been mapped to any package yet, so tools that rely on package matching cannot act on it.
Besides GitHub-reported advisories and the NVD, the sources include npm, FriendsOfPHP, the Go vulnerability database, the Python Packaging Advisory database, the Ruby Advisory database, RustSec and community contributions.
GHSA IDs
A GHSA ID has the form GHSA-xxxx-xxxx-xxxx, three groups of four characters from the set 23456789cfghjmpqrvwx, for example GHSA-jfh8-c2jp-5v3q for Log4Shell. Unlike a CVE ID it carries no year. Most reviewed advisories also have a CVE ID, but not all: a GHSA can be published for a package vulnerability that never gets a CVE, and malware advisories usually have none.
Ecosystems
Reviewed advisories cover 12 ecosystems: Composer, Erlang, Go, GitHub Actions, Maven, npm, NuGet, pip, Pub, RubyGems, Rust and Swift. A vulnerability in a C library that you vendor, a Debian package or a firmware component falls outside them; for those, look at distribution trackers and the NVD.
Severity and scores
Each advisory carries a severity of low, moderate, high or critical, based on a CVSS 3.1 or 4.0 vector (imported CVEs may use 3.0). GitHub also shows the EPSS score from FIRST, synced daily, which estimates the probability of exploitation in the next 30 days (EPSS).
How a maintainer publishes a GHSA
- A researcher reports privately, through private vulnerability reporting if the repository has it enabled, which creates a proposed advisory, or by the contact in the project's security policy.
- The maintainer opens a draft repository security advisory, discusses it privately and fixes it in a temporary private fork.
- Anyone with admin permissions on the advisory can request a CVE ID. GitHub is a CVE Numbering Authority and usually answers within about three days, unless another CNA covers the project.
- After the patch is released, the maintainer publishes the advisory.
- GitHub reviews it, which can take up to three days. Reviewed advisories are added to the GitHub Advisory Database and can trigger Dependabot alerts for every repository that depends on an affected version.
Anyone can suggest a correction to an existing advisory from its page or by pull request to the repository; GitHub's curation team decides whether to merge it.
GitHub Advisory Database vs OSV vs NVD
| Database | Run by | Keyed by | Scope |
|---|---|---|---|
| GitHub Advisory Database | GitHub | Ecosystem and package | 12 package ecosystems, plus unreviewed NVD CVEs |
| OSV.dev | Google, OpenSSF | Ecosystem and package, Git | Aggregates GHSA and many other databases |
| NVD | NIST | CPE names | Every published CVE, any kind of product |
OSV.dev imports the GitHub Advisory Database, so a GHSA also appears there under the same ID. What a vendor publishes for its own products is covered in security advisory; the machine-readable format for that is CSAF.
How CRACI relates
CRACI shows each package's advisories, with their CVE, GHSA and other IDs and their severity, for the components recorded in each build, and its build history shows which past builds contained a vulnerable dependency. See build-time SBOMs.