Channel
@CVEIntelligence
On this record: Topic · Growth · Engagement · Posts · Citations · Handles named that no longer answer · Cite this entry
4,066subscribers
+448 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of 3,162–10,000.
| Telegram ID | -1003503160660 |
|---|---|
| Type | Channel |
| Username | @CVEIntelligence |
| Created | Between 1 December 2025 and 31 May 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 6 August 2026 |
| Last confirmed live | 18 September 2026 |
| Measurements held | 15 |
| Confirmed unchanged | 1 time, most recently 18 September 2026 |
| On Telegram | t.me/CVEIntelligence |
Hacking & security — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-FP8, prompt version 1) read this channel’s own recent posts on 14 September 2026 and assigned it the closest of 31 fixed categories, at 98% confidence. This is a model’s judgement about what the channel is likely to be about, not a fact this register measured the way a subscriber count or a view count is measured — it can be revised on a later pass, and it carries no weight anywhere else on this page. How this classification works, and why it has no browse page of its own yet.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 18 Sept 2026, 19:57 | 4,066 | +39 |
| 14 Sept 2026, 18:57 | 4,027 | +33 |
| 11 Sept 2026, 07:58 | 3,994 | +49 |
| 6 Sept 2026, 17:20 | 3,945 | +44 |
| 1 Sept 2026, 23:54 | 3,901 | +30 |
| 29 Aug 2026, 13:25 | 3,871 | +18 |
| 26 Aug 2026, 13:13 | 3,853 | +8 |
| 23 Aug 2026, 07:16 | 3,845 | +52 |
| 19 Aug 2026, 20:02 | 3,793 | +30 |
| 16 Aug 2026, 22:24 | 3,763 | +48 |
| 13 Aug 2026, 05:18 | 3,715 | +42 |
| 9 Aug 2026, 22:21 | 3,673 | +49 |
| 7 Aug 2026, 01:30 | 3,624 | +6 |
| 6 Aug 2026, 18:15 | 3,618 | no change |
| 6 Aug 2026, 18:04 | 3,618 | first reading |
60 posts held, back to 6 August 2026 — the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 3 pages of Telegram’s post history, 20 posts per page.
Nothing published in the last 30 days. ERR and ER are rolling 30-day measures, so there is nothing to compute — we hold 60 posts for this entry, the most recent from 7 August 2026. An engagement rate over an empty window would be a number about nothing.
📄 Exhaustive Intelligence Report: CVE-2026-64676 🏛 Metadata & Status • Severity: MEDIUM (5.7) • State: Received • Published: 2026-08-07 • Modified: 2026-08-07 • Assigner: GitHub_M • Date Reserved: 2026-07-20 📝 Descriptions • Main: Kata Containers is an open source implementation of lightweight Virtual Machines (VMs) that perform like containers. In versions prior to 4.0.0, the kata-agent is vulnerable to an authori…
📄 Exhaustive Intelligence Report: CVE-2026-58262 🏛 Metadata & Status • Severity: HIGH (7.1) • State: Received • Published: 2026-08-07 • Modified: 2026-08-07 • Assigner: GitHub_M • Date Reserved: 2026-06-29 📝 Descriptions • Main: Klever-Go is the Go implementation of the Klever blockchain protocol. Prior to 1.7.20, header signature verification counts the unused padding bits of the PubKeysBitmap toward the two-third…
📄 Exhaustive Intelligence Report: CVE-2026-48170 🏛 Metadata & Status • Severity: CRITICAL (9.1) • State: Received • Published: 2026-08-07 • Modified: 2026-08-07 • Assigner: GitHub_M • Date Reserved: 2026-05-20 📝 Descriptions • Main: `scim-patch`, a library to perform SCIM patch, prior to version 0.9.1 performs prototype pollution when applying a SCIM PATCH operation whose `value` object contains a key like `"__prot…
📄 Exhaustive Intelligence Report: CVE-2026-48169 🏛 Metadata & Status • Severity: HIGH (8.8) • State: Received • Published: 2026-08-07 • Modified: 2026-08-07 • Assigner: GitHub_M • Date Reserved: 2026-05-20 📝 Descriptions • Main: PraisonAI is a multi-agent teams system. Versions prior to 0.1.4 of the PraisonAI Platform API have two authorization failures that together break workspace isolation. The service layer for…
📄 Exhaustive Intelligence Report: CVE-2026-47243 🏛 Metadata & Status • Severity: CRITICAL (9.2) • State: Received • Published: 2026-08-07 • Modified: 2026-08-07 • Assigner: GitHub_M • Date Reserved: 2026-05-18 📝 Descriptions • Main: Kata Containers is an open source project focusing on a standard implementation of lightweight Virtual Machines (VMs) that perform like containers. Prior to 3.31.0, the runtime-rs stand…
📄 Exhaustive Intelligence Report: CVE-2026-46405 🏛 Metadata & Status • Severity: MEDIUM (5.3) • State: Received • Published: 2026-08-07 • Modified: 2026-08-07 • Assigner: GitHub_M • Date Reserved: 2026-05-13 📝 Descriptions • Main: OpenBao is an open source identity-based secrets management system. Prior to version 2.5.4, in OpenBao's Kerberos auth method on the `GET` handler, or when an `Authorization: Negotiate` h…
📄 Exhaustive Intelligence Report: CVE-2026-45808 🏛 Metadata & Status • Severity: HIGH (7.1) • State: Received • Published: 2026-08-07 • Modified: 2026-08-07 • Assigner: GitHub_M • Date Reserved: 2026-05-13 📝 Descriptions • Main: OpenBao is an open source identity-based secrets management system. Prior to version 2.5.4, OpenBao's namespaces provide multi-tenant separation. A tenant who intentionally leaks lease iden…
📄 Exhaustive Intelligence Report: CVE-2026-11743 🏛 Metadata & Status • Severity: MEDIUM (6.6) • State: Received • Published: 2026-08-07 • Modified: 2026-08-07 • Assigner: zephyr • Date Reserved: 2026-06-09 📝 Descriptions • Main: The SF32LB MPI QSPI NOR flash driver (drivers/flash/flash_sf32lb_mpi_qspi_nor.c) validated the flash offset and length on its read and write paths with the test (offset + size) > data->size…
📄 Exhaustive Intelligence Report: CVE-2026-9031 🏛 Metadata & Status • Severity: MEDIUM (6.8) • State: Received • Published: 2026-08-07 • Modified: 2026-08-07 • Assigner: TPLink • Date Reserved: 2026-05-19 📝 Descriptions • Main: An input validation vulnerability exists in the HTTP-WRITEOEM handler due to insufficient validation of user-supplied data before it is processed by internal flash-write handling logic. …
📄 Exhaustive Intelligence Report: CVE-2026-9030 🏛 Metadata & Status • Severity: MEDIUM (6.8) • State: Received • Published: 2026-08-07 • Modified: 2026-08-07 • Assigner: TPLink • Date Reserved: 2026-05-19 📝 Descriptions • Main: A denial-of-service vulnerability exists in httpd service on Archer A6 v4 where the asynchronous systool instruction handlng path in httpd does not properly synchronize or safely manage conc…
📄 Exhaustive Intelligence Report: CVE-2026-71381 🏛 Metadata & Status • Severity: MEDIUM (4) • State: Received • Published: 2026-08-07 • Modified: 2026-08-07 • Assigner: adobe • Date Reserved: 2026-08-06 📝 Descriptions • Main: Adobe Genuine Software Integrity Service was affected by an Incorrect Authorization vulnerability that could result in a Security feature bypass. An attacker could have leveraged this vulnerab…
📄 Exhaustive Intelligence Report: CVE-2026-70624 🏛 Metadata & Status • Severity: N/A (N/A) • State: Rejected • Published: 2026-08-07 • Modified: 2026-08-07 • Assigner: VulnCheck • Date Reserved: 2026-08-04 📝 Descriptions • Main: Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority. • @CVEIntelligence • @CVEIntelligencebot
Showing the 12 most recent of 60 posts we hold for @CVEIntelligence. View and reaction counts are the latest single reading for each post, not a live figure, and a recent post is still accumulating both. A view count marked ≈ was rounded by Telegram before we ever saw it — t.me prints views in full below 1,000 and to three significant figures above, so ≈1,200,000 means somewhere between 1,150,000 and 1,249,999. Unmarked counts are exact. Text is reproduced from the public post preview and truncated for length.
Named by 1 registered channel — every channel on the register whose own posts have named this one, by its current username or any other username it currently holds, merged from two separately captured readings of the same fact so a namer caught by only one of them is not missed and a namer both caught is not counted twice. A username this channel has since dropped is not matched — that handle may belong to someone else now, and crediting today’s namer to yesterday’s owner would misattribute it.
Named by
Channels on the register whose posts name this channel's handle.
Names
Channels on the register whose handles appear in this channel's posts.
A mention is a weaker signal than a forward and is counted separately for that reason — naming a channel is not republishing it, and a handle in a post body is easy to place deliberately. The post counts beside each row below are distinct posts in which the handle appeared, from posts we have read on both sides — the “Named by N registered channels” figure above is a different count, of distinct NAMING CHANNELS rather than posts, and is not the sum of the rows under it.
@CVEIntelligence named 1 handle that resolve to nothing today. That is a fact about the reference, not necessarily a fact about the handle’s history — see the two groups below.
Most of these may never have existed as a live channel at all. A handle a channel names can be a typo, an aspirational name nobody registered, or a channel that was already gone before this one ever mentioned it. Unless a row below is marked evidenced, all we know is that it references a handle that is not a live channel today — not that anything “died”. How this is measured.
References a handle that is not a live channel — we have no record it ever was one.
A live page changes as we take new readings, so a citation should name the measurement it is based on, not just the URL. The line below cites the subscriber count as measured 18 September 2026 — this entry's latest reading, not the date you are reading this.
“CVE Intelligence” (@CVEIntelligence), 4,066 subscribers as measured 18 September 2026. Telegram Register, tgregister.com/channel/CVEIntelligence.
Full measurement history, CC BY 4.0. Every reading this register holds for this entry, not just the latest one, as a dated, downloadable record: CSV · JSON. Free to use with attribution to tgregister.com. Each file carries its own generation timestamp, which is the figure to cite for exactly when the data was retrieved.