{"vulnerability": "CVE-2026-8055", "sightings": [{"uuid": "c11a5417-31eb-4aa3-8a21-75df066ea561", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2026-8055", "type": "seen", "source": "https://bsky.app/profile/cve.skyfleet.blue/post/3mqpl3db3ao22", "content": "CVE-2026-8055 - Rejected reason: ** REJECT ** DO NOT USE THIS CAND\nCVE ID : CVE-2026-8055\n \n Published : July 15, 2026, 6:16 p.m. | 1\u00a0hour, 17\u00a0minutes ago\n \n Description : Rejected reason: ** REJECT ** DO NOT USE THIS CANDIDATE NUMBER. ConsultIDs: CVE-2026-48866. Reason: This ...", "creation_timestamp": "2026-07-15T20:35:12.232962Z"}, {"uuid": "b3889ea7-7507-4b1b-a91e-512d64a4369c", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "cve-2026-80551", "type": "seen", "source": "https://infosec.exchange/users/cR0w/statuses/117168393907382774", "content": "Anyone want 17 new sev:CRIT Linux vulns? Good. Happy Thursday.\nhttps://nvd.nist.gov/vuln/detail/cve-2026-74746https://nvd.nist.gov/vuln/detail/cve-2026-74737https://nvd.nist.gov/vuln/detail/cve-2026-74744https://nvd.nist.gov/vuln/detail/cve-2026-74743https://nvd.nist.gov/vuln/detail/cve-2026-74752https://nvd.nist.gov/vuln/detail/cve-2026-80528https://nvd.nist.gov/vuln/detail/cve-2026-80519https://nvd.nist.gov/vuln/detail/cve-2026-74751https://nvd.nist.gov/vuln/detail/cve-2026-80551https://nvd.nist.gov/vuln/detail/cve-2026-80557https://nvd.nist.gov/vuln/detail/cve-2026-80561https://nvd.nist.gov/vuln/detail/cve-2026-80558https://nvd.nist.gov/vuln/detail/cve-2026-80554https://nvd.nist.gov/vuln/detail/cve-2026-80587https://nvd.nist.gov/vuln/detail/cve-2026-80589https://nvd.nist.gov/vuln/detail/cve-2026-80586https://nvd.nist.gov/vuln/detail/cve-2026-80585", "creation_timestamp": "2026-08-27T16:23:28.832517Z"}, {"uuid": "9f0fa38c-da85-46b0-a0b6-ca997853ec57", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "cve-2026-80557", "type": "seen", "source": "https://infosec.exchange/users/cR0w/statuses/117168393907382774", "content": "Anyone want 17 new sev:CRIT Linux vulns? Good. Happy Thursday.\nhttps://nvd.nist.gov/vuln/detail/cve-2026-74746https://nvd.nist.gov/vuln/detail/cve-2026-74737https://nvd.nist.gov/vuln/detail/cve-2026-74744https://nvd.nist.gov/vuln/detail/cve-2026-74743https://nvd.nist.gov/vuln/detail/cve-2026-74752https://nvd.nist.gov/vuln/detail/cve-2026-80528https://nvd.nist.gov/vuln/detail/cve-2026-80519https://nvd.nist.gov/vuln/detail/cve-2026-74751https://nvd.nist.gov/vuln/detail/cve-2026-80551https://nvd.nist.gov/vuln/detail/cve-2026-80557https://nvd.nist.gov/vuln/detail/cve-2026-80561https://nvd.nist.gov/vuln/detail/cve-2026-80558https://nvd.nist.gov/vuln/detail/cve-2026-80554https://nvd.nist.gov/vuln/detail/cve-2026-80587https://nvd.nist.gov/vuln/detail/cve-2026-80589https://nvd.nist.gov/vuln/detail/cve-2026-80586https://nvd.nist.gov/vuln/detail/cve-2026-80585", "creation_timestamp": "2026-08-27T16:23:28.883735Z"}, {"uuid": "bae3b2ee-6228-47f5-afcb-71d2bceeba28", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "cve-2026-80558", "type": "seen", "source": "https://infosec.exchange/users/cR0w/statuses/117168393907382774", "content": "Anyone want 17 new sev:CRIT Linux vulns? Good. Happy Thursday.\nhttps://nvd.nist.gov/vuln/detail/cve-2026-74746https://nvd.nist.gov/vuln/detail/cve-2026-74737https://nvd.nist.gov/vuln/detail/cve-2026-74744https://nvd.nist.gov/vuln/detail/cve-2026-74743https://nvd.nist.gov/vuln/detail/cve-2026-74752https://nvd.nist.gov/vuln/detail/cve-2026-80528https://nvd.nist.gov/vuln/detail/cve-2026-80519https://nvd.nist.gov/vuln/detail/cve-2026-74751https://nvd.nist.gov/vuln/detail/cve-2026-80551https://nvd.nist.gov/vuln/detail/cve-2026-80557https://nvd.nist.gov/vuln/detail/cve-2026-80561https://nvd.nist.gov/vuln/detail/cve-2026-80558https://nvd.nist.gov/vuln/detail/cve-2026-80554https://nvd.nist.gov/vuln/detail/cve-2026-80587https://nvd.nist.gov/vuln/detail/cve-2026-80589https://nvd.nist.gov/vuln/detail/cve-2026-80586https://nvd.nist.gov/vuln/detail/cve-2026-80585", "creation_timestamp": "2026-08-27T16:23:29.010643Z"}, {"uuid": "80ec421e-84ee-4b36-8468-fed2e7c29c68", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "cve-2026-80554", "type": "seen", "source": "https://infosec.exchange/users/cR0w/statuses/117168393907382774", "content": "Anyone want 17 new sev:CRIT Linux vulns? Good. Happy Thursday.\nhttps://nvd.nist.gov/vuln/detail/cve-2026-74746https://nvd.nist.gov/vuln/detail/cve-2026-74737https://nvd.nist.gov/vuln/detail/cve-2026-74744https://nvd.nist.gov/vuln/detail/cve-2026-74743https://nvd.nist.gov/vuln/detail/cve-2026-74752https://nvd.nist.gov/vuln/detail/cve-2026-80528https://nvd.nist.gov/vuln/detail/cve-2026-80519https://nvd.nist.gov/vuln/detail/cve-2026-74751https://nvd.nist.gov/vuln/detail/cve-2026-80551https://nvd.nist.gov/vuln/detail/cve-2026-80557https://nvd.nist.gov/vuln/detail/cve-2026-80561https://nvd.nist.gov/vuln/detail/cve-2026-80558https://nvd.nist.gov/vuln/detail/cve-2026-80554https://nvd.nist.gov/vuln/detail/cve-2026-80587https://nvd.nist.gov/vuln/detail/cve-2026-80589https://nvd.nist.gov/vuln/detail/cve-2026-80586https://nvd.nist.gov/vuln/detail/cve-2026-80585", "creation_timestamp": "2026-08-27T16:23:29.054357Z"}, {"uuid": "27e4ffa8-72a0-483a-a791-0c2b16396bed", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2026-80551", "type": "seen", "source": "https://bsky.app/profile/stackflag.bsky.social/post/3mu2g2etdac25", "content": "CVE-2026-80551 - linux\nThe Linux kernel\u2019s support for IBM mainframe I/O devices could read the wrong amount of data because it assumed the first address entry had to line up on a specific memory boundary. This\u2026\n\nToo many irrelevant or confusing CVEs? Use stackflag.com\n\n#linux #CVE #infosec", "creation_timestamp": "2026-08-27T08:20:03.728089Z"}, {"uuid": "73f23b89-8b88-4569-be68-8a82256d6316", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2026-80554", "type": "seen", "source": "https://bsky.app/profile/stackflag.bsky.social/post/3mu2g2g4dtl2y", "content": "CVE-2026-80554 - linux\nThe kernel\u2019s support for certain IBM mainframe channel programs can create more pieces than the system allows, which could stop those programs from running correctly. This happens when the\u2026\n\nToo many irrelevant or confusing CVEs? Use stackflag.com\n\n#linux #CVE #infosec", "creation_timestamp": "2026-08-27T08:20:05.274764Z"}, {"uuid": "caba82e4-68e8-4941-a77d-86189dd09388", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2026-80557", "type": "seen", "source": "https://bsky.app/profile/stackflag.bsky.social/post/3mu2gmbvmhs2j", "content": "CVE-2026-80557 - linux\nA part of the Ceph storage software that runs inside the Linux operating system can be fooled into reading memory past the intended limit. This can lead to instability or a crash of the server\u2026\n\nToo many irrelevant or confusing CVEs? Use stackflag.com\n\n#linux #CVE #infosec", "creation_timestamp": "2026-08-27T08:30:04.903364Z"}, {"uuid": "2290b3c2-0998-4677-91d3-f9496cc35e65", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2026-80558", "type": "seen", "source": "https://bsky.app/profile/stackflag.bsky.social/post/3mu2gmdhwlv2t", "content": "CVE-2026-80558 - linux\nIf a Ceph storage system sends a corrupted map, the Linux kernel could try to use a non\u2011existent storage node number, causing it to read past the end of an internal list and crash. The problem is\u2026\n\nToo many irrelevant or confusing CVEs? Use stackflag.com\n\n#linux #CVE #infosec", "creation_timestamp": "2026-08-27T08:30:06.378750Z"}]}