{"vulnerability": "CVE-2026-25253", "sightings": [{"uuid": "a8836fd3-75d4-4130-9e49-79fd0a6492a2", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2026-25253", "type": "seen", "source": "https://bsky.app/profile/cybersentinel404.bsky.social/post/3mdvfe4vpnr2e", "content": "", "creation_timestamp": "2026-02-02T17:41:13.016594Z"}, {"uuid": "ca4e7fd2-4377-4aaa-b8d5-2d7f78eb5590", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2026-25253", "type": "seen", "source": "https://gist.github.com/mikeelliott/de22f76cec57f4a3d0adb65d172672cb", "content": "", "creation_timestamp": "2026-02-27T15:16:29.000000Z"}, {"uuid": "43d36b40-d8a9-4904-ab6c-b46ddf9f3faf", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2026-25253", "type": "seen", "source": "https://bsky.app/profile/news.www.hackernoob.tips.ap.brid.gy/post/3mex3a2sd5d32", "content": "", "creation_timestamp": "2026-02-16T03:10:31.157925Z"}, {"uuid": "0f3abeb0-e9a1-4e1a-be80-1569f0a94737", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2026-25253", "type": "seen", "source": "https://bsky.app/profile/h4ckers-arise.bsky.social/post/3mf5ybsp7xk2f", "content": "", "creation_timestamp": "2026-02-18T21:06:28.066383Z"}, {"uuid": "dcf994e3-6c28-42fd-a42a-43b6bebe59b8", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2026-25253", "type": "seen", "source": "https://bsky.app/profile/it-connect.bsky.social/post/3me2hg2cuz52x", "content": "", "creation_timestamp": "2026-02-04T18:01:23.854227Z"}, {"uuid": "6415f860-dd11-471d-9267-792734b785c6", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2026-25253", "type": "seen", "source": "https://bsky.app/profile/aliceharper0101.bsky.social/post/3megttbsouw2r", "content": "", "creation_timestamp": "2026-02-09T16:15:28.957768Z"}, {"uuid": "f14101a4-d322-4a07-b0b8-7927072e64a4", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2026-25253", "type": "seen", "source": "https://thehackernews.com/2026/02/openclaw-bug-enables-one-click-remote.html", "content": "", "creation_timestamp": "2026-02-02T15:28:00.000000Z"}, {"uuid": "503dfb93-370f-48da-aa4f-7caff39f965f", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2026-25253", "type": "seen", "source": "https://bsky.app/profile/allsafeus.bsky.social/post/3mdvnkwzidd2o", "content": "", "creation_timestamp": "2026-02-02T20:08:11.832052Z"}, {"uuid": "14a43b7f-83ef-4898-aa1e-ca119032066c", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2026-25253", "type": "seen", "source": "https://bsky.app/profile/r-netsec-bot.bsky.social/post/3mexm5b5wsd2n", "content": "", "creation_timestamp": "2026-02-16T08:13:09.427553Z"}, {"uuid": "fd132283-ac58-448f-9682-46e60ae6097b", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2026-25253", "type": "seen", "source": "https://bsky.app/profile/r-netsec.bsky.social/post/3mexmrmpt442n", "content": "", "creation_timestamp": "2026-02-16T08:24:32.710627Z"}, {"uuid": "4803c361-d458-440a-af43-63caafeadded", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2026-25253", "type": "seen", "source": "https://bsky.app/profile/modat-io.bsky.social/post/3mdxqinifn22e", "content": "", "creation_timestamp": "2026-02-03T16:05:55.418432Z"}, {"uuid": "6d1810a9-34fd-4624-91b9-f08a72056ffe", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2026-25253", "type": "seen", "source": "https://gist.github.com/rosieRRRRR/f81a1e2b8ec4b920c27da7c9603178a7", "content": "", "creation_timestamp": "2026-02-18T23:10:00.000000Z"}, {"uuid": "61cbb8ed-78b1-416b-bcf2-8c2d11855a15", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2026-25253", "type": "seen", "source": "https://gist.github.com/vitaliysobur/f447fc26c0787121f1dd7c923623486f", "content": "", "creation_timestamp": "2026-02-21T14:07:01.000000Z"}, {"uuid": "1c527e91-d2cb-4885-8f47-bb124865aa1e", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "cve-2026-25253", "type": "seen", "source": "https://bsky.app/profile/infosecbot.bsky.social/post/3meoko5ewbh2e", "content": "", "creation_timestamp": "2026-02-12T17:52:51.131041Z"}, {"uuid": "9a84bbac-8ee5-48db-ba09-e7ed61199cdd", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2026-25253", "type": "seen", "source": "https://bsky.app/profile/shadowserver.bsky.social/post/3mdxviw4qc22y", "content": "", "creation_timestamp": "2026-02-03T17:35:39.562038Z"}, {"uuid": "04e461a9-e1d8-41de-aca4-3ac3c4e7b416", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2026-25253", "type": "seen", "source": "https://bsky.app/profile/shadowserver.bsky.social/post/3mdxvizt3fk2y", "content": "", "creation_timestamp": "2026-02-03T17:35:40.084033Z"}, {"uuid": "aaea4974-003a-4502-b301-cca70e2f4962", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2026-25253", "type": "seen", "source": "https://gist.github.com/felarof99/a19222cb85eeb1f1b7377829ed81f767", "content": "", "creation_timestamp": "2026-03-09T20:20:37.000000Z"}, {"uuid": "85dd3740-8f1b-4b76-81e1-a9bd7eced1d7", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2026-25253", "type": "seen", "source": "https://bsky.app/profile/shadowserver.bsky.social/post/3mdxvj3s7vs2y", "content": "", "creation_timestamp": "2026-02-03T17:35:40.621403Z"}, {"uuid": "47c01c0c-757c-4e8e-ac8b-9da0e365ab1f", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2026-25253", "type": "seen", "source": "https://infosec.exchange/users/shadowserver/statuses/116007910110549648", "content": "", "creation_timestamp": "2026-02-03T17:37:12.314865Z"}, {"uuid": "1598a83c-1904-4959-a901-e3813be6d0eb", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2026-25253", "type": "seen", "source": "https://gist.github.com/Shu4ya/dc8f1b96e50089c2009cc2466bfd57fa", "content": "", "creation_timestamp": "2026-03-01T19:20:16.000000Z"}, {"uuid": "432d6ec6-4b9a-4344-8376-3f19cac6443c", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2026-25253", "type": "seen", "source": "https://gist.github.com/skalpers/f95a4a272ef2dcbe713610f863143d3b", "content": "", "creation_timestamp": "2026-02-14T11:31:11.000000Z"}, {"uuid": "d107e85b-c964-4722-b0f4-7c6190bd03ec", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2026-25253", "type": "seen", "source": "https://gist.github.com/seansilva-adam-bot/418b7d87a090f5cf89f9abf0cd9121f1", "content": "", "creation_timestamp": "2026-02-10T07:02:01.000000Z"}, {"uuid": "96bdb385-dbff-4842-b4d4-c874170a1782", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2026-25253", "type": "seen", "source": "https://bsky.app/profile/r-blueteamsec.bsky.social/post/3mdxxfpepzn2q", "content": "", "creation_timestamp": "2026-02-03T18:09:32.318603Z"}, {"uuid": "df49aed5-396f-4c30-85b4-5c3bf93f1a79", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2026-25253", "type": "seen", "source": "https://gist.github.com/hdknr/1ddcd07ed2cfe5a9510119208b4376e2", "content": "", "creation_timestamp": "2026-03-03T04:17:17.000000Z"}, {"uuid": "af158579-b167-4617-8d82-f264742e86ed", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "cve-2026-25253", "type": "seen", "source": "https://infosec.exchange/users/threatcodex/statuses/116008221029836755", "content": "", "creation_timestamp": "2026-02-03T18:56:14.861640Z"}, {"uuid": "0677ddf1-fa23-438b-9f56-742d3ca512f6", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2026-25253", "type": "seen", "source": "https://bsky.app/profile/diegopacheco.bsky.social/post/3mdwn6v3da22r", "content": "", "creation_timestamp": "2026-02-03T05:34:08.139351Z"}, {"uuid": "725292b5-2435-497e-a47b-f422e03c76e0", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2026-25253", "type": "seen", "source": "https://bsky.app/profile/beikokucyber.bsky.social/post/3mffjijorh62v", "content": "", "creation_timestamp": "2026-02-21T21:03:04.042392Z"}, {"uuid": "a9c141f7-8888-42c1-b902-22ae557d7731", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2026-25253", "type": "seen", "source": "https://gist.github.com/rollkoffers-gaston/d57e8428a5112213da10c3aa4313434f", "content": "", "creation_timestamp": "2026-02-25T05:08:44.000000Z"}, {"uuid": "80901616-081e-44a8-9712-968ff3c7d4ec", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2026-25253", "type": "seen", "source": "https://bsky.app/profile/toxfox.bsky.social/post/3mgh6m6rrxe2d", "content": "", "creation_timestamp": "2026-03-07T06:18:45.684972Z"}, {"uuid": "8f41d519-7c09-45fe-be3e-7aec5ffe7447", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2026-25253", "type": "seen", "source": "https://bsky.app/profile/toxfox.bsky.social/post/3mgi6whkx562u", "content": "", "creation_timestamp": "2026-03-07T15:57:09.771517Z"}, {"uuid": "453612ae-49af-428d-9199-198cafc9e978", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2026-25253", "type": "seen", "source": "https://gist.github.com/jabisu-sudo/f07537ab4a3d53464ab5d95a8940cbf2", "content": "", "creation_timestamp": "2026-03-10T14:16:29.000000Z"}, {"uuid": "c331c854-66c9-46c5-bc07-a97651d5ca3c", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2026-25253", "type": "seen", "source": "https://bsky.app/profile/pmloik.bsky.social/post/3mfg3oqfvk72w", "content": "", "creation_timestamp": "2026-02-22T02:28:38.675695Z"}, {"uuid": "b9163bc6-858b-436e-9920-f7608162603e", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2026-25253", "type": "seen", "source": "https://bsky.app/profile/toxfox.bsky.social/post/3mgfex4vyb42z", "content": "", "creation_timestamp": "2026-03-06T13:06:55.553102Z"}, {"uuid": "cab9a9fb-0a67-40eb-957a-236e646c0ca6", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2026-25253", "type": "seen", "source": "https://bsky.app/profile/thehackerwire.bsky.social/post/3mdtht7p7ts2r", "content": "", "creation_timestamp": "2026-02-01T23:20:07.703766Z"}, {"uuid": "2e332f02-f067-4cc9-8d61-0cfa8746d86e", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2026-25253", "type": "seen", "source": "https://bsky.app/profile/thehackerwire.bsky.social/post/3mdthtljmds2h", "content": "", "creation_timestamp": "2026-02-01T23:20:19.618205Z"}, {"uuid": "41c1405d-c87c-4ca0-8b5a-c1f2304b69fb", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2026-25253", "type": "seen", "source": "https://bsky.app/profile/opsmatters.com/post/3me3gk3beax23", "content": "", "creation_timestamp": "2026-02-05T03:18:24.277194Z"}, {"uuid": "91445d9d-d843-4cee-a311-14e1e5e1768e", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2026-25253", "type": "seen", "source": "https://bsky.app/profile/opsmatters.com/post/3mdyubbbyab22", "content": "", "creation_timestamp": "2026-02-04T02:46:01.842578Z"}, {"uuid": "c48353ea-6360-405a-a0a0-83f664ee4782", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2026-25253", "type": "seen", "source": "https://bsky.app/profile/briskinfosec.bsky.social/post/3mdz7shrquc2i", "content": "", "creation_timestamp": "2026-02-04T06:12:45.991696Z"}, {"uuid": "2adfe3cc-5ff0-49c9-95de-60b8fad26705", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2026-25253", "type": "seen", "source": "https://bsky.app/profile/0xacb.com/post/3mduinj5aaj23", "content": "", "creation_timestamp": "2026-02-02T09:07:29.784917Z"}, {"uuid": "bd6a9fd6-471c-4859-93ce-5ab30d61a172", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2026-25253", "type": "seen", "source": "https://bsky.app/profile/toxfox.bsky.social/post/3mgirjqvsxy2o", "content": "", "creation_timestamp": "2026-03-07T21:30:05.988114Z"}, {"uuid": "cfb63a04-cbb6-44ff-8fc5-b72821835cac", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2026-25253", "type": "seen", "source": "https://bsky.app/profile/pmloik.bsky.social/post/3mfxoxwyp2j2p", "content": "", "creation_timestamp": "2026-03-01T02:29:07.669029Z"}, {"uuid": "04b89433-81f2-490b-9888-0e119c911ce4", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2026-25253", "type": "seen", "source": "https://bsky.app/profile/infosec.skyfleet.blue/post/3meybweazny2i", "content": "", "creation_timestamp": "2026-02-16T14:42:59.958176Z"}, {"uuid": "57c325be-fde6-4432-aa32-908172f13969", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2026-25253", "type": "seen", "source": "https://bsky.app/profile/pmloik.bsky.social/post/3mfv6h5jeby2p", "content": "", "creation_timestamp": "2026-02-28T02:28:01.023660Z"}, {"uuid": "24fc5ca6-4af0-47d0-bbe3-4a5cfbf26160", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2026-25253", "type": "seen", "source": "https://bsky.app/profile/index.cms.1900.live.ap.brid.gy/post/3mefynrvdjg42", "content": "", "creation_timestamp": "2026-02-09T08:09:17.917925Z"}, {"uuid": "c5607577-bf62-4472-a054-d16d43ea381e", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2026-25253", "type": "seen", "source": "https://bsky.app/profile/linkeaz.net/post/3mfoonwpsys2x", "content": "", "creation_timestamp": "2026-02-25T12:29:35.194966Z"}, {"uuid": "578af6e3-1496-4d50-8879-59d92da00d2e", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2026-25253", "type": "seen", "source": "https://gist.github.com/rollkoffers-gaston/a44ec95b645c04e6a8384e40379aa2dd", "content": "", "creation_timestamp": "2026-02-20T07:11:19.000000Z"}, {"uuid": "3758c0be-d26b-4a9a-abcc-992d9ad2ca80", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2026-25253", "type": "seen", "source": "https://bsky.app/profile/linkeaz.net/post/3mfoozsyhic2x", "content": "", "creation_timestamp": "2026-02-25T12:36:14.289141Z"}, {"uuid": "38977246-f016-4350-873c-a9985e3bd480", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2026-25253", "type": "seen", "source": "https://bsky.app/profile/toxfox.bsky.social/post/3mgfzom24yb2k", "content": "", "creation_timestamp": "2026-03-06T19:17:57.793297Z"}, {"uuid": "526f5788-62c8-4072-abdb-b5d7375e415f", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2026-25253", "type": "seen", "source": "https://bsky.app/profile/polyarushseo.com/post/3mfe7ldago22x", "content": "", "creation_timestamp": "2026-02-21T08:33:00.007210Z"}, {"uuid": "5d2a541a-da49-4a4e-95c6-dd947cc4c08f", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2026-25253", "type": "seen", "source": "https://bsky.app/profile/polyarushseo.com/post/3mfe7ldaphc2x", "content": "", "creation_timestamp": "2026-02-21T08:33:00.552536Z"}, {"uuid": "35dc7be9-6417-48fb-95cd-7d78c2a78bd5", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2026-25253", "type": "seen", "source": "https://bsky.app/profile/polyarushseo.com/post/3mfe7ldaqgk2x", "content": "", "creation_timestamp": "2026-02-21T08:33:01.094704Z"}, {"uuid": "a31d1f51-038f-43ad-847f-30cc4c2623bf", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2026-25253", "type": "seen", "source": "https://bsky.app/profile/polyarushseo.com/post/3mfe7ldaqgl2x", "content": "", "creation_timestamp": "2026-02-21T08:33:01.633404Z"}, {"uuid": "c9ca158a-5b4f-4e1a-864b-68a834ca472a", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2026-25253", "type": "seen", "source": "https://bsky.app/profile/polyarushseo.com/post/3mfe7ldarft2x", "content": "", "creation_timestamp": "2026-02-21T08:33:02.253298Z"}, {"uuid": "a25cbc8c-6c5b-45ff-a99b-cb8256a3e836", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2026-25253", "type": "seen", "source": "https://bsky.app/profile/polyarushseo.com/post/3mfe7ldarfu2x", "content": "", "creation_timestamp": "2026-02-21T08:33:02.820379Z"}, {"uuid": "b2a46aa7-404c-4ee6-b177-a7e8e47f6bf5", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2026-25253", "type": "seen", "source": "https://bsky.app/profile/polyarushseo.com/post/3mfe7ldasf42x", "content": "", "creation_timestamp": "2026-02-21T08:33:03.351193Z"}, {"uuid": "61d754e4-66d5-40e8-ba59-c617e44f7ece", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2026-25253", "type": "seen", "source": "https://gist.github.com/rollkoffers-gaston/12359e853efd736fe1a59b8222176993", "content": "", "creation_timestamp": "2026-02-20T09:34:06.000000Z"}, {"uuid": "546d6ac0-a9f6-4985-923e-bd210702af15", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2026-25253", "type": "seen", "source": "https://bsky.app/profile/justin-salmini.bsky.social/post/3mgakhkjerg2j", "content": "", "creation_timestamp": "2026-03-04T15:02:16.651943Z"}, {"uuid": "5966de56-8d90-4e52-bd7a-c8146d271491", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2026-25253", "type": "seen", "source": "https://bsky.app/profile/callmenoble6.bsky.social/post/3mfgwg4ylmk2m", "content": "", "creation_timestamp": "2026-02-22T10:27:05.647611Z"}, {"uuid": "9fa1915a-57e3-4fa2-bdb0-0b809f92352b", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2026-25253", "type": "seen", "source": "https://bsky.app/profile/pigondrugs.bsky.social/post/3mf32fye3sb2h", "content": "", "creation_timestamp": "2026-02-17T17:06:34.098579Z"}, {"uuid": "fbe780d2-8953-42ec-93c8-bc462607d357", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2026-25253", "type": "seen", "source": "https://bsky.app/profile/e-kiledjian.bsky.social/post/3mftpj3hrs22c", "content": "", "creation_timestamp": "2026-02-27T12:28:00.950729Z"}, {"uuid": "1b81cc13-e80f-4ec6-9b4b-c3a8f0fb38df", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2026-25253", "type": "seen", "source": "https://bsky.app/profile/pmloik.bsky.social/post/3mfim5vstw22p", "content": "", "creation_timestamp": "2026-02-23T02:28:46.878076Z"}, {"uuid": "b61881e5-96a3-40a2-89c1-f1611eb9d1c5", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2026-25253", "type": "seen", "source": "https://bsky.app/profile/codepo8.bsky.social/post/3me4t5cz7is2p", "content": "", "creation_timestamp": "2026-02-05T16:36:38.955019Z"}, {"uuid": "b66d6359-92d6-47e6-bc01-9a5526bd4f9a", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2026-25253", "type": "seen", "source": "https://threatintel.cc/2026/02/27/your-personal-openclaw-agent-may.html", "content": "", "creation_timestamp": "2026-02-27T11:27:30.000000Z"}, {"uuid": "72d5f481-ae5f-42cc-842b-e4607155158a", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2026-25253", "type": "seen", "source": "https://bsky.app/profile/pigondrugs.bsky.social/post/3mf5unf2nlw2k", "content": "", "creation_timestamp": "2026-02-18T20:01:18.995991Z"}, {"uuid": "58166224-49d6-4c3a-bc93-50426bf3a30c", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2026-25253", "type": "seen", "source": "https://bsky.app/profile/undercode.bsky.social/post/3mewg2s5xcs2r", "content": "", "creation_timestamp": "2026-02-15T20:51:45.316529Z"}, {"uuid": "cfc35311-6076-4119-baac-b5e289c5ef97", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2026-25253", "type": "seen", "source": "https://bsky.app/profile/dailyqiitatrends.bsky.social/post/3mewlrmm2cd22", "content": "", "creation_timestamp": "2026-02-15T22:33:59.777621Z"}, {"uuid": "74e739dd-1943-4806-966b-df09552f1f6e", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2026-25253", "type": "seen", "source": "https://bsky.app/profile/johnios.bsky.social/post/3mhlxiy6djs2c", "content": "", "creation_timestamp": "2026-03-21T21:20:11.886836Z"}, {"uuid": "c6217e6d-113a-4acf-9506-3ae77879ffbc", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2026-25253", "type": "seen", "source": "https://gist.github.com/changfamilyai/fef1cfb3233902dd0acbbe58b6cc1e00", "content": "", "creation_timestamp": "2026-03-14T05:14:15.000000Z"}, {"uuid": "22edd896-7651-4614-a21e-2d7ae4231144", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2026-25253", "type": "seen", "source": "https://bsky.app/profile/printy.margin.cafe/post/3mhmahtdwko27", "content": "", "creation_timestamp": "2026-03-22T00:00:37.494764Z"}, {"uuid": "26d07026-a5c4-42e8-86d1-8696ee551c99", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2026-25253", "type": "seen", "source": "https://gist.github.com/ksssshy-cloud/b5254fddc2c8ff5ec1115b800583e544", "content": "", "creation_timestamp": "2026-03-12T23:26:09.000000Z"}, {"uuid": "a5b44a21-4fd6-4bc8-97f2-f8a9d4e022c7", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2026-25253", "type": "seen", "source": "https://gist.github.com/ksssshy-cloud/d9234f17bd9b1a08af64f9233128d0ff", "content": "", "creation_timestamp": "2026-03-12T23:46:56.000000Z"}, {"uuid": "85e2eaad-8f8c-4a61-afc0-e6c6236e7229", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "cve-2026-25253", "type": "seen", "source": "https://bsky.app/profile/toxfox.bsky.social/post/3mhr3dj7x6w2p", "content": "", "creation_timestamp": "2026-03-23T22:12:02.113261Z"}, {"uuid": "69f1e1fd-2411-43b7-8ce7-2dcf2666e865", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "cve-2026-25253", "type": "seen", "source": "https://bsky.app/profile/flarestart.bsky.social/post/3mhr4wkiulb2r", "content": "", "creation_timestamp": "2026-03-23T22:40:35.690517Z"}, {"uuid": "198eb700-c569-4605-9993-10e11b633933", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "cve-2026-25253", "type": "seen", "source": "https://bsky.app/profile/flarestart.bsky.social/post/3mhr57j4bwj2r", "content": "", "creation_timestamp": "2026-03-23T22:45:35.520702Z"}, {"uuid": "ab1614cb-484a-46a2-9b21-7194882c4974", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "cve-2026-25253", "type": "seen", "source": "https://bsky.app/profile/cyberhub.blog/post/3mhuetq4tyo2v", "content": "", "creation_timestamp": "2026-03-25T05:40:08.968559Z"}, {"uuid": "2b34bbad-fb98-49b6-9464-5af68adbd292", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2026-25253", "type": "seen", "source": "https://bsky.app/profile/r-netsec-bot.bsky.social/post/3mhqal75app2q", "content": "", "creation_timestamp": "2026-03-23T14:13:08.995562Z"}, {"uuid": "b3aef213-9d18-4a2c-b397-62105f49bda9", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2026-25253", "type": "seen", "source": "https://bsky.app/profile/jmavie.bsky.social/post/3mhq63yn6kc2p", "content": "", "creation_timestamp": "2026-03-23T13:28:52.568094Z"}, {"uuid": "ed207d28-ff39-4be8-903a-ca754ab0d3f6", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2026-25253", "type": "seen", "source": "https://bsky.app/profile/jmavie.bsky.social/post/3mhq63ynlak2p", "content": "", "creation_timestamp": "2026-03-23T13:28:53.126866Z"}, {"uuid": "87e4483e-7ee6-4737-a04e-b814b342c9f7", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2026-25253", "type": "seen", "source": "https://bsky.app/profile/jmavie.bsky.social/post/3mhq63ynq4s2p", "content": "", "creation_timestamp": "2026-03-23T13:28:53.693347Z"}, {"uuid": "ff730ac3-40cf-4fa5-b6dd-d40eaa0e84dc", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2026-25253", "type": "seen", "source": "https://bsky.app/profile/jmavie.bsky.social/post/3mhq63znrjc2p", "content": "", "creation_timestamp": "2026-03-23T13:28:55.062921Z"}, {"uuid": "b7caea2f-57bf-433d-a105-4c31b23a63b5", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2026-25253", "type": "seen", "source": "https://bsky.app/profile/jmavie.bsky.social/post/3mhq63znths2p", "content": "", "creation_timestamp": "2026-03-23T13:28:55.686286Z"}, {"uuid": "6241ccda-6d7e-4a90-8d0f-85e36b5ee6d5", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2026-25253", "type": "seen", "source": "https://bsky.app/profile/jmavie.bsky.social/post/3mhq63zntht2p", "content": "", "creation_timestamp": "2026-03-23T13:28:56.226899Z"}, {"uuid": "ac1eddcb-f777-44a6-a24f-08127a0bf77f", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2026-25253", "type": "seen", "source": "https://bsky.app/profile/jmavie.bsky.social/post/3mhq63znthu2p", "content": "", "creation_timestamp": "2026-03-23T13:29:00.195656Z"}, {"uuid": "7fba5df4-6c53-4055-a952-1004a86e2f23", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2026-25253", "type": "seen", "source": "https://bsky.app/profile/jmavie.bsky.social/post/3mhq63znuh42p", "content": "", "creation_timestamp": "2026-03-23T13:29:00.758809Z"}, {"uuid": "bf6b3bfc-d2a3-4ffb-8536-2f5ff1201ecd", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2026-25253", "type": "seen", "source": "https://bsky.app/profile/r-netsec.bsky.social/post/3mhqdq3f63i2l", "content": "", "creation_timestamp": "2026-03-23T15:09:33.871022Z"}, {"uuid": "5cf99afb-08ad-4082-a448-c85e1e3e06a8", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2026-25253", "type": "seen", "source": "https://bsky.app/profile/agent-tsumugi.bsky.social/post/3mjckzqii7n25", "content": "", "creation_timestamp": "2026-04-12T14:33:21.192312Z"}, {"uuid": "f938419e-9ba2-42dd-bad1-b6d300393ca8", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2026-25253", "type": "seen", "source": "https://bsky.app/profile/hasamba72.bsky.social/post/3mjfbvatyg52p", "content": "", "creation_timestamp": "2026-04-13T16:27:46.491810Z"}, {"uuid": "58905808-6920-4f01-8dea-659ab69b08ba", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2026-25253", "type": "seen", "source": "https://github.blog/security/hack-the-ai-agent-build-agentic-ai-security-skills-with-the-github-secure-code-game/", "content": "", "creation_timestamp": "2026-04-14T16:17:59.000000Z"}, {"uuid": "050ff7e3-6536-4a9b-a7a4-e128a1d1abc3", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2026-25253", "type": "seen", "source": "https://t.me/GithubRedTeam/79480", "content": "\ud83d\udea8 GitHub \u76d1\u63a7\u6d88\u606f\u63d0\u9192\n\n\ud83d\udea8 \u53d1\u73b0\u5173\u952e\u8bcd\uff1a #CVE-2026\n\n\ud83d\udce6 \u9879\u76ee\u540d\u79f0\uff1a start-here\n\ud83d\udc64 \u9879\u76ee\u4f5c\u8005\uff1a msaleme\n\ud83d\udee0 \u5f00\u53d1\u8bed\u8a00\uff1a None\n\u2b50 Star\u6570\u91cf\uff1a 0  |  \ud83c\udf74 Fork\u6570\u91cf\uff1a 0\n\ud83d\udcc5 \u66f4\u65b0\u65f6\u95f4\uff1a 2026-04-08 21:55:56\n\n\ud83d\udcdd \u9879\u76ee\u63cf\u8ff0\uff1a\nMichael Saleme \u2014 Decision Governance for Autonomous Agents. 5 DOIs, 3 NIST submissions, CVE-2026-25253, 358 security tests.\n\n\ud83d\udd17 \u70b9\u51fb\u8bbf\u95ee\u9879\u76ee\u5730\u5740", "creation_timestamp": "2026-04-08T22:00:04.000000Z"}, {"uuid": "71296ab0-62f2-454d-9d2c-16ad5c49f79e", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2026-25253", "type": "published-proof-of-concept", "source": "Telegram/O7yR2b4OLQp6kid0WdGHPQvQVIbLyZOFm8IdlAgSGDL0FUM", "content": "", "creation_timestamp": "2026-04-18T15:00:07.000000Z"}, {"uuid": "cb4c415c-b32c-45b6-a681-c889a6d5fd32", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2026-25253", "type": "seen", "source": "https://gist.github.com/iamalvisng/cec5751e8a7d57e4c0838f280dab962e", "content": "# The claim ledger \u2014 companion to \"The Best Lines Were the Wrong Ones\"\n\nA claim-by-claim fact-check of a one-hour Cantonese-language podcast interview about AI (the speaker stays unnamed; the point was never him). Every checkable assertion was pulled from a cleaned English transcript, verified against the best available source, and graded. High-stakes claims (specific numbers, named-entity actions, direct quotes) got a second, adversarial pass whose only job was to break them.\n\n**Source-quality tiers:** t1 = primary/official (the org itself, papers, regulators, official statistics) \u00b7 t2 = reputable secondary (established press, named analysts) \u00b7 t3 = single blog / aggregator, directional only.\n\n**Verdicts:** SUPPORTED \u00b7 MISSTATED (a source exists but says something materially different) \u00b7 UNSUPPORTED (no credible source found) \u00b7 NEEDS-SOURCE (plausible but uncited).\n\n&gt; **Correction (2026-08-04), left visible on purpose:** this ledger's original summary line said \"52 claims checked, 30 supported, 12 misstated, 7 unsupported, 3 needs-source.\" The table below has **64 numbered rows**. By row count: **12 MISSTATED, 8 UNSUPPORTED, 1 clean NEEDS-SOURCE (+2 hybrid), ~43 SUPPORTED with varying hedges.** The summary line was a compression that failed its own file \u2014 which became the second half of the essay this ledger accompanies. Cite the table, not summaries. Including this one.\n\n---\n\n## AI history\n\n| # | Claim | Verdict | Best source (tier) | Evidence / correction |\n|---|---|---|---|---|\n| 1 | GPT-3 released 2020 | SUPPORTED | arXiv 2005.14165 (t1) | Preprint 28 May 2020; API beta 11 June 2020 |\n| 2 | GPT-3 &gt;100x larger than GPT-2 | SUPPORTED | OpenAI paper (t1/t2) | \"over two orders of magnitude\" \u2014 175B vs 1.5B \u2248 117x |\n| 3 | ChatGPT launched Nov 2022, not Nov 2023 | SUPPORTED | openai.com/index/chatgpt (t1) | 30 Nov 2022. The transcript's \"Nov 2023\" was a speech-recognition/speaker error |\n| 4 | ~40 human contractors for early RLHF | SUPPORTED | Ouyang et al., InstructGPT (t1) | \"a team of about 40 contractors\" via Upwork and ScaleAI |\n| 5 | OpenAI never disclosed the GPT-3.5 labeler count | MISSTATED | InstructGPT paper (t1) | It *was* disclosed \u2014 ChatGPT is OpenAI's \"sibling model\" to InstructGPT, same method. Correct framing: not separately re-disclosed for ChatGPT |\n| 6 | Transformer came out of machine translation | SUPPORTED | arXiv 1706.03762 (t1) | Paper frames the Transformer against RNN translation quality/parallelization limits |\n| 7 | GPT-1/2 had almost no impact; GPT-3 first real influence | SUPPORTED (overstated) | TechTarget (t2) | GPT-2 did get real attention via the \"too dangerous to release\" controversy. GPT-3 was the commercial inflection |\n| 8 | Distillation + AI eval is the *main driver* of the narrowing gap | UNSUPPORTED as stated | Epoch AI (t1) | Real techniques, but no source names them the main driver. Compute efficiency, post-training recipes and competitive pressure cited more often |\n| 9 | Closed/open gap now ~6 months | MISSTATED | Epoch AI open-closed ECI gap (t1) | \"an average of four months\" (Jan\u2013May 2026). Six months is stale \u2014 the 2025 figure |\n| 10 | DeepSeek compressed the release cadence | SUPPORTED directionally; causation NEEDS-SOURCE | industry retrospective (t3) | Cadence did compress after DeepSeek R1 (Jan 2025) \u2014 6\u20139 month cycles to a 4\u20136 week competitive floor \u2014 but sources describe multi-lab dynamics, not isolated DeepSeek causation |\n\n## Money\n\n| # | Claim | Verdict | Best source (tier) | Evidence / correction |\n|---|---|---|---|---|\n| 11 | Anthropic ~$14B by Feb 2026 | SUPPORTED | Anthropic official (t1) | \"Our run-rate revenue is $14 billion, and has grown over 10x in each of the past 3 years\" |\n| 12 | Anthropic grew ~12x | MISSTATED | Anthropic official (t1) | Anthropic's own wording is \"over 10x\" per year. No official 12x figure |\n| 13 | OpenAI $2B \u2192 $20B by Feb 2026 | MISSTATED | OpenAI CFO disclosure via Epoch AI (t2) | Actual: $2B (2023) \u2192 $6B (2024) \u2192 $20B+ (2025) \u2192 ~$25B by Feb 2026. The \"20 months earlier\" framing is wrong |\n| 14 | 2026 AI capex \u2248 one year of US military spending | SUPPORTED, order-of-magnitude only | Futurum (t2/t3) + CBO (t1) | ~$1.04T both sides \u2014 but only on the broadest AI definition (hyperscalers + Oracle + neoclouds + sovereign + China). Big-Five-only is $660\u2013725B, ~two-thirds |\n| 15 | Most lab revenue is B2B, not consumer | SUPPORTED with caveat | Forbes (t2) | True for Anthropic (~80% API). OpenAI is closer to 50/50 by mid-2026 |\n| 16 | Jensen Huang's \"five-layer cake\" | SUPPORTED | NVIDIA blog (t1), Forbes (t2) | Davos 2026. Layers: energy, chips, infrastructure, models, applications |\n| 17 | Google trains on its own TPUs, not Nvidia | SUPPORTED | The Conversation (t2) | \"All phases of Gemini 3 training ran on Google-made TPU v5e and v6e pods without fallback to Nvidia GPUs\" |\n\n## Rankings and usage\n\n*(This whole block leans on tier-3 aggregators. Treat as directional.)*\n\n| # | Claim | Verdict | Best source (tier) | Evidence / correction |\n|---|---|---|---|---|\n| 18 | ChatGPT still #1 on mobile and web | SUPPORTED with nuance | TechCrunch (t2) | 53.9% of worldwide web visits vs Gemini 27.9%, Claude 9.2% \u2014 but share fell below 50% for the first time in June 2026; Gemini +450% YoY, Claude +855% YoY |\n| 19 | Big four = OpenAI, Anthropic, Google, xAI; Meta \"constrained\" | MISSTATED | capex trackers (t3), SemiAnalysis (t2) | Depends entirely on the metric. By capex Meta is ~$125B in 2026, third among hyperscalers \u2014 not capital-constrained. Its constraint is talent/model quality |\n| 20 | Doubao is China's strongest model | UNSUPPORTED | OpenCompass rankings via aggregators (t3) | No single Chinese model leads mid-2026. Qwen3-Max leads LiveBench/Arena-Hard, DeepSeek-V4-Pro tops aggregate coding, GLM-5.2 leads long-horizon agent tasks, Ernie 5.1 topped LMArena preference. Doubao is top-4-ish |\n| 21 | Doubao's top model is closed-weight | SUPPORTED (first half) | Doubao model docs (t3) | Closed-weight is correct. \"Stronger than the open models\" is not \u2014 see #20 |\n| 22 | Ranking: DeepSeek &gt; GLM &gt; Qwen &gt; Ernie &gt; MiniMax/Moonshot | UNSUPPORTED | multiple comparisons (t3) | No source supports this fixed hierarchy. Benchmark-dependent and contested |\n| 23 | GLM/Zhipu came out of Tsinghua | SUPPORTED | (t3, consistent across sources) | Spun out of Tsinghua's Knowledge Engineering Group (THUDM), 2019 |\n| 24 | DeepSeek, GLM, Qwen ship open weights | SUPPORTED | (t3) | All three, as of mid-2026 |\n| 25 | DeepSeek got famous by open-sourcing, investment followed | SUPPORTED | CSET (t1-adjacent), IISS (t2) | \"turning DeepSeek from a little-known research team into China's best-known AI company almost overnight\" |\n| 26 | Western labs rarely open their strongest weights | SUPPORTED with exceptions | OpenAI help center (t1), The Register (t2) | Real exceptions: gpt-oss-120b/20b (Aug 2025), Gemma 4 (Apr 2026). But GPT-5.x and Gemini 3 stay closed \u2014 holds for *strongest* |\n\n## Power and infrastructure\n\n| # | Claim | Verdict | Best source (tier) | Evidence / correction |\n|---|---|---|---|---|\n| 27 | China's power ~3x the US by 2027 | **MISSTATED** | Ember via Visual Capitalist (t2 from t1 data) | \"China generated 10,087 TWh of electricity in 2024, while the U.S. generated 4,635 TWh\" \u2014 ~2.2:1, trending to ~2.4\u20132.5:1 by 2027. Correct phrasing: \"more than double, and widening\" |\n| 28 | US has essentially nothing under construction | **UNSUPPORTED** | Rabobank/Wood Mackenzie (t2) | US builds ~40 GW/yr, needs ~80 GW/yr. Accurate version: \"building at about half the needed rate, far below China's scale\" |\n| 29 | Musk/Google proposed space data centers, power the driver | SUPPORTED | DataCenterDynamics, MIT Tech Review (t2) | Musk: \"you're power constrained on Earth\". SpaceX filed with the FCC; Google's Project Suncatcher targets two prototype satellites by early 2027. (The Musk quote could not be fetched directly \u2014 403 \u2014 treat as reported) |\n| 30 | US demand flat partly due to offshoring | SUPPORTED with nuance | EIA (t1) | \"U.S. electricity consumption was essentially flat for nearly two decades.\" EIA attributes this to efficiency + the manufacturing-to-services shift; offshoring is a widely-cited secondary attribution, not EIA's own wording |\n| 31 | Orbital data centers have an unsolved heat problem | SUPPORTED | IEEE Spectrum, 1-ACT (t2/t1) | Radiative rejection only: ~1,200 m\u00b2 of radiator to shed 1 MW; a single 700 W chip needs ~1.4 m\u00b2 |\n| 32 | Power is the binding constraint; demand will exceed supply | SUPPORTED | Gartner, IEA, Uptime (t2 from t1) | Gartner: 40% of AI data centers power-constrained by 2027. Global DC consumption +26% in 2026 to 565 TWh |\n| 33 | Musk timelines slip 3\u20135x | SUPPORTED directionally, figure UNSOURCED | prediction trackers (t3) | Of 20 tracked predictions: 4 delivered, 5 partial, 9 clearly missed. The \"3\u20135x\" multiplier is not a measured statistic anywhere \u2014 the speaker's rule of thumb |\n| 34 | GPU supply + power are the bottleneck, not architecture | MISSTATED (half) | industry analyses (t3) | By mid-2026, GPU supply is no longer primary \u2014 CoWoS capacity doubled in 2025 and again through 2026. Power is now the sole primary constraint |\n\n## Agents and OpenClaw\n\n| # | Claim | Verdict | Best source (tier) | Evidence / correction |\n|---|---|---|---|---|\n| 35 | OpenClaw is real, open-source, viral | SUPPORTED | openclaw.ai (t1), DigitalOcean (t2) | Peter Steinberger, launched Nov 2025 as \"Clawdbot\", most-starred repo on GitHub (346k+ stars) in under five months. Viral peak was Q1 2026, not mid-2026 |\n| 36 | Huang called it the most important software ever shipped | SUPPORTED | CNBC, HPCwire (t2) | Morgan Stanley TMT Conference, March 2026: \"probably the single most important release of software... probably ever\" |\n| 37 | One person, AI-assisted, no monetization | SUPPORTED | Euronews (t2) | Steinberger: \"It's a free, open source hobby project.\" MIT license. (He has since joined OpenAI, Feb 2026 \u2014 not mentioned by the speaker) |\n| 38 | Major publicized security holes from broad access | SUPPORTED | Dark Reading, Barracuda (t2) | \"ClawJacked\" website-driven hijack; CVE-2026-25253, one-click RCE; tens of thousands of internet-facing instances exposed |\n| 39 | Connects WhatsApp/Telegram, messages you proactively | SUPPORTED with nuance | OpenClaw docs (t1) | `post_message` tool. Proactive posting is gated to scheduled cron/heartbeat, not arbitrary spontaneity |\n| 40 | Persistent \"soul\" file that accumulates history | SUPPORTED | OpenClaw docs (t1) | `SOUL.md`, read at startup and injected as a system-level prompt |\n| 41 | Tencent's Shenzhen install event was overrun | SUPPORTED, understated | SCMP (t2) | \"Nearly 1,000 people lined up outside... Tencent Holdings' Shenzhen headquarters\" \u2014 20 staff installing free, 6 March 2026 |\n| 42 | Major AI companies issued a joint statement | **UNSUPPORTED** | \u2014 | No joint statement found. Individual industry responses and OWASP's Top 10 for Agentic Applications exist |\n| 43 | Chinese giants incl. Xiaomi shipped their own | SUPPORTED | Yicai Global, CNBC (t2) | Xiaomi's MiClaw, Honor's Yoyo, Huawei's Xiaoyi; Zhipu, ByteDance, Tencent + 10 other giants |\n| 44 | GPT-4o sycophancy update rolled back after safety objections | SUPPORTED | openai.com/index/sycophancy-in-gpt-4o (t1) | Update 25 April 2025; rollback began 28 April 2025 |\n| 45 | GPT-5 trained to decline over fabricating; less personable | SUPPORTED | (t3) | Real and widely reported personality controversy; direction is right |\n| 46 | Claude's first agent shipped with 26 tools | **NEEDS-SOURCE** | \u2014 | No source found for 26 at any first agent release. Computer Use shipped ~3 (computer, text_editor, bash); Claude Code has ~15+ built-ins |\n| 47 | Tool-use benchmarks exist | SUPPORTED | (t3) | BFCL (Berkeley Function-Calling Leaderboard, v4 as of Apr 2026), \u03c4-bench, ToolBench |\n| 48 | Official 2025 guidance said don't let agents book flights | **UNSUPPORTED** | \u2014 | Not found. Likely conflated with DOT statements on airline AI *pricing* \u2014 a different story |\n| 49 | Agents still fail at flight booking | SUPPORTED, imprecise | tau-bench (t1), Tech Times (t2) | ~56% task success on tau-bench Airline \u2014 coin-flip, not \"never\". Agents reached airline sites directly only ~5% of the time |\n\n## Safety, history, economics\n\n| # | Claim | Verdict | Best source (tier) | Evidence / correction |\n|---|---|---|---|---|\n| 50 | German unemployment 5% (1929) \u2192 29% (1933) fueled the Nazis | SUPPORTED as rounding | Nuffield paper (t1) | Registered unemployment ~4.5% (1929) \u2192 peak ~30% in 1932, ~6M in early 1933. Peak year is 1932, not 1933 |\n| 51 | Hinton, Sutskever, Musk all warned of extinction risk | SUPPORTED with nuance | CAIS statement (t1) | Hinton and Sutskever signed the May 2023 CAIS statement. Musk signed the separate FLI pause letter, not CAIS |\n| 52 | Musk funded OpenAI; it began as a nonprofit | SUPPORTED | CNBC (t2) | Launched 11 Dec 2015 as a nonprofit research lab |\n| 53 | Musk broke with Larry Page over AI safety, motivating OpenAI | SUPPORTED as *Musk's account* | court testimony reporting (t2/t3) | Sworn self-report, not corroborated by Page. Attribute, don't assert |\n| 54 | Anthropic's founders left OpenAI over safety | SUPPORTED | (t2/t3) | Standard account; follows the 2019 Microsoft deal |\n| 55 | A safety lead quit a major lab in early 2026 over safety | SUPPORTED | AP wire (t2) | Mrinank Sharma, Anthropic, effective 9 Feb 2026: \"a confession of futility... the pressures arrayed against safety were winning\" |\n| 56 | Reid Hoffman: market models lag internal by 12\u201318 months | **UNSUPPORTED** | \u2014 | No transcript or article found. Appears to be a floating industry talking point mis-attributed |\n| 57 | LeCun says LLMs alone won't get there; nobody has rebutted him | MISSTATED (second half) | Brown University (t1) | First half accurate. Second half false \u2014 Sutskever, Amodei, Altman and Meta's own leadership publicly disagree; the scaling-focused reorg reportedly contributed to LeCun leaving Meta in Nov 2025 |\n| 58 | Harari's \"useless class\" | SUPPORTED | *Homo Deus* (t1) | Correct attribution |\n| 59 | YouTube took ~10 years to produce full-time creators | MISSTATED | (t2/t3) | Partner Program launched Dec 2007; some creators over $100k/yr within a year; full-time creators as a category by ~2010\u20132013. Closer to 5\u20137 years |\n| 60 | AI coding crossed a step change in Q3 2025 | MISSTATED | (t3) | No source pins Q3 2025. Commentary points to late-2024 and late-2025 milestones and gradual growth with humans in the loop |\n| 61 | Japanese perfume founder's AI poster went viral | **UNSUPPORTED** | \u2014 | Not found. Nearest real story is an AI-generated Iwate Prefecture tourism poster controversy |\n| 62 | California has advanced AI safety legislation | SUPPORTED | CA Legislature (t1), FPF (t2) | SB 53, Transparency in Frontier Artificial Intelligence Act \u2014 signed 29 Sept 2025, in force 1 Jan 2026, applies above 10^26 FLOPs. Already law, not merely \"advanced\" |\n| 63 | US corporations are legally obliged to maximize shareholder returns | **MISSTATED** | Stanford Law (t1), Harvard Corp Gov Forum (t2) | The classic legal myth. *Dodge v. Ford* (1919, Michigan, closely-held) is \"mere dicta\"; Delaware courts have never cited it on corporate purpose. Directors have broad discretion under the business judgment rule |\n| 64 | Ukraine is largely AI vs AI, humans nearly absent | **MISSTATED** | CSIS (t2), IEEE Spectrum (t2) | \"most autonomous systems remain 'human-in-the-loop' rather than fully autonomous\". AI does terminal guidance, GPS-denied navigation, target recognition. Humans plan, launch and usually confirm strikes |\n\n---\n\n## Not checked, on purpose\n\nThe speaker's first-person business claims \u2014 his monthly AI spend, his former company's headcount, project timelines before and after AI, two hiring anecdotes. Only he can confirm these. They are plausible and internally consistent, but they are **testimony, not evidence** \u2014 and, as the essay notes, they are also the one section where nothing could fail.\n", "creation_timestamp": "2026-08-04T15:51:21.179913Z"}, {"uuid": "35daf97c-5e17-4f40-bb52-53538440044d", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2026-25253", "type": "seen", "source": "https://poliverso.org/objects/0477a01e-e8c8129d-b09e02c4de9c4f4a", "content": "Exploits and vulnerabilities in Q1 2026\nDuring Q1 2026, the exploit kits leveraged by threat actors to target user systems expanded once again, incorporating new exploits for the Microsoft Office platform, as well as Windows and Linux operating systems.\nIn this report, we dive into the statistics on published vulnerabilities and exploits, as well as the known vulnerabilities leveraged by popular C2 frameworks throughout Q1 2026.\nStatistics on registered vulnerabilities\nThis section provides statistical data on registered vulnerabilities. The data is sourced from cve.org.\nWe examine the number of registered CVEs for each month starting from January 2022. The total volume of vulnerabilities continues rising and, according to current reports, the use of AI agents for discovering security issues is expected to further reinforce this upward trend.\nTotal published vulnerabilities per month from 2022 through 2026 (download)\nNext, we analyze the number of new critical vulnerabilities (CVSS &gt; 8.9) over the same period.\nTotal critical vulnerabilities published per month from 2022 through 2026 (download)\nThe graph indicates that while the volume of critical vulnerabilities slightly decreased compared to previous years, an upward trend remained clearly visible. At present, we attribute this to the fact that the end of last year was marked by the disclosure of several severe vulnerabilities in web frameworks. The current growth is driven by high-profile issues like React2Shell, the release of exploit frameworks for mobile platforms, and the uncovering of secondary vulnerabilities during the remediation of previously discovered ones. We will be able to test this hypothesis in the next quarter; if correct, the second quarter will show a significant decline, similar to the pattern observed in the previous year.\nExploitation statistics\nThis section presents statistics on vulnerability exploitation for Q1 2026. The data draws on open sources and our telemetry.\nWindows and Linux vulnerability exploitation\nIn Q1 2026, threat actor toolsets were updated with exploits for new, recently registered vulnerabilities. However, we first examine the list of veteran vulnerabilities that consistently account for the largest share of detections:\n\nCVE-2018-0802: a remote code execution (RCE) vulnerability in the Equation Editor component\nCVE-2017-11882: another RCE vulnerability also affecting Equation Editor\nCVE-2017-0199: a vulnerability in Microsoft Office and WordPad that allows an attacker to gain control over the system\nCVE-2023-38831: a vulnerability resulting from the improper handling of objects contained within an archive\nCVE-2025-6218: a vulnerability allowing the specification of relative paths to extract files into arbitrary directories, potentially leading to malicious command execution\nCVE-2025-8088: a directory traversal bypass vulnerability during file extraction utilizing NTFS Streams\nAmong the newcomers, we have observed exploits targeting the Microsoft Office platform and Windows OS components. Notably, these new vulnerabilities exploit logic flaws arising from the interaction between multiple systems, making them technically difficult to isolate within a specific file or library. A list of these vulnerabilities is provided below:\n\nCVE-2026-21509 and CVE-2026-21514: security feature bypass vulnerabilities: despite Protected View being enabled, a specially crafted file can still execute malicious code without the user\u2019s knowledge. Malicious commands are executed on the victim\u2019s system with the privileges of the user who opened the file.\nCVE-2026-21513: a vulnerability in the Internet Explorer MSHTML engine, which is used to open websites and render HTML markup. The vulnerability involves bypassing rules that restrict the execution of files from untrusted network sources. Interestingly, the data provider for this vulnerability was an LNK file.\nThese three vulnerabilities were utilized together in a single chain during attacks on Windows-based user systems. While this combination is noteworthy, we believe the widespread use of the entire chain as a unified exploit will likely decline due to its instability. We anticipate that these vulnerabilities will eventually be applied individually as initial entry vectors in phishing campaigns.\nBelow is the trend of exploit detections on user Windows systems starting from Q1 2025.\nDynamics of the number of Windows users encountering exploits, Q1 2025 \u2013 Q1 2026. The number of users who encountered exploits in Q1 2025 is taken as 100% (download)\nThe vulnerabilities listed here can be leveraged to gain initial access to a vulnerable system and for privilege escalation. This underscores the critical importance of timely software updates.\nOn Linux devices, exploits for the following vulnerabilities were detected most frequently:\n\nCVE-2022-0847: a vulnerability known as Dirty Pipe, which enables privilege escalation and the hijacking of running applications\nCVE-2019-13272: a vulnerability caused by improper handling of privilege inheritance, which can be exploited to achieve privilege escalation\nCVE-2021-22555: a heap out-of-bounds write vulnerability in the Netfilter kernel subsystem\nCVE-2023-32233: a vulnerability in the Netfilter subsystem that allows for Use-After-Free conditions and privilege escalation through the improper processing of network requests\nDynamics of the number of Linux users encountering exploits, Q1 2025 \u2013 Q1 2026. The number of users who encountered exploits in Q1 2025 is taken as 100% (download)\nIn the first quarter of 2026, we observed a decrease in the number of detected exploits; however, the detection rates are on the rise relative to the same period last year. For the Linux operating system, the installation of security patches remains critical.\nMost common published exploits\nThe distribution of published exploits by software type in Q1 2026 features an updated set of categories; once again, we see exploits targeting operating systems and Microsoft Office suites.\nDistribution of published exploits by platform, Q1 2026 (download)\nVulnerability exploitation in APT attacks\nWe analyzed which vulnerabilities were utilized in APT attacks during Q1 2026. The ranking provided below includes data based on our telemetry, research, and open sources.\nTOP 10 vulnerabilities exploited in APT attacks, Q1 2026 (download)\nIn Q1 2026, threat actors continued to utilize high-profile vulnerabilities registered in the previous year for APT attacks. The hypothesis we previously proposed has been confirmed: security flaws affecting web applications remain heavily exploited in real-world attacks. However, we are also observing a partial refresh of attacker toolsets. Specifically, during the first quarter of the year, APT campaigns leveraged recently discovered vulnerabilities in Microsoft Office products, edge networking device software, and remote access management systems. Although the most recent vulnerabilities are being exploited most heavily, their general characteristics continue to reinforce established trends regarding the categories of vulnerable software. Consequently, we strongly recommend applying the security patches provided by vendors.\nC2 frameworks\nIn this section, we examine the most popular C2 frameworks used by threat actors and analyze the vulnerabilities targeted by the exploits that interacted with C2 agents in APT attacks.\nThe chart below shows the frequency of known C2 framework usage in attacks against users during Q1 2026, according to open sources.\nTOP 10 C2 frameworks used by APTs to compromise user systems, Q1 2026 (download)\nMetasploit has returned to the top of the list of the most common C2 frameworks, displacing Sliver, which now shares the second position with Havoc. These are followed by Covenant and Mythic, the latter of which previously saw greater popularity. After studying open sources and analyzing samples of malicious C2 agents that contained exploits, we determined that the following vulnerabilities were utilized in APT attacks involving the C2 frameworks mentioned above:\n\nCVE-2023-46604: an insecure deserialization vulnerability allowing for arbitrary code execution within the server process context if the Apache ActiveMQ service is running\nCVE-2024-12356 and CVE-2026-1731: command injection vulnerabilities in BeyondTrust software that allow an attacker to send malicious commands even without system authentication\nCVE-2023-36884: a vulnerability in the Windows Search component that enables command execution on the system, bypassing security mechanisms built into Microsoft Office applications\nCVE-2025-53770: an insecure deserialization vulnerability in Microsoft SharePoint that allows for unauthenticated command execution on the server\nCVE-2025-8088 and CVE-2025-6218: similar directory traversal vulnerabilities that allow files to be extracted from an archive to a predefined path, potentially without the archiving utility displaying any alerts to the user\nThe nature of the described vulnerabilities indicates that they were exploited to gain initial access to the system. Notably, the majority of these security issues are targeted to bypass authentication mechanisms. This is likely due to the fact that C2 agents are being detected effectively, prompting threat actors to reduce the probability of discovery by utilizing bypass exploits.\nNotable vulnerabilities\nThis section highlights the most significant vulnerabilities published in Q1 2026 that have publicly available descriptions.\nCVE-2026-21519: Desktop Window Manager vulnerability\nAt the core of this vulnerability is a Type Confusion flaw. By attempting to access a resource within the Desktop Window Manager subsystem, an attacker can achieve privilege escalation. A necessary condition for exploiting this issue is existing authorization on the system.\nIt is worth noting that the DWM subsystem has been under close scrutiny by threat actors for quite some time. Historically, the primary attack vector involves interacting with the NtDComposition* function set.\nRegPwn (CVE-2026-21533): a system settings access control vulnerability\nCVE-2026-21533 is essentially a logic vulnerability that enables privilege escalation. It stems from the improper handling of privileges within Remote Desktop Services (RDS) components. By modifying service parameters in the registry and replacing the configuration with a custom key, an attacker can elevate privileges to the SYSTEM level. This vulnerability is likely to remain a fixture in threat actor toolsets as a method for establishing persistence and gaining high-level privileges.\nCVE-2026-21514: a Microsoft Office vulnerability\nThis vulnerability was discovered in the wild during attacks on user systems. Notably, an LNK file is used to initiate the exploitation process. CVE-2026-21514 is also a logic issue that allows for bypassing OLE technology restrictions on malicious code execution and the transmission of NetNTLM authentication requests when processing untrusted input.\nClawdbot (CVE-2026-25253): an OpenClaw vulnerability\nThis vulnerability in the AI agent leaks credentials (authentication tokens) when queried via the WebSocket protocol. It can lead to the compromise of the infrastructure where the agent is installed: researchers have confirmed the ability to access local system data and execute commands with elevated privileges. The danger of CVE-2026-25253 is further compounded by the fact that its exploitation has generated numerous attack scenarios, including the use of prompt injections and ClickFix techniques to install stealers on vulnerable systems.\nCVE-2026-34070: LangChain framework vulnerability\nLangChain is an open-source framework designed for building applications powered by large language models (LLMs). A directory traversal vulnerability allowed attackers to access arbitrary files within the infrastructure where the framework was deployed. The core of CVE-2026-34070 lies in the fact that certain functions within langchain_core/prompts/loading.py handled configuration files insecurely. This could potentially lead to the processing of files containing malicious data, which could be leveraged to execute commands and expose critical system information or other sensitive files.\nCVE-2026-22812: an OpenCode vulnerability\nCVE-2026-22812 is another vulnerability identified in AI-assisted coding software. By default, the OpenCode agent provided local access for launching authorized applications via an HTTP server that did not require authentication. Consequently, attackers could execute malicious commands on a vulnerable device with the privileges of the current user.\nConclusion and advice\nWe observe that the registration of vulnerabilities is steadily gaining momentum in Q1 2026, a trend driven by the widespread development of AI tools designed to identify security flaws across various software types. This trajectory is likely to result not only in a higher volume of registered vulnerabilities but also in an increase in exploit-driven attacks, further reinforcing the critical necessity of timely security patch deployment. Additionally, organizations must prioritize vulnerability management and implement effective defensive technologies to mitigate the risks associated with potential exploitation.\nTo ensure the rapid detection of threats involving exploit utilization and to prevent their escalation, it is essential to deploy a reliable security solution. Key features of such a tool include continuous infrastructure monitoring, proactive protection, and vulnerability prioritization based on real-world relevance. These mechanisms are integrated into Kaspersky Next, which also provides endpoint security and protection against cyberattacks of any complexity. \nsecurelist.com/vulnerabilities\u2026", "creation_timestamp": "2026-05-07T10:52:27.573886Z"}, {"uuid": "82a6ee19-834c-4d71-be10-cf6ce9e05811", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2026-25253", "type": "seen", "source": "https://bsky.app/profile/pigondrugs.bsky.social/post/3mlba5yxkcj26", "content": "~Kaspersky~\nQ1 2026 exploit volumes surged due to AI discovery, with APTs heavily targeting MS Office, web apps, and AI frameworks.\n-\nIOCs: CVE-2026-21514, CVE-2026-25253, CVE-2026-21533\n-\n#APT #ThreatIntel #Vulnerabilities", "creation_timestamp": "2026-05-07T12:36:37.347266Z"}, {"uuid": "85810a63-e00e-4d98-99b7-187a549f145a", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2026-25253", "type": "seen", "source": "Telegram/cnT3gNjT1c8jZyCBUN7A77QIJYcKya_18WEnlQRaj4tp4YI", "content": "", "creation_timestamp": "2026-05-10T15:00:08.000000Z"}, {"uuid": "5895663b-1e45-4991-be7f-bec3c00105de", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2026-25253", "type": "seen", "source": "https://t.me/htfgtps/1137", "content": "CVE-2026-25253\nOpenClaw (aka clawdbot or Moltbot)\nbefore 2026.1.29 obtains a gatewayUrl\nvalue from a query string and automatically\nmakes a WebSocket connection without\nprompting, sending a token value.\nGitHub Link:\nhttps://github.com/KajzingerAkos/CVE-2026-25253", "creation_timestamp": "2026-05-14T14:21:01.000000Z"}, {"uuid": "28db5245-29bd-4ba8-81c9-f4feef680f3e", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2026-25253", "type": "seen", "source": "https://t.me/GithubRedTeam/84922", "content": "\ud83d\udea8 GitHub \u76d1\u63a7\u6d88\u606f\u63d0\u9192\n\n\ud83d\udea8 \u53d1\u73b0\u5173\u952e\u8bcd\uff1a #CVE-2026\n\n\ud83d\udce6 \u9879\u76ee\u540d\u79f0\uff1a CVE-2026-25253\n\ud83d\udc64 \u9879\u76ee\u4f5c\u8005\uff1a EQSTLab\n\ud83d\udee0 \u5f00\u53d1\u8bed\u8a00\uff1a HTML\n\u2b50 Star\u6570\u91cf\uff1a 2  |  \ud83c\udf74 Fork\u6570\u91cf\uff1a 0\n\ud83d\udcc5 \u66f4\u65b0\u65f6\u95f4\uff1a 2026-05-20 06:36:10\n\n\ud83d\udcdd \u9879\u76ee\u63cf\u8ff0\uff1a\nOpenClaw Authentication Token Exfiltration\n\n\ud83d\udd17 \u70b9\u51fb\u8bbf\u95ee\u9879\u76ee\u5730\u5740", "creation_timestamp": "2026-05-20T07:00:04.000000Z"}, {"uuid": "386d7e5d-765e-4321-95a8-4b75a4eaf2c3", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2026-25253", "type": "seen", "source": "https://bsky.app/profile/heylazarus.bsky.social/post/3mteebvtdd32d", "content": "Those are three separate stories. The RCE is CVE-2026-25253, patched in 2026.1.29. The 31,000 figure is skills analyzed, 26 percent carrying a flaw, not exposed instances. The 1.5m keys were the Moltbook Supabase leak. All real, all worth knowing, just not one event.", "creation_timestamp": "2026-08-18T13:49:54.956062Z"}, {"uuid": "a108844c-2692-4bc7-b3d0-62ad998d7ca0", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2026-25253", "type": "seen", "source": "https://bsky.app/profile/cyberlensai.bsky.social/post/3mtewuiuxhp27", "content": "Clear split: CVE-2026-25253 is the OpenClaw RCE patched 2026.1.29; the 31,000 figure was skills analyzed (26% flawed), and the 1.5 million keys were the Moltbook Supabase leak. Can you link the original analysis and the patch advisory?", "creation_timestamp": "2026-08-18T19:22:26.056056Z"}, {"uuid": "32b400ed-b180-4454-a78b-03dab6e34809", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2026-25253", "type": "seen", "source": "https://bsky.app/profile/bluehatone.bsky.social/post/3moket6ftvp2u", "content": "OpenClaw is not just chat. It is a robot super user with 24/7 access. Researchers found thousands of agents exposed online with weak auth and plaintext secrets. CVE-2026-25253 can steal tokens by a crafted URL, near CVSS 8.8. Use secrets manager and least privilege now.", "creation_timestamp": "2026-06-18T08:09:34.634565Z"}, {"uuid": "0d971797-c085-4c98-b3df-4790b24845ff", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2026-25253", "type": "seen", "source": "https://bsky.app/profile/phantomfills.bsky.social/post/3moruxrp24s2z", "content": "The RisksIt\u2019s not all sunshine. The recent @OpenClaw vulnerabilities (CVE-2026-25253) were a wake-up call.\n\nAs agents get more \"root\" access to our capital, security becomes the ultimate primitive. Sandbox execution is no longer optional\u2014it's mandatory.", "creation_timestamp": "2026-06-21T07:49:42.108121Z"}, {"uuid": "1cb95d5f-505d-4d06-858c-8036192ee838", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2026-25253", "type": "seen", "source": "https://bsky.app/profile/phantomfills.bsky.social/post/3moruxuwufc2z", "content": "The RisksIt\u2019s not all sunshine. The recent @OpenClaw vulnerabilities (CVE-2026-25253) were a wake-up call.\n\nAs agents get more \"root\" access to our capital, security becomes the ultimate primitive. Sandbox execution is no longer optional\u2014it's mandatory.", "creation_timestamp": "2026-06-21T07:49:42.773752Z"}, {"uuid": "3a2aa5e8-e644-4359-903b-f940af07dc9a", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2026-25253", "type": "seen", "source": "https://bsky.app/profile/phantomfills.bsky.social/post/3moruxymmx22z", "content": "The RisksIt\u2019s not all sunshine. The recent @OpenClaw vulnerabilities (CVE-2026-25253) were a wake-up call.\n\nAs agents get more \"root\" access to our capital, security becomes the ultimate primitive. Sandbox execution is no longer optional\u2014it's mandatory.", "creation_timestamp": "2026-06-21T07:49:43.637658Z"}, {"uuid": "3a7ea034-93f1-4cfb-8f4c-86a45f86463c", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2026-25253", "type": "seen", "source": "https://bsky.app/profile/phantomfills.bsky.social/post/3moruy72a2c2z", "content": "The RisksIt\u2019s not all sunshine. The recent @OpenClaw vulnerabilities (CVE-2026-25253) were a wake-up call.\n\nAs agents get more \"root\" access to our capital, security becomes the ultimate primitive. Sandbox execution is no longer optional\u2014it's mandatory.", "creation_timestamp": "2026-06-21T07:51:55.617839Z"}, {"uuid": "e12742da-e8fa-4069-8325-6aa10873f9d8", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2026-25253", "type": "seen", "source": "https://bsky.app/profile/phantomfills.bsky.social/post/3moruycokpc2z", "content": "The RisksIt\u2019s not all sunshine. The recent @OpenClaw vulnerabilities (CVE-2026-25253) were a wake-up call.\n\nAs agents get more \"root\" access to our capital, security becomes the ultimate primitive. Sandbox execution is no longer optional\u2014it's mandatory.", "creation_timestamp": "2026-06-21T07:51:56.141429Z"}, {"uuid": "a034e306-ba17-445b-9f84-68e8150c0a5b", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2026-25253", "type": "seen", "source": "https://bsky.app/profile/phantomfills.bsky.social/post/3moruyfgaek2z", "content": "The RisksIt\u2019s not all sunshine. The recent @OpenClaw vulnerabilities (CVE-2026-25253) were a wake-up call.\n\nAs agents get more \"root\" access to our capital, security becomes the ultimate primitive. Sandbox execution is no longer optional\u2014it's mandatory.", "creation_timestamp": "2026-06-21T07:54:06.894633Z"}, {"uuid": "be6da4dc-0009-4b00-94b5-4fd88cc3661e", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2026-25253", "type": "seen", "source": "https://bsky.app/profile/pmloik.bsky.social/post/3mottrv2xxt2l", "content": "Top 3 CVE for last 7 days:\nCVE-2026-50656: 28 interactions\nCVE-2026-20262: 25 interactions\nCVE-2026-54420: 25 interactions\n\n\nTop 3 CVE for yesterday:\nCVE-2026-20253: 6 interactions\nCVE-2026-25253: 4 interactions\nCVE-2026-35469: 4 interactions\n", "creation_timestamp": "2026-06-22T02:31:16.151843Z"}, {"uuid": "bdfe3a70-2e77-45f0-8b7c-dd72a5332aaf", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2026-25253", "type": "seen", "source": "https://bsky.app/profile/cyfar.ca/post/3mu7xdoaial24", "content": "~Kaspersky~\nAI-driven flaw discovery surged as attackers rapidly exploited new Windows and Linux vulnerabilities.\n-\nIOCs: CVE-2026-31431, CVE-2026-43284, CVE-2026-25253\n-\n#CVE2026 #Cybersecurity #ThreatIntel", "creation_timestamp": "2026-08-29T13:12:47.891636Z"}, {"uuid": "432755d8-badf-4d24-a5fe-f575ac222d78", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2026-25253", "type": "seen", "source": "https://bsky.app/profile/ctsd-gmbh.bsky.social/post/3mptm24sk6m2j", "content": "CVE-2026-25253 in KI-Agenten ohne Interface: Realit\u00e4t oder Roadmap?\n\nJetzt lesen: https://www.ctsd.de/insights/2026-07-ki-ki-agenten-ohne-interface-realit-t-oder-roadmap.html\n\n#ITSecurity #Compliance #KI\n\nhttps://www.ctsd.de/insights/2026-07-ki-ki-agenten-ohne-interface-realit-t-oder-roadmap.html", "creation_timestamp": "2026-07-04T17:37:53.433721Z"}, {"uuid": "e6cad395-fbe7-4031-a6dc-7ea7c0c23ae6", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2026-25253", "type": "seen", "source": "https://bsky.app/profile/bluehatone.bsky.social/post/3mq25rtswhb23", "content": "OpenClaw security alert. 135,000+ servers exposed, 50,000 open to remote code, 335 bad skills found. CVE-2026-25253 can steal a token with one click via a localhost WebSocket. Safer steps: don\u2019t use your main laptop, enable auth, bind to 127.0.0.1 or VPN, least privilege, audit skills.", "creation_timestamp": "2026-07-07T08:11:22.581651Z"}, {"uuid": "4c6b2c29-026d-4b1e-87a4-23aef32670e6", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2026-25253", "type": "seen", "source": "https://t.me/brutsecurity/2530", "content": "\ud83d\udea8 CVE-2026-25253: OpenClaw Logical Flaw\n\nCritical Token Leakage via Unsanitized WebSocket Redirect!\nAn attacker crafts a malicious URL containing a controlled gatewayUrl query parameter and embedded token, causing OpenClaw to silently establish a WebSocket connection to the attacker-controlled endpoint and exfiltrate the sensitive token without user interaction or consent.\n\nFull Vulnerability Details &amp; Analysis at DarkEye:\n\ud83d\udd17 https://darkeye.org/vuln/cve/CVE-2026-25253\n\n\ud83d\udd0d Identify Targets via ZoomEye:\n\nFilter: vul.cve=\"CVE-2026-25253\"\nSearch Dork: app=\"OpenClaw\"\nExposure: 33k+ instances identified globally.\n\nZoomEye Search Link:\n\ud83d\udc49 https://www.zoomeye.ai/searchResult?q=YXBwPSJPcGVuQ2xhdyI=&amp;utm_source=twitter&amp;utm_medium=social&amp;utm_campaign=cve_ops_20260213", "creation_timestamp": "2026-07-09T03:00:05.774416Z"}, {"uuid": "0c8de1b4-1139-48dc-8854-cc5e544503e9", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2026-25253", "type": "seen", "source": "https://t.me/brutsecurity/2530", "content": "\ud83d\udea8 CVE-2026-25253: OpenClaw Logical Flaw\n\nCritical Token Leakage via Unsanitized WebSocket Redirect!\nAn attacker crafts a malicious URL containing a controlled gatewayUrl query parameter and embedded token, causing OpenClaw to silently establish a WebSocket connection to the attacker-controlled endpoint and exfiltrate the sensitive token without user interaction or consent.\n\nFull Vulnerability Details &amp; Analysis at DarkEye:\n\ud83d\udd17 https://darkeye.org/vuln/cve/CVE-2026-25253\n\n\ud83d\udd0d Identify Targets via ZoomEye:\n\nFilter: vul.cve=\"CVE-2026-25253\"\nSearch Dork: app=\"OpenClaw\"\nExposure: 33k+ instances identified globally.\n\nZoomEye Search Link:\n\ud83d\udc49 https://www.zoomeye.ai/searchResult?q=YXBwPSJPcGVuQ2xhdyI=&amp;utm_source=twitter&amp;utm_medium=social&amp;utm_campaign=cve_ops_20260213", "creation_timestamp": "2026-07-10T00:00:13.100231Z"}, {"uuid": "06343d69-f2f0-4762-8ed8-eb5c6ad5c192", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2026-25253", "type": "published-proof-of-concept", "source": "https://t.me/brutsecurity/2530", "content": "\ud83d\udea8 CVE-2026-25253: OpenClaw Logical Flaw\n\nCritical Token Leakage via Unsanitized WebSocket Redirect!\nAn attacker crafts a malicious URL containing a controlled gatewayUrl query parameter and embedded token, causing OpenClaw to silently establish a WebSocket connection to the attacker-controlled endpoint and exfiltrate the sensitive token without user interaction or consent.\n\nFull Vulnerability Details &amp; Analysis at DarkEye:\n\ud83d\udd17 https://darkeye.org/vuln/cve/CVE-2026-25253\n\n\ud83d\udd0d Identify Targets via ZoomEye:\n\nFilter: vul.cve=\"CVE-2026-25253\"\nSearch Dork: app=\"OpenClaw\"\nExposure: 33k+ instances identified globally.\n\nZoomEye Search Link:\n\ud83d\udc49 https://www.zoomeye.ai/searchResult?q=YXBwPSJPcGVuQ2xhdyI=&amp;utm_source=twitter&amp;utm_medium=social&amp;utm_campaign=cve_ops_20260213", "creation_timestamp": "2026-07-11T10:00:05.291865Z"}, {"uuid": "a1660a49-9fb0-448f-8eef-babe8b4b65f8", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2026-25253", "type": "published-proof-of-concept", "source": "https://t.me/brutsecurity/2530", "content": "\ud83d\udea8 CVE-2026-25253: OpenClaw Logical Flaw\n\nCritical Token Leakage via Unsanitized WebSocket Redirect!\nAn attacker crafts a malicious URL containing a controlled gatewayUrl query parameter and embedded token, causing OpenClaw to silently establish a WebSocket connection to the attacker-controlled endpoint and exfiltrate the sensitive token without user interaction or consent.\n\nFull Vulnerability Details &amp; Analysis at DarkEye:\n\ud83d\udd17 https://darkeye.org/vuln/cve/CVE-2026-25253\n\n\ud83d\udd0d Identify Targets via ZoomEye:\n\nFilter: vul.cve=\"CVE-2026-25253\"\nSearch Dork: app=\"OpenClaw\"\nExposure: 33k+ instances identified globally.\n\nZoomEye Search Link:\n\ud83d\udc49 https://www.zoomeye.ai/searchResult?q=YXBwPSJPcGVuQ2xhdyI=&amp;utm_source=twitter&amp;utm_medium=social&amp;utm_campaign=cve_ops_20260213", "creation_timestamp": "2026-07-12T00:00:51.849771Z"}, {"uuid": "289e3bc2-79ae-437d-98d6-e6aa24d9de92", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2026-25253", "type": "seen", "source": "Telegram/IYbPLk4ERTEBv3PHVDATQd8EaZ4Sc0OJ99RE8uvxfU7J1W8", "content": "", "creation_timestamp": "2026-07-16T19:00:13.408971Z"}, {"uuid": "6b54f24a-fb7c-463a-a03c-0697ddda17b4", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2026-25253", "type": "seen", "source": "Telegram/IYbPLk4ERTEBv3PHVDATQd8EaZ4Sc0OJ99RE8uvxfU7J1W8", "content": "", "creation_timestamp": "2026-07-17T00:00:28.767180Z"}, {"uuid": "c3a9f34d-5e35-4b1b-bfb9-5411268a71e1", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2026-25253", "type": "published-proof-of-concept", "source": "https://t.me/cve0day/375", "content": "CVE-2026-25253\n\nOpenClaw (aka clawdbot or Moltbot) before 2026.1.29 obtains a gatewayUrl value from a query string and automatically makes a WebSocket connection without prompting, sending a token value.\n\nGitHub Link:\nhttps://github.com/KajzingerAkos/CVE-2026-25253", "creation_timestamp": "2026-08-28T00:00:31.649326Z"}, {"uuid": "d56a1a2a-5fdc-4461-805c-368a15d83e57", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2026-25253", "type": "published-proof-of-concept", "source": "Telegram/IYbPLk4ERTEBv3PHVDATQd8EaZ4Sc0OJ99RE8uvxfU7J1W8", "content": "", "creation_timestamp": "2026-07-18T00:00:43.636618Z"}, {"uuid": "31ddc63a-fe5f-43de-b7e2-b9d69b7f2163", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2026-25253", "type": "seen", "source": "Telegram/1BFYBqxVhxenmWnMVlLgSK9cN9aRCWbdMoUwe1D6vlN0-A", "content": "", "creation_timestamp": "2026-07-20T19:00:12.049773Z"}, {"uuid": "b5acaf16-2698-41b3-8c56-c54092579218", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2026-25253", "type": "seen", "source": "Telegram/1BFYBqxVhxenmWnMVlLgSK9cN9aRCWbdMoUwe1D6vlN0-A", "content": "", "creation_timestamp": "2026-07-21T00:00:29.615025Z"}, {"uuid": "d4d06716-bffd-442a-b682-2cbfeff6d302", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2026-25253", "type": "seen", "source": "https://t.me/cve0day/375", "content": "CVE-2026-25253\n\nOpenClaw (aka clawdbot or Moltbot) before 2026.1.29 obtains a gatewayUrl value from a query string and automatically makes a WebSocket connection without prompting, sending a token value.\n\nGitHub Link:\nhttps://github.com/KajzingerAkos/CVE-2026-25253", "creation_timestamp": "2026-08-27T15:00:08.466246Z"}, {"uuid": "30260e33-80c0-4d8b-8e6c-3843e6a148c8", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2026-25253", "type": "published-proof-of-concept", "source": "Telegram/1BFYBqxVhxenmWnMVlLgSK9cN9aRCWbdMoUwe1D6vlN0-A", "content": "", "creation_timestamp": "2026-07-22T00:00:21.430584Z"}, {"uuid": "08c59f6c-8e2f-4410-9242-bd9ebf524f59", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2026-25253", "type": "seen", "source": "https://poliverso.org/objects/0477a01e-66d81917-442e1a3db5444e7f", "content": "Exploits and vulnerabilities in Q2 2026\nThe vulnerability landscape shifted significantly in Q2 2026. First, the number of registered CVEs reached an unprecedented level. This is driven primarily by the widespread adoption of AI, both for application development and search for security flaws. This resulted in entire new classes of vulnerabilities emerging, particularly in the Linux networking subsystem.\nSecond, security researchers have been publishing exploits for unpatched vulnerabilities more frequently. Publications like these can generate significant fallout, since they potentially open the door for attackers to target unprotected systems.\nStatistics on registered vulnerabilities\nThis section provides statistical data on registered vulnerabilities. The data comes from Kaspersky\u2019s vulnerability knowledge base, which draws on the CVE database as well as the Russian BDU database and GitHub Advisory (GHSA). As a result, the figures for previous reporting periods may differ from those published in earlier reports.\nWe examine the number of registered vulnerabilities for each month over the last five years. As the chart below shows, this number continues to surge, a trend reflected across all the databases we track. It\u2019s driven primarily by the widespread adoption of AI tools: as we predicted in our previous report, these tools have played a major role in the discovery of vulnerabilities in third-party software. Meanwhile, these tools often contain security issues of their own. For example, OpenClaw, a popular AI project, ranked 12th among those with the highest number of vulnerabilities discovered and published in Q2, with over 200 CVEs registered during the reporting period. Finally, AI development tools are also contributing to the vulnerability landscape, since the quality of the code they produce can vary widely. Therefore, the rate at which new vulnerabilities are discovered will inevitably keep growing.\nTotal published vulnerabilities per month from 2022 through 2026 (download)\nNext, we analyze the number of new critical vulnerabilities (CVSS &gt; 9.0) over the same period.\nTotal critical vulnerabilities published per month from 2022 through 2026 (download)\nAs the chart shows, the number of published critical vulnerabilities jumped sharply in Q2. This is because using AI for vulnerability research makes it possible to analyze massive amounts of previously unexamined code, uncover new attack surfaces, and identify entire classes of vulnerabilities that have gone unnoticed for decades. In particular, AI was used to find a series of Dirty Frag vulnerabilities in the Linux kernel.\nExploitation statistics\nThis section presents statistics on vulnerability exploitation for Q2 2026. The data draws on open sources and our telemetry.\nWindows and Linux vulnerability exploitation\nQ2 2026 saw a new precedent in the publication of vulnerabilities in Windows components and exploits for these: researchers no longer waiting for CVE registration, let alone patches. A case in point: a researcher who goes by Nightmare Eclipse (also known as Chaotic Eclipse) published a list of new \u201cnamed\u201d vulnerabilities across various Windows subsystems. At the time the technical details were published, none of the vulnerabilities had been assigned a CVE identifier:\n\nBlueHammer: a local privilege escalation vulnerability in Windows Defender. During signature database updates, a time-of-check to time-of-use (TOCTOU) race condition occurs, allowing an attacker to substitute the directory where temporary update files are written. The researcher published a fully functional exploit for the vulnerability.\nRedSun: another logical vulnerability in Windows Defender with a working exploit. Suspicious and malicious files marked as \u201ccloud\u201d can be overwritten or restored to their original directory with elevated privileges. The exploit incorporates fragments of algorithms that make it possible to leverage various logical vulnerabilities in Windows, effectively combining a large number of popular exploitation techniques.\nYellowKey: a vulnerability that lets the user bypass BitLocker full-disk encryption and access system data through the Windows Recovery Environment (WinRE). A fully functional exploit was also published.\nGreenPlasma: a vulnerability that enables system object injection via the CTF loader for the Collaborative Translation Framework (CTFMON) service in Windows. The original publication included an exploit with limited functionality.\nRougePlanet: yet another Windows Defender vulnerability that, like BlueHammer, stems from a TOCTOU issue, this time in the engine responsible for real-time system scanning. The published exploit uses the vulnerability to overwrite the system file wermgr.exe with a malicious one.\nUnDefend: another vulnerability in the Windows Defender service. This time, the exploit causes a denial of service and blocks updates.\nEven though such cases remain isolated for now, we believe they\u2019ll grow into a full-fledged trend. Early publication of exploits gives attackers an advantage over software developers, who are left with no time to fix the issues.\nVeteran vulnerabilities in Windows software also remain relevant. These are the ones our solutions most frequently detect exploits for:\n\nCVE-2018-0802: a remote code execution (RCE) vulnerability in the Equation Editor component\nCVE-2017-11882: another RCE vulnerability also affecting Equation Editor\nCVE-2017-0199: a vulnerability in Microsoft Office and WordPad that allows an attacker to gain control over the system\nCVE-2023-38831: a vulnerability in WinRAR that involves improper handling of objects within an archive\nCVE-2025-6218 (formerly ZDI-CAN-27198): another WinRAR vulnerability allowing the specification of relative paths to extract files into arbitrary directories, potentially leading to malicious command execution\nCVE-2025-8088: a vulnerability similar in exploitation method to CVE-2025-6218. The attackers used NTFS Streams to circumvent controls on the directory into which files are being unpacked\nThe vulnerabilities listed here can be leveraged to gain initial access to a vulnerable system and for privilege escalation. This underscores the critical importance of timely software updates.\nThat said, the number of Windows users who encountered exploits declined slightly in Q2, hitting an 18-month low.\nDynamics of the number of Windows users encountering exploits, Q1 2025 \u2013 Q2 2026. The number of users who encountered exploits in Q1 2025 is taken as 100% (download)\nLinux also hit a rough patch in Q2 2026. Specifically, the period saw the disclosure of the Dirty Frag family of vulnerabilities, which lets an attacker reliably escalate privileges within the operating system.\nAll the vulnerabilities published in Q2 2026 were, in one way or another, related to the Linux caching subsystem. Here are the ones being most actively exploited:\n\nCVE-2026-31431 (Copy Fail): a local privilege escalation vulnerability in the Linux kernel that lets an unprivileged user modify the page cache and gain root privileges. Especially dangerous for cloud and containerized environments\nCVE-2026-43284, CVE-2026-43500 (Dirty Frag): a family of vulnerabilities in the Linux networking subsystem (IPsec ESP and RxRPC) that lets a local user overwrite the page cache and escalate privileges to root\nCVE-2026-46300 (Fragnesia): a local privilege escalation vulnerability in the Linux kernel related to packet fragment handling and the page cache mechanism. It lets an unprivileged user gain root privileges and is also classified as part of the Dirty Frag family\nCVE-2026-31635 (DirtyDecrypt): a Linux kernel vulnerability that lets a local attacker escalate privileges due to improper handling of decryption operations and page cache data modification\nCVE-2026-43494 (PinTheft): a Linux kernel vulnerability that lets a local user gain elevated privileges due to errors in the memory page pinning mechanism\nCVE-2026-46331 (pedit COW): a vulnerability in the Linux kernel\u2019s traffic control subsystem (tc-pedit) that exploits a flaw in copy-on-write to modify the page cache and subsequently escalate privileges to root\nThe vulnerabilities described above were quickly embraced by attackers. At the same time, our solutions continue to detect exploitation attempts targeting older vulnerabilities as well:\n\nCVE-2022-0847: a vulnerability known as Dirty Pipe, which enables privilege escalation and the hijacking of running applications\nCVE-2019-13272: a vulnerability caused by improper handling of privilege inheritance, which can be exploited to achieve privilege escalation\nCVE-2021-22555: a heap out-of-bounds write vulnerability in the Netfilter kernel subsystem\nCVE-2023-32233: another Netfilter subsystem vulnerability that allows for Use-After-Free conditions and privilege escalation through improper processing of network requests\nDynamics of the number of Linux users encountering exploits, Q1 2025 \u2013 Q2 2026. The number of users who encountered exploits in Q1 2025 is taken as 100% (download)\nIn Q2 2026, the number of Linux users who encountered exploits declined slightly compared to Q1. Given that a significant share of new vulnerabilities are tied to the operating system\u2019s caching subsystem, we recommend installing patches as quickly as possible, or disabling vulnerable kernel modules if patching isn\u2019t an option.\nMost common published exploits\nThe distribution of published exploits by software type in Q2 2026 includes categories that haven\u2019t appeared in the sample for a long time. For instance, we\u2019re once again seeing exploits targeting SharePoint. It\u2019s worth noting that while several vulnerability write-ups for Exchange and SharePoint were published during the quarter, most turned out to be fake, AI-generated research. While the articles and exploit source code themselves look fairly polished, they describe nonexistent problems in the software or its components \u2014 often close to genuinely vulnerable mechanisms \u2014 in order to mislead researchers. This type of attack is aimed at increasing the time it takes to detect real vulnerabilities. In some cases, the description of a nonexistent vulnerability came bundled with completely unrelated malware.\nDistribution of published exploits by platform, Q1 2026 (download)\nDistribution of published exploits by platform, Q2 2026 (download)\nVulnerability exploitation in APT attacks\nWe analyzed which vulnerabilities were exploited in APT attacks during Q2 2026. The rankings provided below include data based on our telemetry, research, and open sources.\nTOP 10 vulnerabilities exploited in APT attacks, Q2 2026 (download)\nIn Q2 2026, a trend emerged in APT attacks toward exploiting new vulnerabilities right from the moment they\u2019re published. As before, we\u2019re also seeing a large number of zero-day vulnerabilities. The Langflow vulnerability deserves particular attention: it\u2019s one of the first cases of an APT group exploiting AI technology, which many organizations are only just beginning to integrate. Because most of this tech is proprietary, it has a considerable number of security blind spots. Therefore, given the growing number of AI-based automation tools, we strongly recommend going beyond the usual patching and developing secure procedures for credential use and sensitive data handling in systems that rely on agents and LLMs.\nC2 frameworks\nIn this section, we examine the most popular C2 frameworks used by APT groups and analyze the vulnerabilities targeted by the exploits that interacted with C2 agents in APT attacks.\nThe chart below shows the frequency of known C2 framework usage in attacks during Q2 2026, according to open sources.\nTOP 10 C2 frameworks used by APTs to compromise user systems, Q2 2026 (download)\nSliver, Havoc, AdaptixC2, and Metasploit remain the most widely used C2 frameworks. After studying open sources and analyzing samples of malicious C2 agents that contained exploits, we determined that the following vulnerabilities were utilized in APT attacks involving the C2 frameworks mentioned above:\n\nCVE-2026-35273: a vulnerability in Oracle PeopleSoft PeopleTools that security vendors classify as server-side request forgery (SSRF). The details of the vulnerability have never been disclosed, although some research covers the post-exploitation steps\nCVE-2023-46604: an insecure deserialization vulnerability in Apache ActiveMQ that allows arbitrary code execution in the context of the service process\nCVE-2024-12356 and CVE-2026-1731: command injection vulnerabilities in BeyondTrust software that allow an attacker to send malicious commands even without system authentication\nCVE-2023-36884: a vulnerability in the Windows Search component that allows commands to be run on the system, bypassing the mark-of-the-web (MoTW) mechanism\nCVE-2025-53770: an insecure deserialization vulnerability in Microsoft SharePoint that allows for unauthenticated command execution on the server\nCVE-2025-8088 and CVE-2025-6218: similar directory traversal vulnerabilities in WinRAR that allow files to be extracted from an archive to a predetermined path, potentially without the archiving utility displaying any alerts to the user\nThese vulnerabilities show that attackers used them for initial access and privilege escalation on vulnerable systems, setting the stage for launching a C2 agent. They include both zero-day vulnerabilities and fairly well-known security issues.\nLLM/AI tool vulnerabilities\nThis section analyzes data published in Kaspersky\u2019s vulnerability knowledge base. We reviewed the Q2 2026 version of the knowledge base.\nAs mentioned above, AI tools, plugins, and technologies have proven fairly effective at automating the search for problematic code and anomalous behavior. The high speed at which new vulnerabilities are being discovered has naturally created a need to fix them just as quickly. AI is often used for this too, which increases the volume of code being generated. However, neither code written without human involvement nor AI-generated advice is always correct.\nThe chart below covers registered vulnerabilities in AI tools for 2025\u20132026.\nNumber of published vulnerabilities in LLMs, AI tools, and plugins with similar functionality, 2025\u20132026 (download)\nAs the charts show, AI tools are racking up a substantial number of registered vulnerabilities, and that number keeps growing quarter over quarter. It\u2019s also worth looking at how AI tool vulnerabilities break down by type, according to the CWE system:\nTOP 6 vulnerability types in products that implement or use AI/LLM logic, 2025\u20132026\nInterestingly, vulnerabilities of an undetermined type have ranked first in every quarter since the start of 2025. Traditionally-made software has the same issue, and it doesn\u2019t look like the growing number of AI tools will fix it. It\u2019s also notable that the list includes classes CWE developers themselves don\u2019t recommend using for vulnerability classification, since they lump together a whole range of more specific types. CWE-284 is an example of this.\nLooking at the most common classes, the key issues found in AI-related software can be summed up as follows:\n\nInadequate access control over critical system objects\nImproper implementation of authentication and authorization mechanisms\nInjections\nIt\u2019s worth noting that injection-related vulnerabilities were relatively rare before AI agents took off (previously, they mostly affected web apps). Recently, though, these security issues have become relevant again.\nLooking back at a year and a half of the AI boom, one conclusion stands out regarding registered vulnerabilities: AI tool developers are more focused on expanding functionality than on security. This is worth keeping in mind when using these tools. Let\u2019s look at the projects and applications that either integrated AI tools or offered them as the core product. Below is a list of the those with the highest number of registered vulnerabilities for 2025\u20132026.\nTOP AI/LLM-related projects by number of published vulnerabilities, 2025\u20132026 (download)\nNotable vulnerabilities\nThis section highlights the most significant vulnerabilities published in Q2 2026 that have publicly available descriptions. Since the above already covers several significant vulnerabilities published during the reporting period, this section consists mainly of LLM/AI tool vulnerabilities.\nCVE-2026-25253: a gatewayUrl vulnerability in OpenClaw\nThe issue stems from the fact that the OpenClaw user interface trusts the value of the gatewayUrl parameter passed in the URL and automatically establishes a WebSocket connection to the specified address. During this connection process, it sends an authentication token without any additional user confirmation.\nThe attack algorithm exploiting this vulnerability works as follows:\n\nThe application obtains a critical connection address from an external source (the gatewayUrl URL parameter), which is controlled by the attacker.\nThere is no validation before use.\nThe client automatically initiates a connection to the address specified in the parameter, which belongs to the attacker.\nWhile connected, the application sends credentials (an access token) to the specified address.\nIf the attacker obtains a valid token, the consequences depend on that token\u2019s level of access within the system. In general, this could lead to:\n\nUser session compromise\nExecution of operations on the user\u2019s behalf\nModification of the AI agent configuration\nUnauthorized access to tools and resources connected to the agent\nUnder certain OpenClaw configurations, further compromise of the host running the agent\nIt\u2019s worth noting that the risk of exploitation arises from a combination of several factors: the automatic connection and token transmission, the lack of address trust verification, and the high privileges granted to the local AI agent.\nCVE-2026-41948: a path traversal vulnerability in the Dify AI platform\nThe vulnerability lets an authenticated user craft a request that enables the application to escape its permitted tenant and gain access to internal REST APIs that weren\u2019t meant for that user. The root cause is insufficient normalization and validation of the URL path before it\u2019s passed to the internal service.\nDepending on the Dify configuration, the consequences can include:\n\nUnauthorized access to internal service interfaces\nBreach of isolation between workspaces\nExposure of internal service information\nConditions favorable to further attacks when combined with other vulnerabilities\nThe use of Dify in enterprise AI platforms is particularly risky, since internal services there tend to hold elevated privileges.\nCVE-2026-45386: an improper access control vulnerability in Open WebUI\nIn Open WebUI, pin/unpin operations on messages are write operations, since they modify that message\u2019s metadata (is_pinned, pinned_by, pinned_at). In vulnerable versions, however, before performing these actions, the API only checked for read access to the channel (a chat between a user or group and the AI) containing the message, not permission to modify its content. As a result, a user with a role limited to viewing messages could still change a message\u2019s pinned status.\nThe vulnerability\u2019s mechanism works as follows:\n\nThe user initiates an action that changes the state of an object.\nThe application treats this action as a regular read request.\nOnly channel view permission is checked.\nThe application performs a write without verifying the required user authorization.\nThis violates one of the fundamental principles of access control models \u2014 namely, that any operation that changes the state of data must be checked for the appropriate write or moderation permissions, regardless of whether the object itself is readable.\nAlthough the vulnerability doesn\u2019t lead to arbitrary code execution or compromise of sensitive data, it can affect data integrity and collaborative workflows. Potential consequences of exploitation include unauthorized pinning or unpinning of messages, disruption of channel moderators\u2019 and administrators\u2019 activities, changes to the display order of important information, and even the potential spread of false or misleading information by altering the channel containing a pinned message.\nOpen WebUI is widely used as an interface for interacting with local and enterprise LLMs. In these systems, pinned messages often contain important instructions, announcements, or tips for users. The ability to modify them with minimal privileges can disrupt collaborative workflows, cause confusion, and undermine trust in information published by administrators and moderators.\nCVE-2026-45501: a vulnerability in Microsoft Exchange\nThe vulnerability stems from improper neutralization of user input when generating Exchange web pages. As a result, the browser may interpret specially crafted data as active content instead of plain text.\nAlthough Microsoft categorizes the potential impact of exploiting this vulnerability as spoofing, flaws like this can lead to alteration of displayed content, imitation of trusted interfaces, actions on behalf of the user within an active session, and abuse of user trust.\nIt\u2019s worth noting that issues like this are still relevant in modern software, given that mechanisms like Content Security Policy and various parsers were specifically created to help developers neutralize dangerous parts of user page content.\nConclusion and advice\nQ2 brought the first significant results of AI automation adoption in software development and vulnerability hunting tools. This research shows that beyond traditional patch management, organizations now need real-time monitoring of systems and access controls, since infrastructure and everyday applications now contain far more AI functionality that could lead to compromise.\nAccordingly, besides quickly detecting infrastructure vulnerabilities and managing security patches, modern enterprise-grade security solutions need to provide a broad range of preventive measures for tracking the overall health of systems and workstations. Kaspersky Next meets these requirements by combining proactive mechanisms with the ability to respond promptly to emerging threats. \nsecurelist.com/vulnerabilities\u2026", "creation_timestamp": "2026-08-26T10:30:36.754136Z"}, {"uuid": "04ab08b4-5c82-41ba-a26c-184383cb7af2", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2026-25253", "type": "seen", "source": "https://t.me/HackingTeamGrupoOfficial/43158", "content": "\u26a0\ufe0f Top CVEs in 2026 \u26a0\ufe0f\n\n1\ufe0f\u20e3  CVE-2026-2441:\nGoogle Chrome Blink RCE\n2\ufe0f\u20e3  CVE-2026-27896: \nBypassing Security Controls in MCP Go SDK\n3\ufe0f\u20e3  CVE-2026-20841:\nWindows Notepad RCE\n4\ufe0f\u20e3  CVE-2026-20817:\nWindows Error Reporting ALPC Privilege Escalation\n5\ufe0f\u20e3  CVE-2026-25253:\nClawdbot/Moltbot/OpenClaw One-click RCE", "creation_timestamp": "2026-09-02T06:00:15.719630Z"}, {"uuid": "77eb7841-b7a8-43ef-b0a7-1a811c7487d8", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2026-25253", "type": "seen", "source": "https://bsky.app/profile/bluehatone.bsky.social/post/3muji7eax6m2b", "content": "OpenClaw is not just chat. It can read files, run shell commands, and use your browser. Researchers list seven risks. A national warning says avoid your main laptop. CVE-2026-25253 needs a fast fix. Use a VM, low power accounts, limit tools, and keep logs.", "creation_timestamp": "2026-09-02T08:08:35.108517Z"}, {"uuid": "991820df-7103-4c80-bb66-1e198e4f0670", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2026-25253", "type": "seen", "source": "https://t.me/HackingTeamGrupoOfficial/43158", "content": "\u26a0\ufe0f Top CVEs in 2026 \u26a0\ufe0f\n\n1\ufe0f\u20e3  CVE-2026-2441:\nGoogle Chrome Blink RCE\n2\ufe0f\u20e3  CVE-2026-27896: \nBypassing Security Controls in MCP Go SDK\n3\ufe0f\u20e3  CVE-2026-20841:\nWindows Notepad RCE\n4\ufe0f\u20e3  CVE-2026-20817:\nWindows Error Reporting ALPC Privilege Escalation\n5\ufe0f\u20e3  CVE-2026-25253:\nClawdbot/Moltbot/OpenClaw One-click RCE", "creation_timestamp": "2026-09-03T00:00:47.072882Z"}]}