Skip to content

Package advisories

NuGet

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

243 counted rows in this one change · showing 1 to 50 · newest advisory first

One change, in full: Package added to advisory: 171 packages named as affected in nuget. The same change, 243 rows across 70 advisories. Back to nuget

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 changeAdvisory, 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 changedSeverity, 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.
scriban.signedPackage added to advisoryGHSA-6q7j-xr26-3h2cnot named as affected when the advisory was published, now names scriban.signedmoderate2026-06-26
scriban.signedPackage added to advisoryGHSA-q6rr-fm2g-g5x8not named as affected when the advisory was published, now names scriban.signedmoderate2026-06-26
scriban.signedPackage added to advisoryGHSA-24c8-4792-22hxnot named as affected when the advisory was published, now names scriban.signedhigh2026-05-19
microsoft.openapi.kiotaPackage added to advisoryGHSA-2hx3-vp6r-mg3fCVE-2026-41134not named as affected when the advisory was published, now names microsoft.openapi.kiotahigh2026-04-14
microsoft.openapi.kiota.builderPackage added to advisoryGHSA-2hx3-vp6r-mg3fCVE-2026-41134not named as affected when the advisory was published, now names microsoft.openapi.kiota.builderhigh2026-04-14
scriban.signedPackage added to advisoryGHSA-xw6w-9jjh-p9crnot named as affected when the advisory was published, now names scriban.signedmoderate2026-03-24
scriban.signedPackage added to advisoryGHSA-m2p3-hwv5-xpqwnot named as affected when the advisory was published, now names scriban.signedmoderate2026-03-24
scriban.signedPackage added to advisoryGHSA-xcx6-vp38-8hr5not named as affected when the advisory was published, now names scriban.signedhigh2026-03-24
scriban.signedPackage added to advisoryGHSA-v66j-x4hw-fv9gnot named as affected when the advisory was published, now names scriban.signedhigh2026-03-24
scriban.signedPackage added to advisoryGHSA-c875-h985-hvrcnot named as affected when the advisory was published, now names scriban.signedhigh2026-03-24
scriban.signedPackage added to advisoryGHSA-5wr9-m6jw-xx44not named as affected when the advisory was published, now names scriban.signedcritical2026-03-24
scriban.signedPackage added to advisoryGHSA-x6m9-38vm-2xhfnot named as affected when the advisory was published, now names scriban.signedhigh2026-03-24
scriban.signedPackage added to advisoryGHSA-p6q4-fgr8-vx4pnot named as affected when the advisory was published, now names scriban.signedhigh2026-03-24
scriban.signedPackage added to advisoryGHSA-5rpf-x9jg-8j5pnot named as affected when the advisory was published, now names scriban.signedmoderate2026-03-19
scriban.signedPackage added to advisoryGHSA-grr9-747v-xvcpnot named as affected when the advisory was published, now names scriban.signedhigh2026-03-19
scriban.signedPackage added to advisoryGHSA-wgh7-7m3c-fx25not named as affected when the advisory was published, now names scriban.signedhigh2026-03-19
umbraco.cms.web.commonPackage added to advisoryGHSA-69cg-w8vm-h229CVE-2024-10761not named as affected when the advisory was published, now names umbraco.cms.web.commonmoderate2025-01-21
prodotnetzipPackage added to advisoryGHSA-xhg6-9j5j-w4vfCVE-2024-48510not named as affected when the advisory was published, now names prodotnetziphigh2024-11-13
microsoft.extensions.caching.memoryPackage added to advisoryGHSA-qj66-m88j-hmgjCVE-2024-43483not named as affected when the advisory was published, now names microsoft.extensions.caching.memoryhigh2024-10-08
microsoft.netcore.app.runtime.linux-armPackage added to advisoryGHSA-5fxj-whcv-crrcCVE-2024-21392not named as affected when the advisory was published, now names microsoft.netcore.app.runtime.linux-armhigh2024-03-12
microsoft.netcore.app.runtime.linux-arm64Package added to advisoryGHSA-5fxj-whcv-crrcCVE-2024-21392not named as affected when the advisory was published, now names microsoft.netcore.app.runtime.linux-arm64high2024-03-12
microsoft.netcore.app.runtime.linux-musl-armPackage added to advisoryGHSA-5fxj-whcv-crrcCVE-2024-21392not named as affected when the advisory was published, now names microsoft.netcore.app.runtime.linux-musl-armhigh2024-03-12
microsoft.netcore.app.runtime.linux-musl-arm64Package added to advisoryGHSA-5fxj-whcv-crrcCVE-2024-21392not named as affected when the advisory was published, now names microsoft.netcore.app.runtime.linux-musl-arm64high2024-03-12
microsoft.netcore.app.runtime.linux-musl-x64Package added to advisoryGHSA-5fxj-whcv-crrcCVE-2024-21392not named as affected when the advisory was published, now names microsoft.netcore.app.runtime.linux-musl-x64high2024-03-12
microsoft.netcore.app.runtime.linux-x64Package added to advisoryGHSA-5fxj-whcv-crrcCVE-2024-21392not named as affected when the advisory was published, now names microsoft.netcore.app.runtime.linux-x64high2024-03-12
microsoft.netcore.app.runtime.osx-arm64Package added to advisoryGHSA-5fxj-whcv-crrcCVE-2024-21392not named as affected when the advisory was published, now names microsoft.netcore.app.runtime.osx-arm64high2024-03-12
microsoft.netcore.app.runtime.osx-x64Package added to advisoryGHSA-5fxj-whcv-crrcCVE-2024-21392not named as affected when the advisory was published, now names microsoft.netcore.app.runtime.osx-x64high2024-03-12
microsoft.netcore.app.runtime.win-armPackage added to advisoryGHSA-5fxj-whcv-crrcCVE-2024-21392not named as affected when the advisory was published, now names microsoft.netcore.app.runtime.win-armhigh2024-03-12
microsoft.netcore.app.runtime.win-arm64Package added to advisoryGHSA-5fxj-whcv-crrcCVE-2024-21392not named as affected when the advisory was published, now names microsoft.netcore.app.runtime.win-arm64high2024-03-12
microsoft.netcore.app.runtime.win-x64Package added to advisoryGHSA-5fxj-whcv-crrcCVE-2024-21392not named as affected when the advisory was published, now names microsoft.netcore.app.runtime.win-x64high2024-03-12
microsoft.netcore.app.runtime.win-x86Package added to advisoryGHSA-5fxj-whcv-crrcCVE-2024-21392not named as affected when the advisory was published, now names microsoft.netcore.app.runtime.win-x86high2024-03-12
kentor.authservicesPackage added to advisoryGHSA-fv2h-753j-9g39CVE-2023-41890not named as affected when the advisory was published, now names kentor.authserviceshigh2023-09-20
magick.net-q16-anycpuPackage added to advisoryGHSA-j7hp-h8jx-5pprCVE-2023-4863not named as affected when the advisory was published, now names magick.net-q16-anycpuhigh2023-09-12
magick.net-q16-hdri-anycpuPackage added to advisoryGHSA-j7hp-h8jx-5pprCVE-2023-4863not named as affected when the advisory was published, now names magick.net-q16-hdri-anycpuhigh2023-09-12
magick.net-q16-x64Package added to advisoryGHSA-j7hp-h8jx-5pprCVE-2023-4863not named as affected when the advisory was published, now names magick.net-q16-x64high2023-09-12
magick.net-q8-anycpuPackage added to advisoryGHSA-j7hp-h8jx-5pprCVE-2023-4863not named as affected when the advisory was published, now names magick.net-q8-anycpuhigh2023-09-12
magick.net-q8-openmp-x64Package added to advisoryGHSA-j7hp-h8jx-5pprCVE-2023-4863not named as affected when the advisory was published, now names magick.net-q8-openmp-x64high2023-09-12
magick.net-q8-x64Package added to advisoryGHSA-j7hp-h8jx-5pprCVE-2023-4863not named as affected when the advisory was published, now names magick.net-q8-x64high2023-09-12
skiasharpPackage added to advisoryGHSA-j7hp-h8jx-5pprCVE-2023-4863not named as affected when the advisory was published, now names skiasharphigh2023-09-12
microsoft.aspnetcore.server.kestrel.transport.libuvPackage added to advisoryGHSA-vmch-3w2x-vhgqCVE-2023-38180not named as affected when the advisory was published, now names microsoft.aspnetcore.server.kestrel.transport.libuvhigh2023-08-09
microsoft.aspnetcore.server.kestrel.transport.socketsPackage added to advisoryGHSA-vmch-3w2x-vhgqCVE-2023-38180not named as affected when the advisory was published, now names microsoft.aspnetcore.server.kestrel.transport.socketshigh2023-08-09
oracle.manageddataaccess.corePackage added to advisoryGHSA-5pm2-9mr2-3frqCVE-2023-21893not named as affected when the advisory was published, now names oracle.manageddataaccess.corehigh2023-01-18
microsoft.aspnetcore.app.runtime.osx-arm64Package added to advisoryGHSA-3rq8-h3gj-r5c6CVE-2022-29117not named as affected when the advisory was published, now names microsoft.aspnetcore.app.runtime.osx-arm64high2022-08-30
jquery.ui.combinedPackage added to advisoryGHSA-h6gj-6jjq-h8g9CVE-2022-31160not named as affected when the advisory was published, now names jquery.ui.combinedmoderate2022-07-18
opcfoundation.netstandard.opc.ua.corePackage added to advisoryGHSA-r7pq-3x6p-7jcmCVE-2022-29863not named as affected when the advisory was published, now names opcfoundation.netstandard.opc.ua.corehigh2022-06-17
opcfoundation.netstandard.opc.ua.corePackage added to advisoryGHSA-vhfw-v69p-crcwCVE-2022-29864not named as affected when the advisory was published, now names opcfoundation.netstandard.opc.ua.corehigh2022-06-17
opcfoundation.netstandard.opc.ua.corePackage added to advisoryGHSA-fvxf-r9fw-49pcCVE-2022-29865not named as affected when the advisory was published, now names opcfoundation.netstandard.opc.ua.corehigh2022-06-17
opcfoundation.netstandard.opc.ua.corePackage added to advisoryGHSA-6fp8-cxc9-4fr9CVE-2022-29866not named as affected when the advisory was published, now names opcfoundation.netstandard.opc.ua.corehigh2022-06-17
opcfoundation.netstandard.opc.ua.corePackage added to advisoryGHSA-5q2v-6j86-5h9vCVE-2022-29862not named as affected when the advisory was published, now names opcfoundation.netstandard.opc.ua.corehigh2022-06-17
microsoft.aspnetcore.app.runtime.linux-musl-armPackage added to advisoryGHSA-242j-2gm6-5rwxCVE-2021-1723not named as affected when the advisory was published, now names microsoft.aspnetcore.app.runtime.linux-musl-armhigh2022-05-24

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 changeAdvisoryWhat changedSeverityAdvisory published
Advisory severity changedGHSA-j7hp-h8jx-5pprCVE-2023-4863stated at publication MODERATE, now states HIGHNo CVSS vector was stated in the first observed version.high2023-09-12
Advisory severity changedGHSA-jxwx-85vp-gvwmCVE-2021-21252stated at publication MODERATE, now states HIGHNo CVSS vector was stated in the first observed version.high2021-01-13
Advisory severity changedGHSA-2pqj-h3vj-pqgwCVE-2012-6708stated at publication HIGH, now states MODERATENo CVSS vector was stated in the first observed version.moderate2020-09-01
Advisory severity changedGHSA-hpcf-8vf9-q4gjCVE-2016-7103stated at publication HIGH, now states MODERATEThe severity label changed while the stated CVSS vectors stayed the same.moderate2017-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.