diff --git a/advisories/github-reviewed/2025/03/GHSA-pgr7-mhp5-fgjp/GHSA-pgr7-mhp5-fgjp.json b/advisories/github-reviewed/2025/03/GHSA-pgr7-mhp5-fgjp/GHSA-pgr7-mhp5-fgjp.json
index 20edd96d7a9..0264826dae3 100644
--- a/advisories/github-reviewed/2025/03/GHSA-pgr7-mhp5-fgjp/GHSA-pgr7-mhp5-fgjp.json
+++ b/advisories/github-reviewed/2025/03/GHSA-pgr7-mhp5-fgjp/GHSA-pgr7-mhp5-fgjp.json
@@ -1,13 +1,13 @@
 {
   "schema_version": "1.4.0",
   "id": "GHSA-pgr7-mhp5-fgjp",
-  "modified": "2025-03-21T03:31:44Z",
+  "modified": "2025-04-09T17:02:38Z",
   "published": "2025-03-20T12:32:50Z",
   "aliases": [
     "CVE-2024-9052"
   ],
   "summary": "vLLM deserialization vulnerability in vllm.distributed.GroupCoordinator.recv_object",
-  "details": "vllm-project vllm version 0.6.0 contains a vulnerability in the distributed training API. The function vllm.distributed.GroupCoordinator.recv_object() deserializes received object bytes using pickle.loads() without sanitization, leading to a remote code execution vulnerability.",
+  "details": "vllm-project vllm version 0.6.0 contains a vulnerability in the distributed training API. The function vllm.distributed.GroupCoordinator.recv_object() deserializes received object bytes using pickle.loads() without sanitization, leading to a remote code execution vulnerability.\n\n### Maintainer perspective\nNote that vLLM does NOT use the code as described in the report on huntr. The problem only exists if you use these internal APIs in a way that exposes them to a network as described. The vllm team was not involved in the analysis of this report and the decision to assign it a CVE.",
   "severity": [
     {
       "type": "CVSS_V3",
@@ -40,6 +40,10 @@
       "type": "ADVISORY",
       "url": "https://nvd.nist.gov/vuln/detail/CVE-2024-9052"
     },
+    {
+      "type": "WEB",
+      "url": "https://github.com/github/advisory-database/pull/5444"
+    },
     {
       "type": "PACKAGE",
       "url": "https://github.com/vllm-project/vllm"