https://vulnerability.circl.lu Contains only the most 10 recent sightings. http://www.rssboard.org/rss-specification python-feedgen en Thu, 17 Sep 2026 13:28:47 +0000 https://vulnerability.circl.lu/sighting/91c188e5-dc14-4389-8a46-b6502396c780/export {"uuid": "91c188e5-dc14-4389-8a46-b6502396c780", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37735", "type": "seen", "source": "https://t.me/Intel_Encyclopedia/2016", "content": "\u2728 General Cyber News \u2728\n\n\u041a\u0440\u0438\u0442\u0438\u0447\u0435\u0441\u043a\u0430\u044f \u0443\u044f\u0437\u0432\u0438\u043c\u043e\u0441\u0442\u044c \u0432 Elastic Defend \u0434\u043b\u044f Windows \u043f\u043e\u0437\u0432\u043e\u043b\u044f\u0435\u0442 \u043f\u043e\u0432\u044b\u0448\u0430\u0442\u044c \u043f\u0440\u0438\u0432\u0438\u043b\u0435\u0433\u0438\u0438\n\n\u2014\n\nSummary:\n\u041a\u043e\u043c\u043f\u0430\u043d\u0438\u044f Elastic \u0432\u044b\u043f\u0443\u0441\u0442\u0438\u043b\u0430 \u044d\u043a\u0441\u0442\u0440\u0435\u043d\u043d\u043e\u0435 \u043e\u0431\u043d\u043e\u0432\u043b\u0435\u043d\u0438\u0435 \u0431\u0435\u0437\u043e\u043f\u0430\u0441\u043d\u043e\u0441\u0442\u0438 \u0434\u043b\u044f \u0441\u0432\u043e\u0435\u0433\u043e \u043f\u0440\u043e\u0434\u0443\u043a\u0442\u0430 Elastic Defend \u043f\u043e\u0441\u043b\u0435 \u043e\u0431\u043d\u0430\u0440\u0443\u0436\u0435\u043d\u0438\u044f \u043e\u043f\u0430\u0441\u043d\u043e\u0439 \u0443\u044f\u0437\u0432\u0438\u043c\u043e\u0441\u0442\u0438, \u043f\u043e\u0437\u0432\u043e\u043b\u044f\u044e\u0449\u0435\u0439 \u0437\u043b\u043e\u0443\u043c\u044b\u0448\u043b\u0435\u043d\u043d\u0438\u043a\u0430\u043c \u043f\u043e\u0432\u044b\u0448\u0430\u0442\u044c \u043f\u0440\u0438\u0432\u0438\u043b\u0435\u0433\u0438\u0438 \u043d\u0430 \u0441\u0438\u0441\u0442\u0435\u043c\u0430\u0445 Windows. \u0423\u044f\u0437\u0432\u0438\u043c\u043e\u0441\u0442\u044c, \u043f\u043e\u043b\u0443\u0447\u0438\u0432\u0448\u0430\u044f \u0438\u0434\u0435\u043d\u0442\u0438\u0444\u0438\u043a\u0430\u0442\u043e\u0440 CVE-2025-37735, \u0441\u0432\u044f\u0437\u0430\u043d\u0430 \u0441 \u043d\u0435\u043f\u0440\u0430\u0432\u0438\u043b\u044c\u043d\u044b\u043c \u0441\u043e\u0445\u0440\u0430\u043d\u0435\u043d\u0438\u0435\u043c \u0440\u0430\u0437\u0440\u0435\u0448\u0435\u043d\u0438\u0439 \u0444\u0430\u0439\u043b\u043e\u0432 \u0432 \u0441\u043b\u0443\u0436\u0431\u0435 Defend \u0438 \u043f\u0440\u0435\u0434\u0441\u0442\u0430\u0432\u043b\u044f\u0435\u0442 \u0441\u0435\u0440\u044c\u0435\u0437\u043d\u0443\u044e \u0443\u0433\u0440\u043e\u0437\u0443 \u0434\u043b\u044f \u043e\u0440\u0433\u0430\u043d\u0438\u0437\u0430\u0446\u0438\u0439, \u0438\u0441\u043f\u043e\u043b\u044c\u0437\u0443\u044e\u0449\u0438\u0445 \u044d\u0442\u0443 \u043f\u043b\u0430\u0442\u0444\u043e\u0440\u043c\u0443 \u0437\u0430\u0449\u0438\u0442\u044b \u043a\u043e\u043d\u0435\u0447\u043d\u044b\u0445 \u0442\u043e\u0447\u0435\u043a. \u0414\u0435\u0442\u0430\u043b\u0438 \u0443\u044f\u0437\u0432\u0438\u043c\u043e\u0441\u0442\u0438 \u041f\u0440\u043e\u0431\u043b\u0435\u043c\u0430 \u0437\u0430\u0442\u0440\u0430\u0433\u0438\u0432\u0430\u0435\u0442 \u043c\u0435\u0445\u0430\u043d\u0438\u0437\u043c \u043e\u0431\u0440\u0430\u0431\u043e\u0442\u043a\u0438 \u0444\u0430\u0439\u043b\u043e\u0432\u044b\u0445...\n\n\u2014\n\nSource: SEC-1275-1\nPublished: 2025-11-10 07:44 | Author: Vulner Queen\n\n#defend #elastic #general_cyber_news\n\nhttps://1275.ru/vulnerability/kriticheskaya-uyazvimost-v-elastic-defend-dlya-windows-pozvolyaet-povyshat-privilegii_16155", "creation_timestamp": "2026-09-10T00:00:36.172853Z"} {"uuid": "91c188e5-dc14-4389-8a46-b6502396c780", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37735", "type": "seen", "source": "https://t.me/Intel_Encyclopedia/2016", "content": "\u2728 General Cyber News \u2728\n\n\u041a\u0440\u0438\u0442\u0438\u0447\u0435\u0441\u043a\u0430\u044f \u0443\u044f\u0437\u0432\u0438\u043c\u043e\u0441\u0442\u044c \u0432 Elastic Defend \u0434\u043b\u044f Windows \u043f\u043e\u0437\u0432\u043e\u043b\u044f\u0435\u0442 \u043f\u043e\u0432\u044b\u0448\u0430\u0442\u044c \u043f\u0440\u0438\u0432\u0438\u043b\u0435\u0433\u0438\u0438\n\n\u2014\n\nSummary:\n\u041a\u043e\u043c\u043f\u0430\u043d\u0438\u044f Elastic \u0432\u044b\u043f\u0443\u0441\u0442\u0438\u043b\u0430 \u044d\u043a\u0441\u0442\u0440\u0435\u043d\u043d\u043e\u0435 \u043e\u0431\u043d\u043e\u0432\u043b\u0435\u043d\u0438\u0435 \u0431\u0435\u0437\u043e\u043f\u0430\u0441\u043d\u043e\u0441\u0442\u0438 \u0434\u043b\u044f \u0441\u0432\u043e\u0435\u0433\u043e \u043f\u0440\u043e\u0434\u0443\u043a\u0442\u0430 Elastic Defend \u043f\u043e\u0441\u043b\u0435 \u043e\u0431\u043d\u0430\u0440\u0443\u0436\u0435\u043d\u0438\u044f \u043e\u043f\u0430\u0441\u043d\u043e\u0439 \u0443\u044f\u0437\u0432\u0438\u043c\u043e\u0441\u0442\u0438, \u043f\u043e\u0437\u0432\u043e\u043b\u044f\u044e\u0449\u0435\u0439 \u0437\u043b\u043e\u0443\u043c\u044b\u0448\u043b\u0435\u043d\u043d\u0438\u043a\u0430\u043c \u043f\u043e\u0432\u044b\u0448\u0430\u0442\u044c \u043f\u0440\u0438\u0432\u0438\u043b\u0435\u0433\u0438\u0438 \u043d\u0430 \u0441\u0438\u0441\u0442\u0435\u043c\u0430\u0445 Windows. \u0423\u044f\u0437\u0432\u0438\u043c\u043e\u0441\u0442\u044c, \u043f\u043e\u043b\u0443\u0447\u0438\u0432\u0448\u0430\u044f \u0438\u0434\u0435\u043d\u0442\u0438\u0444\u0438\u043a\u0430\u0442\u043e\u0440 CVE-2025-37735, \u0441\u0432\u044f\u0437\u0430\u043d\u0430 \u0441 \u043d\u0435\u043f\u0440\u0430\u0432\u0438\u043b\u044c\u043d\u044b\u043c \u0441\u043e\u0445\u0440\u0430\u043d\u0435\u043d\u0438\u0435\u043c \u0440\u0430\u0437\u0440\u0435\u0448\u0435\u043d\u0438\u0439 \u0444\u0430\u0439\u043b\u043e\u0432 \u0432 \u0441\u043b\u0443\u0436\u0431\u0435 Defend \u0438 \u043f\u0440\u0435\u0434\u0441\u0442\u0430\u0432\u043b\u044f\u0435\u0442 \u0441\u0435\u0440\u044c\u0435\u0437\u043d\u0443\u044e \u0443\u0433\u0440\u043e\u0437\u0443 \u0434\u043b\u044f \u043e\u0440\u0433\u0430\u043d\u0438\u0437\u0430\u0446\u0438\u0439, \u0438\u0441\u043f\u043e\u043b\u044c\u0437\u0443\u044e\u0449\u0438\u0445 \u044d\u0442\u0443 \u043f\u043b\u0430\u0442\u0444\u043e\u0440\u043c\u0443 \u0437\u0430\u0449\u0438\u0442\u044b \u043a\u043e\u043d\u0435\u0447\u043d\u044b\u0445 \u0442\u043e\u0447\u0435\u043a. \u0414\u0435\u0442\u0430\u043b\u0438 \u0443\u044f\u0437\u0432\u0438\u043c\u043e\u0441\u0442\u0438 \u041f\u0440\u043e\u0431\u043b\u0435\u043c\u0430 \u0437\u0430\u0442\u0440\u0430\u0433\u0438\u0432\u0430\u0435\u0442 \u043c\u0435\u0445\u0430\u043d\u0438\u0437\u043c \u043e\u0431\u0440\u0430\u0431\u043e\u0442\u043a\u0438 \u0444\u0430\u0439\u043b\u043e\u0432\u044b\u0445...\n\n\u2014\n\nSource: SEC-1275-1\nPublished: 2025-11-10 07:44 | Author: Vulner Queen\n\n#defend #elastic #general_cyber_news\n\nhttps://1275.ru/vulnerability/kriticheskaya-uyazvimost-v-elastic-defend-dlya-windows-pozvolyaet-povyshat-privilegii_16155", "creation_timestamp": "2026-09-10T00:00:36.172853Z"} https://vulnerability.circl.lu/sighting/91c188e5-dc14-4389-8a46-b6502396c780/export Thu, 10 Sep 2026 00:00:36 +0000 https://vulnerability.circl.lu/sighting/f8cbf429-c385-499c-8cf8-9c6e9ca5efef/export {"uuid": "f8cbf429-c385-499c-8cf8-9c6e9ca5efef", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37735", "type": "seen", "source": "https://t.me/Intel_Encyclopedia/2016", "content": "\u2728 General Cyber News \u2728\n\n\u041a\u0440\u0438\u0442\u0438\u0447\u0435\u0441\u043a\u0430\u044f \u0443\u044f\u0437\u0432\u0438\u043c\u043e\u0441\u0442\u044c \u0432 Elastic Defend \u0434\u043b\u044f Windows \u043f\u043e\u0437\u0432\u043e\u043b\u044f\u0435\u0442 \u043f\u043e\u0432\u044b\u0448\u0430\u0442\u044c \u043f\u0440\u0438\u0432\u0438\u043b\u0435\u0433\u0438\u0438\n\n\u2014\n\nSummary:\n\u041a\u043e\u043c\u043f\u0430\u043d\u0438\u044f Elastic \u0432\u044b\u043f\u0443\u0441\u0442\u0438\u043b\u0430 \u044d\u043a\u0441\u0442\u0440\u0435\u043d\u043d\u043e\u0435 \u043e\u0431\u043d\u043e\u0432\u043b\u0435\u043d\u0438\u0435 \u0431\u0435\u0437\u043e\u043f\u0430\u0441\u043d\u043e\u0441\u0442\u0438 \u0434\u043b\u044f \u0441\u0432\u043e\u0435\u0433\u043e \u043f\u0440\u043e\u0434\u0443\u043a\u0442\u0430 Elastic Defend \u043f\u043e\u0441\u043b\u0435 \u043e\u0431\u043d\u0430\u0440\u0443\u0436\u0435\u043d\u0438\u044f \u043e\u043f\u0430\u0441\u043d\u043e\u0439 \u0443\u044f\u0437\u0432\u0438\u043c\u043e\u0441\u0442\u0438, \u043f\u043e\u0437\u0432\u043e\u043b\u044f\u044e\u0449\u0435\u0439 \u0437\u043b\u043e\u0443\u043c\u044b\u0448\u043b\u0435\u043d\u043d\u0438\u043a\u0430\u043c \u043f\u043e\u0432\u044b\u0448\u0430\u0442\u044c \u043f\u0440\u0438\u0432\u0438\u043b\u0435\u0433\u0438\u0438 \u043d\u0430 \u0441\u0438\u0441\u0442\u0435\u043c\u0430\u0445 Windows. \u0423\u044f\u0437\u0432\u0438\u043c\u043e\u0441\u0442\u044c, \u043f\u043e\u043b\u0443\u0447\u0438\u0432\u0448\u0430\u044f \u0438\u0434\u0435\u043d\u0442\u0438\u0444\u0438\u043a\u0430\u0442\u043e\u0440 CVE-2025-37735, \u0441\u0432\u044f\u0437\u0430\u043d\u0430 \u0441 \u043d\u0435\u043f\u0440\u0430\u0432\u0438\u043b\u044c\u043d\u044b\u043c \u0441\u043e\u0445\u0440\u0430\u043d\u0435\u043d\u0438\u0435\u043c \u0440\u0430\u0437\u0440\u0435\u0448\u0435\u043d\u0438\u0439 \u0444\u0430\u0439\u043b\u043e\u0432 \u0432 \u0441\u043b\u0443\u0436\u0431\u0435 Defend \u0438 \u043f\u0440\u0435\u0434\u0441\u0442\u0430\u0432\u043b\u044f\u0435\u0442 \u0441\u0435\u0440\u044c\u0435\u0437\u043d\u0443\u044e \u0443\u0433\u0440\u043e\u0437\u0443 \u0434\u043b\u044f \u043e\u0440\u0433\u0430\u043d\u0438\u0437\u0430\u0446\u0438\u0439, \u0438\u0441\u043f\u043e\u043b\u044c\u0437\u0443\u044e\u0449\u0438\u0445 \u044d\u0442\u0443 \u043f\u043b\u0430\u0442\u0444\u043e\u0440\u043c\u0443 \u0437\u0430\u0449\u0438\u0442\u044b \u043a\u043e\u043d\u0435\u0447\u043d\u044b\u0445 \u0442\u043e\u0447\u0435\u043a. \u0414\u0435\u0442\u0430\u043b\u0438 \u0443\u044f\u0437\u0432\u0438\u043c\u043e\u0441\u0442\u0438 \u041f\u0440\u043e\u0431\u043b\u0435\u043c\u0430 \u0437\u0430\u0442\u0440\u0430\u0433\u0438\u0432\u0430\u0435\u0442 \u043c\u0435\u0445\u0430\u043d\u0438\u0437\u043c \u043e\u0431\u0440\u0430\u0431\u043e\u0442\u043a\u0438 \u0444\u0430\u0439\u043b\u043e\u0432\u044b\u0445...\n\n\u2014\n\nSource: SEC-1275-1\nPublished: 2025-11-10 07:44 | Author: Vulner Queen\n\n#defend #elastic #general_cyber_news\n\nhttps://1275.ru/vulnerability/kriticheskaya-uyazvimost-v-elastic-defend-dlya-windows-pozvolyaet-povyshat-privilegii_16155", "creation_timestamp": "2026-09-09T05:00:15.454064Z"} {"uuid": "f8cbf429-c385-499c-8cf8-9c6e9ca5efef", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37735", "type": "seen", "source": "https://t.me/Intel_Encyclopedia/2016", "content": "\u2728 General Cyber News \u2728\n\n\u041a\u0440\u0438\u0442\u0438\u0447\u0435\u0441\u043a\u0430\u044f \u0443\u044f\u0437\u0432\u0438\u043c\u043e\u0441\u0442\u044c \u0432 Elastic Defend \u0434\u043b\u044f Windows \u043f\u043e\u0437\u0432\u043e\u043b\u044f\u0435\u0442 \u043f\u043e\u0432\u044b\u0448\u0430\u0442\u044c \u043f\u0440\u0438\u0432\u0438\u043b\u0435\u0433\u0438\u0438\n\n\u2014\n\nSummary:\n\u041a\u043e\u043c\u043f\u0430\u043d\u0438\u044f Elastic \u0432\u044b\u043f\u0443\u0441\u0442\u0438\u043b\u0430 \u044d\u043a\u0441\u0442\u0440\u0435\u043d\u043d\u043e\u0435 \u043e\u0431\u043d\u043e\u0432\u043b\u0435\u043d\u0438\u0435 \u0431\u0435\u0437\u043e\u043f\u0430\u0441\u043d\u043e\u0441\u0442\u0438 \u0434\u043b\u044f \u0441\u0432\u043e\u0435\u0433\u043e \u043f\u0440\u043e\u0434\u0443\u043a\u0442\u0430 Elastic Defend \u043f\u043e\u0441\u043b\u0435 \u043e\u0431\u043d\u0430\u0440\u0443\u0436\u0435\u043d\u0438\u044f \u043e\u043f\u0430\u0441\u043d\u043e\u0439 \u0443\u044f\u0437\u0432\u0438\u043c\u043e\u0441\u0442\u0438, \u043f\u043e\u0437\u0432\u043e\u043b\u044f\u044e\u0449\u0435\u0439 \u0437\u043b\u043e\u0443\u043c\u044b\u0448\u043b\u0435\u043d\u043d\u0438\u043a\u0430\u043c \u043f\u043e\u0432\u044b\u0448\u0430\u0442\u044c \u043f\u0440\u0438\u0432\u0438\u043b\u0435\u0433\u0438\u0438 \u043d\u0430 \u0441\u0438\u0441\u0442\u0435\u043c\u0430\u0445 Windows. \u0423\u044f\u0437\u0432\u0438\u043c\u043e\u0441\u0442\u044c, \u043f\u043e\u043b\u0443\u0447\u0438\u0432\u0448\u0430\u044f \u0438\u0434\u0435\u043d\u0442\u0438\u0444\u0438\u043a\u0430\u0442\u043e\u0440 CVE-2025-37735, \u0441\u0432\u044f\u0437\u0430\u043d\u0430 \u0441 \u043d\u0435\u043f\u0440\u0430\u0432\u0438\u043b\u044c\u043d\u044b\u043c \u0441\u043e\u0445\u0440\u0430\u043d\u0435\u043d\u0438\u0435\u043c \u0440\u0430\u0437\u0440\u0435\u0448\u0435\u043d\u0438\u0439 \u0444\u0430\u0439\u043b\u043e\u0432 \u0432 \u0441\u043b\u0443\u0436\u0431\u0435 Defend \u0438 \u043f\u0440\u0435\u0434\u0441\u0442\u0430\u0432\u043b\u044f\u0435\u0442 \u0441\u0435\u0440\u044c\u0435\u0437\u043d\u0443\u044e \u0443\u0433\u0440\u043e\u0437\u0443 \u0434\u043b\u044f \u043e\u0440\u0433\u0430\u043d\u0438\u0437\u0430\u0446\u0438\u0439, \u0438\u0441\u043f\u043e\u043b\u044c\u0437\u0443\u044e\u0449\u0438\u0445 \u044d\u0442\u0443 \u043f\u043b\u0430\u0442\u0444\u043e\u0440\u043c\u0443 \u0437\u0430\u0449\u0438\u0442\u044b \u043a\u043e\u043d\u0435\u0447\u043d\u044b\u0445 \u0442\u043e\u0447\u0435\u043a. \u0414\u0435\u0442\u0430\u043b\u0438 \u0443\u044f\u0437\u0432\u0438\u043c\u043e\u0441\u0442\u0438 \u041f\u0440\u043e\u0431\u043b\u0435\u043c\u0430 \u0437\u0430\u0442\u0440\u0430\u0433\u0438\u0432\u0430\u0435\u0442 \u043c\u0435\u0445\u0430\u043d\u0438\u0437\u043c \u043e\u0431\u0440\u0430\u0431\u043e\u0442\u043a\u0438 \u0444\u0430\u0439\u043b\u043e\u0432\u044b\u0445...\n\n\u2014\n\nSource: SEC-1275-1\nPublished: 2025-11-10 07:44 | Author: Vulner Queen\n\n#defend #elastic #general_cyber_news\n\nhttps://1275.ru/vulnerability/kriticheskaya-uyazvimost-v-elastic-defend-dlya-windows-pozvolyaet-povyshat-privilegii_16155", "creation_timestamp": "2026-09-09T05:00:15.454064Z"} https://vulnerability.circl.lu/sighting/f8cbf429-c385-499c-8cf8-9c6e9ca5efef/export Wed, 09 Sep 2026 05:00:15 +0000 https://vulnerability.circl.lu/sighting/e7f7e20f-e922-4fd9-b5db-e00eb9f27e2a/export {"uuid": "e7f7e20f-e922-4fd9-b5db-e00eb9f27e2a", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37164", "type": "seen", "source": "https://github.com/rapid7/metasploit-framework/blob/master/modules/exploits/linux/http/hpe_oneview_rce.rb", "content": "{\"aliases\": [], \"arch\": \"cmd\", \"author\": [\"Nguyen Quoc Khanh\", \"remmons-r7\", \"sfewer-r7\"], \"autofilter_ports\": [80, 8080, 443, 8000, 8888, 8880, 8008, 3000, 8443], \"autofilter_services\": [\"http\", \"https\"], \"check\": true, \"default_credential\": false, \"description\": \"This module exploits an unauthenticated RCE vulnerability, CVE-2025-37164, against Hewlett Packard Enterprise\\n (HPE) OneView. All versions below 11.00 are vulnerable (so long as the vendor supplied hotfix has not been\\n applied), however some VM product versions do not enable the vulnerable \\\"ID Pools\\\" endpoint, and are not\\n exploitable.\", \"disclosure_date\": \"2025-12-16\", \"fullname\": \"exploit/linux/http/hpe_oneview_rce\", \"is_install_path\": true, \"mod_time\": \"2025-12-19 15:38:43 +0000\", \"name\": \"HPE OneView unauthenticated RCE\", \"needs_cleanup\": null, \"notes\": {\"Reliability\": [\"repeatable-session\"], \"SideEffects\": [\"ioc-in-logs\"], \"Stability\": [\"crash-safe\"]}, \"path\": \"/modules/exploits/linux/http/hpe_oneview_rce.rb\", \"platform\": \"Linux,Unix\", \"post_auth\": false, \"rank\": 600, \"ref_name\": \"linux/http/hpe_oneview_rce\", \"references\": [\"CVE-2025-37164\", \"URL-https://support.hpe.com/hpesc/public/docDisplay?docId=hpesbgn04985en_us&docLocale=en_US\", \"URL-https://www.rapid7.com/blog/post/etr-cve-2025-37164-critical-unauthenticated-rce-affecting-hewlett-packard-enterprise-oneview/\", \"URL-https://attackerkb.com/topics/ixWdbDvjwX/cve-2025-37164/rapid7-analysis\"], \"rport\": 443, \"session_types\": false, \"targets\": [\"Default\"], \"type\": \"exploit\"}", "creation_timestamp": "2026-09-08T06:48:37.655458Z"} {"uuid": "e7f7e20f-e922-4fd9-b5db-e00eb9f27e2a", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37164", "type": "seen", "source": "https://github.com/rapid7/metasploit-framework/blob/master/modules/exploits/linux/http/hpe_oneview_rce.rb", "content": "{\"aliases\": [], \"arch\": \"cmd\", \"author\": [\"Nguyen Quoc Khanh\", \"remmons-r7\", \"sfewer-r7\"], \"autofilter_ports\": [80, 8080, 443, 8000, 8888, 8880, 8008, 3000, 8443], \"autofilter_services\": [\"http\", \"https\"], \"check\": true, \"default_credential\": false, \"description\": \"This module exploits an unauthenticated RCE vulnerability, CVE-2025-37164, against Hewlett Packard Enterprise\\n (HPE) OneView. All versions below 11.00 are vulnerable (so long as the vendor supplied hotfix has not been\\n applied), however some VM product versions do not enable the vulnerable \\\"ID Pools\\\" endpoint, and are not\\n exploitable.\", \"disclosure_date\": \"2025-12-16\", \"fullname\": \"exploit/linux/http/hpe_oneview_rce\", \"is_install_path\": true, \"mod_time\": \"2025-12-19 15:38:43 +0000\", \"name\": \"HPE OneView unauthenticated RCE\", \"needs_cleanup\": null, \"notes\": {\"Reliability\": [\"repeatable-session\"], \"SideEffects\": [\"ioc-in-logs\"], \"Stability\": [\"crash-safe\"]}, \"path\": \"/modules/exploits/linux/http/hpe_oneview_rce.rb\", \"platform\": \"Linux,Unix\", \"post_auth\": false, \"rank\": 600, \"ref_name\": \"linux/http/hpe_oneview_rce\", \"references\": [\"CVE-2025-37164\", \"URL-https://support.hpe.com/hpesc/public/docDisplay?docId=hpesbgn04985en_us&docLocale=en_US\", \"URL-https://www.rapid7.com/blog/post/etr-cve-2025-37164-critical-unauthenticated-rce-affecting-hewlett-packard-enterprise-oneview/\", \"URL-https://attackerkb.com/topics/ixWdbDvjwX/cve-2025-37164/rapid7-analysis\"], \"rport\": 443, \"session_types\": false, \"targets\": [\"Default\"], \"type\": \"exploit\"}", "creation_timestamp": "2026-09-08T06:48:37.655458Z"} https://vulnerability.circl.lu/sighting/e7f7e20f-e922-4fd9-b5db-e00eb9f27e2a/export Tue, 08 Sep 2026 06:48:37 +0000 https://vulnerability.circl.lu/sighting/c63568c0-6eed-46bb-a6b3-6eefc11e980d/export {"uuid": "c63568c0-6eed-46bb-a6b3-6eefc11e980d", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37899", "type": "published-proof-of-concept", "source": "https://t.me/hacking_Attack/160936", "content": "Your strategy for hunting 0days\nhttps://www.reddit.com/r/redteamsec/comments/1kwtl4f/your_strategy_for_hunting_0days/\n\nI recently read the post about this guy finding a 0day using chatgpt o3 model and it's really interesting the way he talks about how he carefully picks the attack surface for the model to analyze, only providing certain handler functions to look for UAF's, up to a limited call depth. It made me wonder how hunting for 0days requires not only a carefully thought out strategy, but it's also probably different for everyone. I''m curious how different vuln researchers approach this? What is your strategy? How do you pick the codebase/project to research and how do you pick the specific part/section of the source code (or execution flow) to analyze? In general: what is your strategy? submitted by /u/Lmao_vogreward_shard (https://www.reddit.com/user/Lmao_vogreward_shard) \n [link] (https://sean.heelan.io/2025/05/22/how-i-used-o3-to-find-cve-2025-37899-a-remote-zeroday-vulnerability-in-the-linux-kernels-smb-implementation/) [comments] (https://www.reddit.com/r/redteamsec/comments/1kwtl4f/your_strategy_for_hunting_0days/)", "creation_timestamp": "2026-09-04T00:00:53.645721Z"} {"uuid": "c63568c0-6eed-46bb-a6b3-6eefc11e980d", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37899", "type": "published-proof-of-concept", "source": "https://t.me/hacking_Attack/160936", "content": "Your strategy for hunting 0days\nhttps://www.reddit.com/r/redteamsec/comments/1kwtl4f/your_strategy_for_hunting_0days/\n\nI recently read the post about this guy finding a 0day using chatgpt o3 model and it's really interesting the way he talks about how he carefully picks the attack surface for the model to analyze, only providing certain handler functions to look for UAF's, up to a limited call depth. It made me wonder how hunting for 0days requires not only a carefully thought out strategy, but it's also probably different for everyone. I''m curious how different vuln researchers approach this? What is your strategy? How do you pick the codebase/project to research and how do you pick the specific part/section of the source code (or execution flow) to analyze? In general: what is your strategy? submitted by /u/Lmao_vogreward_shard (https://www.reddit.com/user/Lmao_vogreward_shard) \n [link] (https://sean.heelan.io/2025/05/22/how-i-used-o3-to-find-cve-2025-37899-a-remote-zeroday-vulnerability-in-the-linux-kernels-smb-implementation/) [comments] (https://www.reddit.com/r/redteamsec/comments/1kwtl4f/your_strategy_for_hunting_0days/)", "creation_timestamp": "2026-09-04T00:00:53.645721Z"} https://vulnerability.circl.lu/sighting/c63568c0-6eed-46bb-a6b3-6eefc11e980d/export Fri, 04 Sep 2026 00:00:53 +0000 https://vulnerability.circl.lu/sighting/0a67c05e-6c7a-40a6-86d0-a92854b593bd/export {"uuid": "0a67c05e-6c7a-40a6-86d0-a92854b593bd", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37899", "type": "published-proof-of-concept", "source": "https://t.me/hacking_Attack/160936", "content": "Your strategy for hunting 0days\nhttps://www.reddit.com/r/redteamsec/comments/1kwtl4f/your_strategy_for_hunting_0days/\n\nI recently read the post about this guy finding a 0day using chatgpt o3 model and it's really interesting the way he talks about how he carefully picks the attack surface for the model to analyze, only providing certain handler functions to look for UAF's, up to a limited call depth. It made me wonder how hunting for 0days requires not only a carefully thought out strategy, but it's also probably different for everyone. I''m curious how different vuln researchers approach this? What is your strategy? How do you pick the codebase/project to research and how do you pick the specific part/section of the source code (or execution flow) to analyze? In general: what is your strategy? submitted by /u/Lmao_vogreward_shard (https://www.reddit.com/user/Lmao_vogreward_shard) \n [link] (https://sean.heelan.io/2025/05/22/how-i-used-o3-to-find-cve-2025-37899-a-remote-zeroday-vulnerability-in-the-linux-kernels-smb-implementation/) [comments] (https://www.reddit.com/r/redteamsec/comments/1kwtl4f/your_strategy_for_hunting_0days/)", "creation_timestamp": "2026-09-03T10:00:04.241147Z"} {"uuid": "0a67c05e-6c7a-40a6-86d0-a92854b593bd", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37899", "type": "published-proof-of-concept", "source": "https://t.me/hacking_Attack/160936", "content": "Your strategy for hunting 0days\nhttps://www.reddit.com/r/redteamsec/comments/1kwtl4f/your_strategy_for_hunting_0days/\n\nI recently read the post about this guy finding a 0day using chatgpt o3 model and it's really interesting the way he talks about how he carefully picks the attack surface for the model to analyze, only providing certain handler functions to look for UAF's, up to a limited call depth. It made me wonder how hunting for 0days requires not only a carefully thought out strategy, but it's also probably different for everyone. I''m curious how different vuln researchers approach this? What is your strategy? How do you pick the codebase/project to research and how do you pick the specific part/section of the source code (or execution flow) to analyze? In general: what is your strategy? submitted by /u/Lmao_vogreward_shard (https://www.reddit.com/user/Lmao_vogreward_shard) \n [link] (https://sean.heelan.io/2025/05/22/how-i-used-o3-to-find-cve-2025-37899-a-remote-zeroday-vulnerability-in-the-linux-kernels-smb-implementation/) [comments] (https://www.reddit.com/r/redteamsec/comments/1kwtl4f/your_strategy_for_hunting_0days/)", "creation_timestamp": "2026-09-03T10:00:04.241147Z"} https://vulnerability.circl.lu/sighting/0a67c05e-6c7a-40a6-86d0-a92854b593bd/export Thu, 03 Sep 2026 10:00:04 +0000 https://vulnerability.circl.lu/sighting/41beb9c0-9b30-48c0-acae-aa1eb5d50249/export {"uuid": "41beb9c0-9b30-48c0-acae-aa1eb5d50249", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37899", "type": "seen", "source": "https://t.me/hacking_Attack/160936", "content": "Your strategy for hunting 0days\nhttps://www.reddit.com/r/redteamsec/comments/1kwtl4f/your_strategy_for_hunting_0days/\n\nI recently read the post about this guy finding a 0day using chatgpt o3 model and it's really interesting the way he talks about how he carefully picks the attack surface for the model to analyze, only providing certain handler functions to look for UAF's, up to a limited call depth. It made me wonder how hunting for 0days requires not only a carefully thought out strategy, but it's also probably different for everyone. I''m curious how different vuln researchers approach this? What is your strategy? How do you pick the codebase/project to research and how do you pick the specific part/section of the source code (or execution flow) to analyze? In general: what is your strategy? submitted by /u/Lmao_vogreward_shard (https://www.reddit.com/user/Lmao_vogreward_shard) \n [link] (https://sean.heelan.io/2025/05/22/how-i-used-o3-to-find-cve-2025-37899-a-remote-zeroday-vulnerability-in-the-linux-kernels-smb-implementation/) [comments] (https://www.reddit.com/r/redteamsec/comments/1kwtl4f/your_strategy_for_hunting_0days/)", "creation_timestamp": "2026-09-02T01:00:40.316224Z"} {"uuid": "41beb9c0-9b30-48c0-acae-aa1eb5d50249", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37899", "type": "seen", "source": "https://t.me/hacking_Attack/160936", "content": "Your strategy for hunting 0days\nhttps://www.reddit.com/r/redteamsec/comments/1kwtl4f/your_strategy_for_hunting_0days/\n\nI recently read the post about this guy finding a 0day using chatgpt o3 model and it's really interesting the way he talks about how he carefully picks the attack surface for the model to analyze, only providing certain handler functions to look for UAF's, up to a limited call depth. It made me wonder how hunting for 0days requires not only a carefully thought out strategy, but it's also probably different for everyone. I''m curious how different vuln researchers approach this? What is your strategy? How do you pick the codebase/project to research and how do you pick the specific part/section of the source code (or execution flow) to analyze? In general: what is your strategy? submitted by /u/Lmao_vogreward_shard (https://www.reddit.com/user/Lmao_vogreward_shard) \n [link] (https://sean.heelan.io/2025/05/22/how-i-used-o3-to-find-cve-2025-37899-a-remote-zeroday-vulnerability-in-the-linux-kernels-smb-implementation/) [comments] (https://www.reddit.com/r/redteamsec/comments/1kwtl4f/your_strategy_for_hunting_0days/)", "creation_timestamp": "2026-09-02T01:00:40.316224Z"} https://vulnerability.circl.lu/sighting/41beb9c0-9b30-48c0-acae-aa1eb5d50249/export Wed, 02 Sep 2026 01:00:40 +0000 https://vulnerability.circl.lu/sighting/ea5d8be6-c429-418c-a3bf-5549d2375a9c/export {"uuid": "ea5d8be6-c429-418c-a3bf-5549d2375a9c", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37899", "type": "seen", "source": "https://t.me/hacking_Attack/160936", "content": "Your strategy for hunting 0days\nhttps://www.reddit.com/r/redteamsec/comments/1kwtl4f/your_strategy_for_hunting_0days/\n\nI recently read the post about this guy finding a 0day using chatgpt o3 model and it's really interesting the way he talks about how he carefully picks the attack surface for the model to analyze, only providing certain handler functions to look for UAF's, up to a limited call depth. It made me wonder how hunting for 0days requires not only a carefully thought out strategy, but it's also probably different for everyone. I''m curious how different vuln researchers approach this? What is your strategy? How do you pick the codebase/project to research and how do you pick the specific part/section of the source code (or execution flow) to analyze? In general: what is your strategy? submitted by /u/Lmao_vogreward_shard (https://www.reddit.com/user/Lmao_vogreward_shard) \n [link] (https://sean.heelan.io/2025/05/22/how-i-used-o3-to-find-cve-2025-37899-a-remote-zeroday-vulnerability-in-the-linux-kernels-smb-implementation/) [comments] (https://www.reddit.com/r/redteamsec/comments/1kwtl4f/your_strategy_for_hunting_0days/)", "creation_timestamp": "2026-09-01T20:00:23.771640Z"} {"uuid": "ea5d8be6-c429-418c-a3bf-5549d2375a9c", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37899", "type": "seen", "source": "https://t.me/hacking_Attack/160936", "content": "Your strategy for hunting 0days\nhttps://www.reddit.com/r/redteamsec/comments/1kwtl4f/your_strategy_for_hunting_0days/\n\nI recently read the post about this guy finding a 0day using chatgpt o3 model and it's really interesting the way he talks about how he carefully picks the attack surface for the model to analyze, only providing certain handler functions to look for UAF's, up to a limited call depth. It made me wonder how hunting for 0days requires not only a carefully thought out strategy, but it's also probably different for everyone. I''m curious how different vuln researchers approach this? What is your strategy? How do you pick the codebase/project to research and how do you pick the specific part/section of the source code (or execution flow) to analyze? In general: what is your strategy? submitted by /u/Lmao_vogreward_shard (https://www.reddit.com/user/Lmao_vogreward_shard) \n [link] (https://sean.heelan.io/2025/05/22/how-i-used-o3-to-find-cve-2025-37899-a-remote-zeroday-vulnerability-in-the-linux-kernels-smb-implementation/) [comments] (https://www.reddit.com/r/redteamsec/comments/1kwtl4f/your_strategy_for_hunting_0days/)", "creation_timestamp": "2026-09-01T20:00:23.771640Z"} https://vulnerability.circl.lu/sighting/ea5d8be6-c429-418c-a3bf-5549d2375a9c/export Tue, 01 Sep 2026 20:00:23 +0000 https://vulnerability.circl.lu/sighting/2c80fa02-a516-4bbf-826c-17e35ef9e7a5/export {"uuid": "2c80fa02-a516-4bbf-826c-17e35ef9e7a5", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37164", "type": "exploited", "source": "https://t.me/CyberDispatch/525", "content": "Check Point says CVE-2025-37164 is being mass-exploited to spread the RondoDox botnet, with 40,000+ attacks on Jan 7.\n\nThe activity targeted government, finance, and industrial sectors, prompting same-day KEV inclusion.", "creation_timestamp": "2026-08-31T00:00:10.670720Z"} {"uuid": "2c80fa02-a516-4bbf-826c-17e35ef9e7a5", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37164", "type": "exploited", "source": "https://t.me/CyberDispatch/525", "content": "Check Point says CVE-2025-37164 is being mass-exploited to spread the RondoDox botnet, with 40,000+ attacks on Jan 7.\n\nThe activity targeted government, finance, and industrial sectors, prompting same-day KEV inclusion.", "creation_timestamp": "2026-08-31T00:00:10.670720Z"} https://vulnerability.circl.lu/sighting/2c80fa02-a516-4bbf-826c-17e35ef9e7a5/export Mon, 31 Aug 2026 00:00:10 +0000 https://vulnerability.circl.lu/sighting/11ae2144-b2e0-481f-8196-2d956e35a2a9/export {"uuid": "11ae2144-b2e0-481f-8196-2d956e35a2a9", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37164", "type": "seen", "source": "https://t.me/CyberDispatch/525", "content": "Check Point says CVE-2025-37164 is being mass-exploited to spread the RondoDox botnet, with 40,000+ attacks on Jan 7.\n\nThe activity targeted government, finance, and industrial sectors, prompting same-day KEV inclusion.", "creation_timestamp": "2026-08-30T00:00:49.263064Z"} {"uuid": "11ae2144-b2e0-481f-8196-2d956e35a2a9", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37164", "type": "seen", "source": "https://t.me/CyberDispatch/525", "content": "Check Point says CVE-2025-37164 is being mass-exploited to spread the RondoDox botnet, with 40,000+ attacks on Jan 7.\n\nThe activity targeted government, finance, and industrial sectors, prompting same-day KEV inclusion.", "creation_timestamp": "2026-08-30T00:00:49.263064Z"} https://vulnerability.circl.lu/sighting/11ae2144-b2e0-481f-8196-2d956e35a2a9/export Sun, 30 Aug 2026 00:00:49 +0000 https://vulnerability.circl.lu/sighting/90b069e7-9d9a-48d0-92a7-119223a3ddb9/export {"uuid": "90b069e7-9d9a-48d0-92a7-119223a3ddb9", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37164", "type": "seen", "source": "https://t.me/CyberDispatch/525", "content": "Check Point says CVE-2025-37164 is being mass-exploited to spread the RondoDox botnet, with 40,000+ attacks on Jan 7.\n\nThe activity targeted government, finance, and industrial sectors, prompting same-day KEV inclusion.", "creation_timestamp": "2026-08-29T20:00:23.670456Z"} {"uuid": "90b069e7-9d9a-48d0-92a7-119223a3ddb9", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-37164", "type": "seen", "source": "https://t.me/CyberDispatch/525", "content": "Check Point says CVE-2025-37164 is being mass-exploited to spread the RondoDox botnet, with 40,000+ attacks on Jan 7.\n\nThe activity targeted government, finance, and industrial sectors, prompting same-day KEV inclusion.", "creation_timestamp": "2026-08-29T20:00:23.670456Z"} https://vulnerability.circl.lu/sighting/90b069e7-9d9a-48d0-92a7-119223a3ddb9/export Sat, 29 Aug 2026 20:00:23 +0000