{"vulnerability": "CVE-2025-26598", "sightings": [{"uuid": "53f57805-3f7b-40ca-ad2a-c024756e3e99", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-26598", "type": "seen", "source": "https://infosec.exchange/users/cR0w/statuses/114065731196406120", "content": "", "creation_timestamp": "2025-02-25T17:35:32.474044Z"}, {"uuid": "fdd19636-d5a6-403e-9deb-f2a80d33acf4", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-26598", "type": "seen", "source": "http://www.zerodayinitiative.com/advisories/ZDI-25-139/", "content": "", "creation_timestamp": "2025-03-13T04:00:00.000000Z"}, {"uuid": "870d4172-0d0f-4ae8-8f95-73b900f72f28", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-26598", "type": "seen", "source": "https://bsky.app/profile/bsd.cafe/post/3lj2tzliwsqw2", "content": "", "creation_timestamp": "2025-02-26T07:27:09.533625Z"}, {"uuid": "e5ea207f-c20c-49a6-b5c4-0eb6f90d99c6", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-26598", "type": "seen", "source": "Telegram/8HAXDkwfUuERvEZPrRm02gndBwAxNxuQaWo6blnqeOPCpO4", "content": "", "creation_timestamp": "2026-04-06T15:20:42.000000Z"}, {"uuid": "73d5abdf-2ddb-44ee-9825-7b55323e9630", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-26598", "type": "seen", "source": "MISP/8e1b6542-ae86-4729-a7a6-4e9f670b8bb7", "content": "", "creation_timestamp": "2025-08-22T17:25:06.000000Z"}, {"uuid": "30d24836-757c-4cb3-9fb8-58a5b67a08d7", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-26598", "type": "seen", "source": "Telegram/YPTFZMnbtWpnAikWtS-r7Wh5pSyLx87YJDgdlbqcufwDCfc", "content": "", "creation_timestamp": "2026-04-06T15:21:07.000000Z"}, {"uuid": "2c4f228b-3eb5-49d1-915c-0ff0d902b817", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-26598", "type": "seen", "source": "https://t.me/cvedetector/18898", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2025-26598 - X.Org and Xwayland Out-of-Bounds Write Vulnerability\", \n  \"Content\": \"CVE ID : CVE-2025-26598 \nPublished : Feb. 25, 2025, 4:15 p.m. | 1\u00a0hour, 37\u00a0minutes ago \nDescription : An out-of-bounds write flaw was found in X.Org and Xwayland. The function GetBarrierDevice() searches for the pointer device based on its device ID and returns the matching value, or supposedly NULL, if no match was found. However, the code will return the last element of the list if no matching device ID is found, which can lead to out-of-bounds memory access. \nSeverity: 7.8 | HIGH \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n  \"Detection Date\": \"25 Feb 2025\",\n  \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2025-02-25T19:03:37.000000Z"}, {"uuid": "fb8d4040-f72f-47e6-bccd-9475fe2cfbda", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-26598", "type": "seen", "source": "Telegram/mdfCxTTCb6UE8Zb3blCTSkJTn4LpHAZ5nFeC-QatuPrhfJUt", "content": "", "creation_timestamp": "2025-03-10T14:45:05.000000Z"}, {"uuid": "b75dc7cc-7237-4897-9db5-0a85683514b6", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-26598", "type": "seen", "source": "https://t.me/DarkWebInformer_CVEAlerts/9009", "content": "\ud83d\udd17 DarkWebInformer.com - Cyber Threat Intelligence\n\ud83d\udccc CVE ID: CVE-2025-26598\n\ud83d\udd25 CVSS Score: 7.8 (cvssV3_1, Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H)\n\ud83d\udd39 Description: An out-of-bounds write flaw was found in X.Org and Xwayland. The function GetBarrierDevice() searches for the pointer device based on its device ID and returns the matching value, or supposedly NULL, if no match was found. However, the code will return the last element of the list if no matching device ID is found, which can lead to out-of-bounds memory access.\n\ud83d\udccf Published: 2025-02-25T15:54:57.355Z\n\ud83d\udccf Modified: 2025-03-27T04:20:45.713Z\n\ud83d\udd17 References:\n1. https://access.redhat.com/errata/RHSA-2025:2500\n2. https://access.redhat.com/errata/RHSA-2025:2502\n3. https://access.redhat.com/errata/RHSA-2025:2861\n4. https://access.redhat.com/errata/RHSA-2025:2862\n5. https://access.redhat.com/errata/RHSA-2025:2865\n6. https://access.redhat.com/errata/RHSA-2025:2866\n7. https://access.redhat.com/errata/RHSA-2025:2873\n8. https://access.redhat.com/errata/RHSA-2025:2874\n9. https://access.redhat.com/errata/RHSA-2025:2875\n10. https://access.redhat.com/errata/RHSA-2025:2879\n11. https://access.redhat.com/errata/RHSA-2025:2880\n12. https://access.redhat.com/security/cve/CVE-2025-26598\n13. https://bugzilla.redhat.com/show_bug.cgi?id=2345254", "creation_timestamp": "2025-03-27T04:25:52.000000Z"}, {"uuid": "33248d12-0ef8-47a0-ac4b-70ce85bbd5c1", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-26598", "type": "seen", "source": "https://t.me/DarkWebInformer_CVEAlerts/5326", "content": "\ud83d\udd17 DarkWebInformer.com - Cyber Threat Intelligence\n\ud83d\udccc CVE ID: CVE-2025-26598\n\ud83d\udd25 CVSS Score: 7.8 (cvssV3_1, Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H)\n\ud83d\udd39 Description: An out-of-bounds write flaw was found in X.Org and Xwayland. The function GetBarrierDevice() searches for the pointer device based on its device ID and returns the matching value, or supposedly NULL, if no match was found. However, the code will return the last element of the list if no matching device ID is found, which can lead to out-of-bounds memory access.\n\ud83d\udccf Published: 2025-02-25T15:54:57.355Z\n\ud83d\udccf Modified: 2025-02-25T15:54:57.355Z\n\ud83d\udd17 References:\n1. https://access.redhat.com/security/cve/CVE-2025-26598\n2. https://bugzilla.redhat.com/show_bug.cgi?id=2345254", "creation_timestamp": "2025-02-25T16:23:12.000000Z"}]}