6 Aug 2026, 07:41 UTC≈37 viewsread 6 August 2026
File
CVE-2026-34980 Author: HORKimhab None GitHub Link: https://github.com/HORKimhab/CVE-2026-34980
Channel
Exploits from Github
@xvnsd7ZxiH4zMTgy
On this record: Topic · Growth · Engagement · Posts · Citations · Cite this entry
1,524subscribers
+122 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
Register entry
| Telegram ID | -1002247977096 |
|---|---|
| Type | Channel |
| Username | @xvnsd7ZxiH4zMTgy |
| Created | Between 1 May 2024 and 31 October 2024 — 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 | 14 |
| Confirmed unchanged | 1 time, most recently 18 September 2026 |
| On Telegram | t.me/xvnsd7ZxiH4zMTgy |
Topic
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 17 September 2026 and assigned it the closest of 31 fixed categories, at 99% 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.
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 18 Sept 2026, 14:39 | 1,524 | +32 |
| 14 Sept 2026, 06:21 | 1,492 | +9 |
| 10 Sept 2026, 17:18 | 1,483 | +14 |
| 5 Sept 2026, 07:18 | 1,469 | +2 |
| 1 Sept 2026, 03:58 | 1,467 | +8 |
| 28 Aug 2026, 21:14 | 1,459 | +8 |
| 25 Aug 2026, 21:46 | 1,451 | +1 |
| 22 Aug 2026, 23:14 | 1,450 | +9 |
| 19 Aug 2026, 13:25 | 1,441 | +13 |
| 16 Aug 2026, 15:24 | 1,428 | +9 |
| 12 Aug 2026, 15:55 | 1,419 | +9 |
| 9 Aug 2026, 18:41 | 1,410 | +8 |
| 6 Aug 2026, 08:33 | 1,402 | no change |
| 6 Aug 2026, 08:26 | 1,402 | first reading |
Engagement
20 posts held, back to 3 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 1 page 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 20 posts for this entry, the most recent from 6 August 2026. An engagement rate over an empty window would be a number about nothing.
Recent posts
6 Aug 2026, 07:41 UTC≈37 viewsread 6 August 2026
File
CVE-2026-34990 Author: HORKimhab None GitHub Link: https://github.com/HORKimhab/CVE-2026-34990
6 Aug 2026, 07:40 UTC≈38 viewsread 6 August 2026
File
CVE-2026-65058 Author: iktok90-design None GitHub Link: https://github.com/iktok90-design/trezor-cve-2026-65058
6 Aug 2026, 07:40 UTC≈37 viewsread 6 August 2026
File
CVE-2024-2961 Author: HORKimhab The iconv() function in the GNU C Library versions 2.39 and older may overflow the output buffer passed to it by up to 4 bytes when converting strings to the ISO-2022-CN-EXT character set, which may be used to crash an application or overwrite a neighbouring variable. GitHub Link: https://github.com/HORKimhab/CVE-2022-31626-CVE-2024-2961-CVE-2019-6977
6 Aug 2026, 01:39 UTC≈66 views0 reactionsread 6 August 2026
File
CVE-2026-71211 Author: Abdivasiyev2008 None GitHub Link: https://github.com/Abdivasiyev2008/CVE-2026-71211-exploit
6 Aug 2026, 01:38 UTC≈66 viewsread 6 August 2026
File
CVE-2025-8110 Author: 9xh4kv Improper Symbolic link handling in the PutContents API in Gogs allows Local Execution of Code. GitHub Link: https://github.com/9xh4kv/CVE-2025-8110
6 Aug 2026, 01:38 UTC≈68 viewsread 6 August 2026
File
CVE-2026-63030 Author: AnggaTechI None GitHub Link: https://github.com/AnggaTechI/CVE-2026-63030
4 Aug 2026, 19:43 UTC≈116 viewsread 6 August 2026
File
CVE-2026-17566 Author: HackSpeak None GitHub Link: https://github.com/HackSpeak/CVE-2026-17566
4 Aug 2026, 19:42 UTC≈116 viewsread 6 August 2026
File
CVE-2026-63030 Author: rechandra None GitHub Link: https://github.com/rechandra/wp2exp-2026
4 Aug 2026, 19:42 UTC≈111 viewsread 6 August 2026
File
CVE-2026-31431 Author: dev1681 In the Linux kernel, the following vulnerability has been resolved: crypto: algifaead - Revert to operating out-of-place This mostly reverts commit 72548b093ee3 except for the copying of the associated data. There is no benefit in operating in-place in algifaead since the source and destination come from different mappings. Get rid of all the complexity added for in-place operation…
4 Aug 2026, 01:42 UTC≈134 viewsread 6 August 2026
File
CVE-2026-45585 Author: Donalhighnecked528 Microsoft is aware of a security feature bypass vulnerability in Windows publicly referred to as "YellowKey". The proof of concept for this vulnerability has been made public violating coordinated vulnerability best practices. We are issuing this CVE to provide mitigation guidance that can be implemented to protect against this vulnerability until the security upda…
4 Aug 2026, 01:42 UTC≈126 viewsread 6 August 2026
File
CVE-2026-46243 Author: 0xBlackash In the Linux kernel, the following vulnerability has been resolved: smb: client: reject userspace cifs.spnego descriptions cifs.spnego key descriptions contain authority-bearing fields such as pid, uid, creduid, and upcalltarget that cifs.upcall treats as kernel-originating inputs. However, userspace can also create keys of this type through requestkey(2) or addkey(2), allowing th…
Showing the 12 most recent of 20 posts we hold for @xvnsd7ZxiH4zMTgy. 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.
Mentions
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.
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.
Cite this entry
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.
“Exploits from Github” (@xvnsd7ZxiH4zMTgy), 1,524 subscribers as measured 18 September 2026. Telegram Register, tgregister.com/channel/xvnsd7ZxiH4zMTgy.
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.