diff --git a/advisories/github-reviewed/2025/01/GHSA-8655-xgh5-5vvq/GHSA-8655-xgh5-5vvq.json b/advisories/github-reviewed/2025/01/GHSA-8655-xgh5-5vvq/GHSA-8655-xgh5-5vvq.json
new file mode 100644
index 00000000000..e0af9ae7848
--- /dev/null
+++ b/advisories/github-reviewed/2025/01/GHSA-8655-xgh5-5vvq/GHSA-8655-xgh5-5vvq.json
@@ -0,0 +1,52 @@
+{
+  "schema_version": "1.4.0",
+  "id": "GHSA-8655-xgh5-5vvq",
+  "modified": "2025-01-29T22:21:18Z",
+  "published": "2025-01-29T22:21:17Z",
+  "aliases": [],
+  "summary": "fast-fault has a segmentation fault due to lack of bound check",
+  "details": "In this case, the \"fast_float::common::AsciiStr::first\" method within the \"AsciiStr\" struct \nuses the unsafe keyword to reading from memory without performing bounds checking. \nSpecifically, it directly dereferences a pointer offset by \"self.ptr\".\nBecause of the above reason, the method accesses invalid memory address when it takes an empty string as its input.\nThis approach violates Rust’s memory safety guarantees, as it can lead to invalid memory access if empty buffer is provided.\n\nNo patched version for fast-float crate has been released, but a patch is available in the fast-float2 fork.\n",
+  "severity": [],
+  "affected": [
+    {
+      "package": {
+        "ecosystem": "crates.io",
+        "name": "fast-float"
+      },
+      "ranges": [
+        {
+          "type": "ECOSYSTEM",
+          "events": [
+            {
+              "introduced": "0"
+            },
+            {
+              "last_affected": "0.2.0"
+            }
+          ]
+        }
+      ]
+    }
+  ],
+  "references": [
+    {
+      "type": "WEB",
+      "url": "https://github.com/aldanor/fast-float-rust/issues/38"
+    },
+    {
+      "type": "PACKAGE",
+      "url": "https://github.com/aldanor/fast-float-rust"
+    },
+    {
+      "type": "WEB",
+      "url": "https://rustsec.org/advisories/RUSTSEC-2025-0003.html"
+    }
+  ],
+  "database_specific": {
+    "cwe_ids": [],
+    "severity": "MODERATE",
+    "github_reviewed": true,
+    "github_reviewed_at": "2025-01-29T22:21:17Z",
+    "nvd_published_at": null
+  }
+}
\ No newline at end of file
diff --git a/advisories/github-reviewed/2025/01/GHSA-jqcp-xc3v-f446/GHSA-jqcp-xc3v-f446.json b/advisories/github-reviewed/2025/01/GHSA-jqcp-xc3v-f446/GHSA-jqcp-xc3v-f446.json
index 7ba0bd98469..755fd3fcf47 100644
--- a/advisories/github-reviewed/2025/01/GHSA-jqcp-xc3v-f446/GHSA-jqcp-xc3v-f446.json
+++ b/advisories/github-reviewed/2025/01/GHSA-jqcp-xc3v-f446/GHSA-jqcp-xc3v-f446.json
@@ -1,10 +1,10 @@
 {
   "schema_version": "1.4.0",
   "id": "GHSA-jqcp-xc3v-f446",
-  "modified": "2025-01-29T22:19:30Z",
+  "modified": "2025-01-29T22:21:13Z",
   "published": "2025-01-29T22:19:01Z",
   "aliases": [],
-  "summary": "fast-float2 has segmentation fault due to lack of bound check",
+  "summary": "fast-float2 has a segmentation fault due to lack of bound check",
   "details": "In this case, the \"fast_float2::common::AsciiStr::first\" method within the \"AsciiStr\" struct \nuses the unsafe keyword to reading from memory without performing bounds checking. \nSpecifically, it directly dereferences a pointer offset by \"self.ptr\".\nBecause of the above reason, the method accesses invalid memory address when it takes an empty string as its input.\nThis approach violates Rust’s memory safety guarantees, as it can lead to invalid memory access if empty buffer is provided.\n",
   "severity": [],
   "affected": [
@@ -33,6 +33,10 @@
       "type": "WEB",
       "url": "https://github.com/aldanor/fast-float-rust/issues/38"
     },
+    {
+      "type": "WEB",
+      "url": "https://github.com/Alexhuszagh/fast-float-rust/pull/7"
+    },
     {
       "type": "PACKAGE",
       "url": "https://github.com/Alexhuszagh/fast-float-rust"