NuGet

All advisory changes →Check your tickets

247advisory rows73advisories174packagesRSSas of the 2026-09-07 snapshot

An advisory is the GHSA entry a Dependabot alert links to; GitHub-reviewed only. One row is one change to one package: 4 fixed-in version changed, 243 package added later.

No rate: 35,259 advisories were compared across every ecosystem together, and the analysis carries no count of how many were NuGet, so nothing here divides one number by the other.

Kind of change

4 counted rows · newest advisory first

Changes to GitHub-reviewed advisories naming a package in nuget. Each row gives the kind of change and the advisory it happened to. Where the same change was made to several advisories or packages at once, one row stands for all of them, says how many, and opens to every one. Then the ecosystem and package, what the advisory said beside what it says now, GitHub's severity level, and the date the advisory was published.
Package, The package the change names, or where one row stands for the same change across several packages, how many.	Kind of change	Advisory, The advisory id, or where one row stands for the same change made to several advisories, how many it stands for. An advisory id links to GitHub, and a CVE id is shown beside it where the advisory names one.	What changed	Severity, GitHub's severity level for the advisory as it stands today: low, moderate, high or critical. Where one row stands for advisories at more than one level, it says how many levels, never one of them.	Advisory published, The date the advisory was published. Every lag on this source is measured from it, and it is a third clock beside the CVE catalog's publication date and the date CISA added an entry to KEV. Two kinds of change also carry a date of their own: a withdrawal states its own timestamp, and a changed fix version is dated by reading back through the dated saves of the advisory file until the one where the version first reached the value it has today. A package added and a severity changed leave no commit of their own to date, so for those the date of the change is not recorded at all. That is absence, never same-day.
microsoft.semantickernel.core	Advisory fix version moved	GHSA-2ww3-72rp-wpp4CVE-2026-25592	stated at publication 1.70.0, now states 1.71.0	critical	2026-02-06
microsoft.aspnetcore.spaservices	Advisory fix version moved	GHSA-xr8f-59pp-rxxhCVE-2019-1302	stated at publication 2.1.2, now states 2.1.13	moderate	2022-05-24
microsoft.aspnetcore.spaservices	Advisory fix version moved	GHSA-xr8f-59pp-rxxhCVE-2019-1302	stated at publication 2.2.1, now states 2.2.7	moderate	2022-05-24
auth0.authenticationapi	Advisory fix version moved	GHSA-c9cg-q8r2-xvjqCVE-2019-16929	stated at publication 6.5.3, now states 6.5.4	high	2019-10-24

4 rows, all on this page

Every change counted from this source is on this page, so an advisory with no row here had no change of that kind. No finding here is not an all clear. It means this check found nothing in the history it can see, not that nothing happened.

A grouped row is the same change, repeated: where one change was made to many packages or advisories, the advisory column says how many it stands for and opens to every one. The change is identical; it was not necessarily made in one act.

A fixed-in version is compared within one release branch: an advisory listing a fix for 4.1.x and another for 4.2.x states two, and taking the highest version across the package would report a newly added branch as though an existing branch's fix had changed.

4 more advisories that name a package in nuget had the severity changed, or the whole advisory withdrawn. None of it is counted in any figure above. Open to read it.

A severity level and a withdrawal belong to the whole advisory. The advisory database records neither against a package, so neither can be attributed to an ecosystem. These 4 rows are here for one reason: the same advisory also names a package in nuget in the table above. The other 3,176 of the 3,180 cannot be placed in an ecosystem at all.

Severity changes and withdrawals recorded against advisories that also name a package in nuget. These rows name no ecosystem of their own and are not counted in this page's ecosystem figures.
Kind of change	Advisory	What changed	Severity	Advisory published
Advisory severity changed	GHSA-j7hp-h8jx-5pprCVE-2023-4863	stated at publication MODERATE, now states HIGHNo CVSS vector was stated in the first observed version.	high	2023-09-12
Advisory severity changed	GHSA-jxwx-85vp-gvwmCVE-2021-21252	stated at publication MODERATE, now states HIGHNo CVSS vector was stated in the first observed version.	high	2021-01-13
Advisory severity changed	GHSA-2pqj-h3vj-pqgwCVE-2012-6708	stated at publication HIGH, now states MODERATENo CVSS vector was stated in the first observed version.	moderate	2020-09-01
Advisory severity changed	GHSA-hpcf-8vf9-q4gjCVE-2016-7103	stated at publication HIGH, now states MODERATEThe severity label changed while the stated CVSS vectors stayed the same.	moderate	2017-10-24

Data sources and quality

Every figure on this page counts rows keyed to a GitHub advisory, naming an ecosystem and a package; none counts CVE records or is added to the record counts elsewhere on this site. Rows, advisories and packages are three different numbers, never added.

Not checked: GitHub-reviewed advisories only. An advisory GitHub never reviewed, and an ecosystem it does not review, produce no row at all, so an ecosystem missing from these figures is not evidence that its advisories held.

How advisories are compared, in full →

Advisory data from the GitHub Advisory Database, used under CC-BY-4.0. Not affiliated with or endorsed by GitHub.

Shipped snapshot computed 2026-09-07 from catalog commit ed5547afbae2. Real findings, not live ones: records amended since are not reflected. A later fix version is evidence that the record changed, not evidence that the first fix was incomplete.