{"vulnerability": "CVE-2025-23085", "sightings": [{"uuid": "3483c3e0-4c58-4b80-bb74-a90325bf7853", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-23085", "type": "seen", "source": "https://bsky.app/profile/infosec.skyfleet.blue/post/3lgbppky7xy2t", "content": "", "creation_timestamp": "2025-01-21T20:42:41.775185Z"}, {"uuid": "0e4d3c11-c901-4833-a797-05352f20158e", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-23085", "type": "seen", "source": "https://infosec.exchange/users/cve/statuses/113961362857658078", "content": "", "creation_timestamp": "2025-02-07T07:13:17.685511Z"}, {"uuid": "ca40d020-a1a8-44e3-8f9d-bc57f4d21704", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-23085", "type": "seen", "source": "https://bsky.app/profile/cve-notifications.bsky.social/post/3lhl2kv5nwm2s", "content": "", "creation_timestamp": "2025-02-07T07:16:05.172048Z"}, {"uuid": "f54b5216-5c92-4e1c-8781-fc513986d7ab", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-23085", "type": "seen", "source": "https://bsky.app/profile/cve.skyfleet.blue/post/3lhl7zf6cuv27", "content": "", "creation_timestamp": "2025-02-07T08:53:42.288338Z"}, {"uuid": "03d58c97-dd70-40b5-b649-6304b1ce7b10", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-23085", "type": "seen", "source": "https://t.me/DarkWebInformer_CVEAlerts/5268", "content": "\ud83d\udd17 DarkWebInformer.com - Cyber Threat Intelligence\n\ud83d\udccc CVE ID: CVE-2025-23085\n\ud83d\udd25 CVSS Score: 5.3 (cvssV3_0, Vector: CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L)\n\ud83d\udd39 Description: A memory leak could occur when a remote peer abruptly closes the socket without sending a GOAWAY notification. Additionally, if an invalid header was detected by nghttp2, causing the connection to be terminated by the peer, the same leak was triggered. This flaw could lead to increased memory consumption and potential denial of service under certain conditions.\n\nThis vulnerability affects HTTP/2 Server users on Node.js v18.x, v20.x, v22.x and v23.x.\n\ud83d\udccf Published: 2025-02-07T07:09:25.804Z\n\ud83d\udccf Modified: 2025-02-25T13:07:47.090Z\n\ud83d\udd17 References:\n1. https://nodejs.org/en/blog/vulnerability/january-2025-security-releases", "creation_timestamp": "2025-02-25T13:23:45.000000Z"}, {"uuid": "017a473d-ecd4-4c80-ab91-edfc9d820491", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "86ecb4e1-bb32-44d5-9f39-8a4673af8385", "vulnerability": "CVE-2025-23085", "type": "seen", "source": "https://www.cert.ssi.gouv.fr/avis/CERTFR-2026-AVI-0316/", "content": "", "creation_timestamp": "2026-03-19T00:00:00.000000Z"}, {"uuid": "09f00c21-7daa-4791-93c2-7e6f54e2c076", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-23085", "type": "seen", "source": "https://t.me/cvedetector/17468", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2025-23085 - Node.js - HTTP/2 Server - Socket Memory Leak Vulnerability\", \n  \"Content\": \"CVE ID : CVE-2025-23085 \nPublished : Feb. 7, 2025, 7:15 a.m. | 1\u00a0hour, 50\u00a0minutes ago \nDescription : A memory leak could occur when a remote peer abruptly closes the socket without sending a GOAWAY notification. Additionally, if an invalid header was detected by nghttp2, causing the connection to be terminated by the peer, the same leak was triggered. This flaw could lead to increased memory consumption and potential denial of service under certain conditions.  \n  \nThis vulnerability affects HTTP/2 Server users on Node.js v18.x, v20.x, v22.x and v23.x. \nSeverity: 5.3 | MEDIUM \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n  \"Detection Date\": \"07 Feb 2025\",\n  \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2025-02-07T10:28:19.000000Z"}, {"uuid": "82a0803c-97af-4228-9b3a-6a81dee3f320", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-23085", "type": "seen", "source": "https://t.me/DarkWebInformer_CVEAlerts/3793", "content": "\ud83d\udd17 DarkWebInformer.com - Cyber Threat Intelligence\n\ud83d\udccc CVE ID: CVE-2025-23085\n\ud83d\udd25 CVSS Score: 5.3 (CVSS_V3)\n\ud83d\udd39 Description: A memory leak could occur when a remote peer abruptly closes the socket without sending a GOAWAY notification. Additionally, if an invalid header was detected by nghttp2, causing the connection to be terminated by the peer, the same leak was triggered. This flaw could lead to increased memory consumption and potential denial of service under certain conditions.\n\nThis vulnerability affects HTTP/2 Server users on Node.js v18.x, v20.x, v22.x and v23.x.\n\ud83d\udccf Published: 2025-02-07T09:31:51Z\n\ud83d\udccf Modified: 2025-02-07T09:31:51Z\n\ud83d\udd17 References:\n1. https://nvd.nist.gov/vuln/detail/CVE-2025-23085\n2. https://nodejs.org/en/blog/vulnerability/january-2025-security-releases", "creation_timestamp": "2025-02-07T10:02:40.000000Z"}, {"uuid": "b66a34b6-1ad0-4b73-bfb7-280f2d8c10fd", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-23085", "type": "seen", "source": "https://t.me/DarkWebInformer_CVEAlerts/14193", "content": "\ud83d\udd17 DarkWebInformer.com - Cyber Threat Intelligence\n\ud83d\udccc CVE ID: CVE-2025-23085\n\ud83d\udd25 CVSS Score: 5.3 (cvssV3_0, Vector: CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L)\n\ud83d\udd39 Description: A memory leak could occur when a remote peer abruptly closes the socket without sending a GOAWAY notification. Additionally, if an invalid header was detected by nghttp2, causing the connection to be terminated by the peer, the same leak was triggered. This flaw could lead to increased memory consumption and potential denial of service under certain conditions.\n\nThis vulnerability affects HTTP/2 Server users on Node.js v18.x, v20.x, v22.x and v23.x.\n\ud83d\udccf Published: 2025-02-07T07:09:25.804Z\n\ud83d\udccf Modified: 2025-04-30T22:25:24.192Z\n\ud83d\udd17 References:\n1. https://nodejs.org/en/blog/vulnerability/january-2025-security-releases", "creation_timestamp": "2025-04-30T23:14:32.000000Z"}]}