diff --git a/advisories/github-reviewed/2021/06/GHSA-jm5c-rv3w-w83m/GHSA-jm5c-rv3w-w83m.json b/advisories/github-reviewed/2021/06/GHSA-jm5c-rv3w-w83m/GHSA-jm5c-rv3w-w83m.json
index ee82bbe5a4b..beb7135a574 100644
--- a/advisories/github-reviewed/2021/06/GHSA-jm5c-rv3w-w83m/GHSA-jm5c-rv3w-w83m.json
+++ b/advisories/github-reviewed/2021/06/GHSA-jm5c-rv3w-w83m/GHSA-jm5c-rv3w-w83m.json
@@ -1,13 +1,13 @@
 {
   "schema_version": "1.4.0",
   "id": "GHSA-jm5c-rv3w-w83m",
-  "modified": "2021-05-21T21:50:44Z",
+  "modified": "2025-01-30T14:38:53Z",
   "published": "2021-06-29T21:13:20Z",
   "aliases": [
     "CVE-2020-26242"
   ],
   "summary": "Denial of service in geth",
-  "details": "### Impact\nDenial-of-service (crash) during block processing\n\n### Details\n\nAffected versions suffer from a vulnerability which can be exploited through the `MULMOD` operation, by specifying a modulo of `0`: `mulmod(a,b,0)`, causing a `panic` in the underlying library. \nThe crash was in the `uint256` library, where a buffer [underflowed](https://github.com/holiman/uint256/blob/4ce82e695c10ddad57215bdbeafb68b8c5df2c30/uint256.go#L442).\n\n\tif `d == 0`, `dLen` remains `0`\n\nand https://github.com/holiman/uint256/blob/4ce82e695c10ddad57215bdbeafb68b8c5df2c30/uint256.go#L451 will try to access index `[-1]`.\n\nThe `uint256` library was first merged in this [commit](https://github.com/ethereum/go-ethereum/commit/cf6674539c589f80031f3371a71c6a80addbe454), on 2020-06-08. \nExploiting this vulnerabilty would cause all vulnerable nodes to drop off the network. \n\nThe issue was brought to our attention through a [bug report](https://github.com/ethereum/go-ethereum/issues/21367), showing a `panic` occurring on sync from genesis on the Ropsten network.\n \nIt was estimated that the least obvious way to fix this would be to merge the fix into `uint256`, make a new release of that library and then update the geth-dependency.\n\n- https://github.com/holiman/uint256/releases/tag/v1.1.1 was made the same day, \n- PR to address the issue: https://github.com/holiman/uint256/pull/80 \n- PR to update geth deps: https://github.com/ethereum/go-ethereum/pull/21368 \n\n\n### Patches\nUpgrade to v1.9.18 or higher\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Open an issue in [go-ethereum](https://github.com/ethereum/go-ethereum)\n* Email us at [security@ethereum.org](mailto:security@ethereum.org)",
+  "details": "### Impact\nDenial-of-service (crash) during block processing\n\n### Details\n\nAffected versions suffer from a vulnerability which can be exploited through the `MULMOD` operation, by specifying a modulo of `0`: `mulmod(a,b,0)`, causing a `panic` in the underlying library. \nThe crash was in the `uint256` library, where a buffer [underflowed](https://github.com/holiman/uint256/blob/4ce82e695c10ddad57215bdbeafb68b8c5df2c30/uint256.go#L442).\n\n\tif `d == 0`, `dLen` remains `0`\n\nand https://github.com/holiman/uint256/blob/4ce82e695c10ddad57215bdbeafb68b8c5df2c30/uint256.go#L451 will try to access index `[-1]`.\n\nThe `uint256` library was first merged in this [commit](https://github.com/ethereum/go-ethereum/commit/cf6674539c589f80031f3371a71c6a80addbe454), on 2020-06-08. \nExploiting this vulnerabilty would cause all vulnerable nodes to drop off the network. \n\nThe issue was brought to our attention through a [bug report](https://github.com/ethereum/go-ethereum/issues/21367), showing a `panic` occurring on sync from genesis on the Ropsten network.\n \nIt was estimated that the least obvious way to fix this would be to merge the fix into `uint256`, make a new release of that library and then update the geth-dependency.\n\n- https://github.com/holiman/uint256/releases/tag/v1.1.1 was made the same day, \n- PR to address the issue: https://github.com/holiman/uint256/pull/80 \n- PR to update geth deps: https://github.com/ethereum/go-ethereum/pull/21368 \n\n\n\n### Patches\n\nUpgrade to v1.9.18 or higher\n\n### Workarounds\n\nNot at this time\n\n### References\n\nhttps://blog.ethereum.org/2020/11/12/geth_security_release/\n### For more information\nIf you have any questions or comments about this advisory:\n* Open an issue in [go-ethereum](https://github.com/ethereum/go-ethereum)\n* Email us at [security@ethereum.org](mailto:security@ethereum.org)\n",
   "severity": [
     {
       "type": "CVSS_V3",
@@ -79,6 +79,10 @@
       "type": "WEB",
       "url": "https://blog.ethereum.org/2020/11/12/geth_security_release"
     },
+    {
+      "type": "PACKAGE",
+      "url": "https://github.com/ethereum/go-ethereum"
+    },
     {
       "type": "WEB",
       "url": "https://pkg.go.dev/vuln/GO-2021-0103"
diff --git a/advisories/github-reviewed/2021/06/GHSA-v592-xf75-856p/GHSA-v592-xf75-856p.json b/advisories/github-reviewed/2021/06/GHSA-v592-xf75-856p/GHSA-v592-xf75-856p.json
index d7c41818d00..d463f42d70d 100644
--- a/advisories/github-reviewed/2021/06/GHSA-v592-xf75-856p/GHSA-v592-xf75-856p.json
+++ b/advisories/github-reviewed/2021/06/GHSA-v592-xf75-856p/GHSA-v592-xf75-856p.json
@@ -1,13 +1,13 @@
 {
   "schema_version": "1.4.0",
   "id": "GHSA-v592-xf75-856p",
-  "modified": "2023-10-02T15:12:07Z",
+  "modified": "2025-01-30T14:39:18Z",
   "published": "2021-06-29T21:12:56Z",
   "aliases": [
     "CVE-2020-26240"
   ],
   "summary": "Erroneous Proof of Work calculation in geth",
-  "details": "### Impact\nAn ethash mining DAG generation flaw in Geth could cause miners to erroneously calculate PoW in an upcoming epoch (estimated early January, 2021). This happened on the ETC chain on 2020-11-06. This issue is relevant only for miners, non-mining nodes are unaffected.\n\n### Specific Go Packages Affected\ngithub.com/ethereum/go-ethereum/consensus\n\n### Patches\nThis issue is also fixed as of 1.9.24. Thanks to @slavikus for bringing the issue to our attention and writing the fix. \n\n### For more information\nIf you have any questions or comments about this advisory:\n* Open an issue in [go-ethereum](https://github.com/ethereum/go-ethereum)\n* Email us at [security@ethereum.org](mailto:security@ethereum.org)",
+  "details": "### Impact\nAn ethash mining DAG generation flaw in Geth could cause miners to erroneously calculate PoW in an upcoming epoch (estimated early January, 2021). This happened on the ETC chain on 2020-11-06. This issue is relevant only for miners, non-mining nodes are unaffected.\n\n### Patches\nThis issue is also fixed as of 1.9.24. Thanks to @slavikus for bringing the issue to our attention and writing the fix. \n\n### Workarounds\nThis PR implements a patch: https://github.com/ethereum/go-ethereum/pull/21793 \n\n### References\nhttps://blog.ethereum.org/2020/11/12/geth_security_release/\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Open an issue in [go-ethereum](https://github.com/ethereum/go-ethereum)\n* Email us at [security@ethereum.org](mailto:security@ethereum.org)",
   "severity": [
     {
       "type": "CVSS_V3",
@@ -55,6 +55,10 @@
     {
       "type": "WEB",
       "url": "https://blog.ethereum.org/2020/11/12/geth_security_release"
+    },
+    {
+      "type": "PACKAGE",
+      "url": "https://github.com/ethereum/go-ethereum"
     }
   ],
   "database_specific": {