Go
173advisory rows139advisories115packagesRSSas 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: 16 fixed-in version changed, 157 package added later.
No rate: 35,259 advisories were compared across every ecosystem together, and the analysis carries no count of how many were Go, so nothing here divides one number by the other.
157 counted rows in this one change · showing 151 to 157 · newest advisory first
One change, in full: Package added to advisory: 102 packages named as affected in go. The same change, 157 rows across 124 advisories. Back to go
| 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. |
|---|---|---|---|---|---|
| helm.sh/helm/v3 | Package added to advisory | GHSA-cjjc-xp8v-855wCVE-2020-7919 | not named as affected when the advisory was published, now names helm.sh/helm/v3 | high | 2021-06-23 |
| github.com/russellhaering/goxmldsig | Package added to advisory | GHSA-gq5r-cc4w-g8xf | not named as affected when the advisory was published, now names github.com/russellhaering/goxmldsig | high | 2021-06-23 |
| github.com/square/go-jose | Package added to advisory | GHSA-86r9-39j9-99wpCVE-2016-9121 | not named as affected when the advisory was published, now names github.com/square/go-jose | critical | 2021-06-23 |
| k8s.io/kubernetes | Package added to advisory | GHSA-g42g-737j-qx6jCVE-2021-25735 | not named as affected when the advisory was published, now names k8s.io/kubernetes | moderate | 2021-05-28 |
| github.com/docker/docker | Package added to advisory | GHSA-vj3f-3286-r4pfCVE-2014-9356 | not named as affected when the advisory was published, now names github.com/docker/docker | moderate | 2021-05-18 |
| k8s.io/kube-state-metrics | Package added to advisory | GHSA-2v6x-frw8-7r7fCVE-2019-17110 | not named as affected when the advisory was published, now names k8s.io/kube-state-metrics | moderate | 2021-05-18 |
| k8s.io/kubernetes | Package added to advisory | GHSA-6qfg-8799-r575CVE-2019-11251 | not named as affected when the advisory was published, now names k8s.io/kubernetes | moderate | 2021-05-18 |
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.
19 more advisories that name a package in go 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 19 rows are here for one reason: the same advisory also names a package in go in the table above. The other 3,161 of the 3,180 cannot be placed in an ecosystem at all.
| Kind of change | Advisory | What changed | Severity | Advisory published |
|---|---|---|---|---|
| Advisory severity changed | GHSA-cj55-gc7m-wvcqCVE-2024-45258 | stated at publication HIGH, now states MODERATEThe severity label changed while the stated CVSS vectors stayed the same. | moderate | 2024-08-26 |
| Advisory severity changed | GHSA-rpcc-p8xm-rc6pCVE-2024-3056 | stated at publication MODERATE, now states HIGHThe severity label changed while the stated CVSS vectors stayed the same. | high | 2024-08-02 |
| Advisory severity changed | GHSA-869c-j7wc-8jqvCVE-2019-25211 | stated at publication MODERATE, now states CRITICALNo CVSS vector was stated in the first observed version. | critical | 2024-06-29 |
| Advisory withdrawn | GHSA-vfxf-76hv-v4w4 | withdrawn 2024-01-23 | high | 2024-01-03 |
| Advisory severity changed | GHSA-3f2q-6294-fmq5CVE-2023-46402 | stated at publication MODERATE, now states HIGHNo CVSS vector was stated in the first observed version. | high | 2023-11-18 |
| 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-5wfc-hjrc-gq87CVE-2023-34620 | stated at publication LOW, now states HIGHNo CVSS vector was stated in the first observed version. | high | 2023-06-14 |
| Advisory severity changed | GHSA-46v3-ggjg-qq3xCVE-2022-43760 | stated at publication HIGH, now states MODERATEA CVSS version was added; the existing vectors stayed the same. | moderate | 2023-06-06 |
| Advisory severity changed | GHSA-r88r-gmrh-7j83CVE-2021-4235 | stated at publication HIGH, now states MODERATENo CVSS vector was stated in the first observed version. | moderate | 2022-12-28 |
| Advisory severity changed | GHSA-vp56-r7qv-783vCVE-2020-36559 | stated at publication MODERATE, now states HIGHNo CVSS vector was stated in the first observed version. | high | 2022-12-28 |
| Advisory withdrawn | GHSA-967g-cjx4-h7j6 | withdrawn 2026-01-23 | high | 2022-12-28 |
| Advisory severity changed | GHSA-qx32-f6g6-fcfrCVE-2022-31259 | stated at publication HIGH, now states CRITICALNo CVSS vector was stated in the first observed version. | critical | 2022-05-22 |
| Advisory severity changed | GHSA-hp87-p4gw-j4gqCVE-2022-28948 | stated at publication MODERATE, now states HIGHNo CVSS vector was stated in the first observed version. | high | 2022-05-20 |
| Advisory severity changed | GHSA-pf59-j7c2-rh6xCVE-2020-13597 | stated at publication LOW, now states MODERATEThe severity label changed while the stated CVSS vectors stayed the same. | moderate | 2022-02-15 |
| Advisory severity changed | GHSA-qhm4-jxv7-j9pqCVE-2020-8551 | stated at publication LOW, now states MODERATEThe severity label changed while the stated CVSS vectors stayed the same. | moderate | 2022-02-15 |
| Advisory severity changed | GHSA-x6mj-w4jf-jmgwCVE-2020-8555 | stated at publication LOW, now states MODERATEThe severity label changed while the stated CVSS vectors stayed the same. | moderate | 2022-02-15 |
| Advisory withdrawn | GHSA-gq5r-cc4w-g8xf | withdrawn 2024-05-20 | high | 2021-06-23 |
| Advisory severity changed | GHSA-vj3f-3286-r4pfCVE-2014-9356 | stated at publication HIGH, now states MODERATEThe severity label changed while the stated CVSS vectors stayed the same. | moderate | 2021-05-18 |
| Advisory withdrawn | GHSA-2v6x-frw8-7r7fCVE-2019-17110 | withdrawn 2024-01-23 | moderate | 2021-05-18 |
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 f3250c735415. 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.