Telegram RegisterThe public register of Telegram
Telegram profile photo for CVE

Channel

CVE

@cve0day

On this record: Growth · Engagement · Reactions · Posts · Cite this entry

4,373subscribers

+58 since we began measuring on 7 August 2026

Risers and fallers across the register · movement among entries of 3,162–10,000.

Register entry

Telegram ID-1003365638267
TypeChannel
Username@cve0day
CreatedBetween 1 November 2025 and 31 March 2026— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live30 August 2026
Measurements held9
Confirmed unchanged1 time, most recently 30 August 2026
On Telegramt.me/cve0day

Growth

4,3154,3734,3447 August 2026 — 4,315 subscribers8 August 2026 — 4,315 subscribers11 August 2026 — 4,326 subscribers15 August 2026 — 4,335 subscribers18 August 2026 — 4,340 subscribers21 August 2026 — 4,343 subscribers24 August 2026 — 4,346 subscribers28 August 2026 — 4,354 subscribers30 August 2026 — 4,373 subscribers7 August 202630 August 2026
9 measurements spanning 23 days, net +58. Dots are measurements; the straight line between them is drawn to join them, not to claim we know the path taken in between — snapshots are recorded only when a count changes, so gaps mean “no change observed”, never “interpolated”. The vertical axis spans 4,306–4,382 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
30 Aug 2026, 16:024,373+19
28 Aug 2026, 00:244,354+8
24 Aug 2026, 18:044,346+3
21 Aug 2026, 02:594,343+3
18 Aug 2026, 06:424,340+5
15 Aug 2026, 02:224,335+9
11 Aug 2026, 18:354,326+11
8 Aug 2026, 11:414,315no change
7 Aug 2026, 19:024,315first reading

Engagement

17 posts held, back to 19 July 2026the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 3 pagesof Telegram’s post history, 20 posts per page.

ERR · 30 days
25.2%
avg views ÷ 4,373 subscribers
Avg views / post
1,100
7 posts measured
Reaction rate
0.074%
reactions ÷ views · ER floor
Posts in window
7
of 17 held

ERR is average views per post over the last 30 days divided by subscribers, the definition TGStat uses, so this figure is comparable with the one you will see elsewhere. It falls structurally as a channel grows: a high ERR on a small channel and a low one on a large channel describe reach mathematics, not quality. We publish the figure and the sample it came from and pass no verdict on it.

ER is defined industry-wide as (forwards + reactions + comments) ÷ views— note the denominator is views, not subscribers. Telegram’s public web preview carries views and reactions but not forward or comment counts, so the reaction rate above is the reactions term only and is therefore a floor: the true ER for this channel is higher by an amount we have not measured and will not estimate. It is computed over the 2 of 7 measured posts that carry a reaction reading, and over those same posts' views.

What these figures were computed from
WindowRolling 30 days · latest post in window 7 August 2026
Posts held17 (19 July 20267 August 2026)
Views total7,718
Reactions total2
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken8 Aug 2026, 11:49 UTC

Views are a single reading per post, taken at the time above. A post published in the last day or two is still accumulating views, which pulls the 30-day average down slightly. That is a property of the standard definition rather than a fault in it, so we keep the definition rather than “correcting” the number into something nobody can reproduce.

Precision. Telegram publishes view counts on its public widget in short form — 8.12K, 3.7M — so any reading at or above 1,000 reaches us rounded to three significant figures, and only counts below 1,000 are exact. Averages and rates derived from them are shown to the same precision rather than to the unit: a figure like 3,701,250 would assert digits nobody measured.

Reaction counts are published per emoji and rounded the same way, so a total below 1,000 is exact and a larger one is a sum that may carry a rounded component from each emoji above 1,000. Because it is a sum, it does not look rounded — read a large reaction total as three significant figures per contributing emoji rather than as the figure it prints.

Reaction mix

29 reactions across 9 posts, in 4 distinct kinds. The most used accounts for 72.4% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
2172.4%
🔥413.8%
❤‍🔥310.3%
🎉13.45%

No sentiment is inferred, and none should be read in. This table is ordered by count and by nothing else. Emoji do not carry stable meaning across languages or communities — 🙏 is thanks in one channel and mourning in another — so we publish which ones were pressed and how often, and pass no judgement on what an audience meant by them.

Precision. Telegram publishes reaction counts per emoji and short-forms each one — 4.34K, 1.2M — so any single kind at or above 1,000 reaches us at three significant figures, and only counts below 1,000 are exact. The shares above are ratios of those figures and carry the same error. This is also why the total here can differ slightly from a reaction total printed elsewhere on the page: both are sums of the same rounded parts, taken over samples with different edges.

Coverage. Reactions were read on 9 of the 17 sampled posts in this sample. Summed by Telegram’s own count on each post — not by adding up the per-emoji breakdown above — those same posts carry 29reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 17 most recent posts we hold, published 19 July 2026 to 7 August 2026, using the newest reading held for each. Telegram Stars are excluded: they are a payment, not a reaction, and they have their own section.

Recent posts

4 Aug 2026, 12:15 UTC≈1,220 views1 reactionsread 8 August 2026
File

CVE-2026-46243 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 those fields to be su

1

2 Aug 2026, 12:10 UTC≈1,470 views1 reactionsread 8 August 2026
File

CVE-2026-33937 Handlebars provides the power necessary to let users build semantic templates. In versions 4.0.0 through 4.7.8, Handlebars.compile() accepts a pre-parsed AST object in addition to a template string. The value field of a NumberLiteral AST node is emitted directly into the generated JavaScript without quoting or sanitization. An attacker who can supply a crafted AST to compile() can therefore inject and

1

30 Jul 2026, 12:22 UTC≈1,740 viewsread 8 August 2026
File

CVE-2025-26466 A flaw was found in the OpenSSH package. For each ping packet the SSH server receives, a pong packet is allocated in a memory buffer and stored in a queue of packages. It is only freed when the server/client key exchange has finished. A malicious client may keep sending such packages, leading to an uncontrolled increase in memory consumption on the server side. Consequently, the server may become unav

29 Jul 2026, 11:50 UTC≈1,790 views2 reactionsread 8 August 2026
File

CVE-2026-41179 Rclone is a command-line program to sync files and directories to and from different cloud storage providers. Starting in version 1.48.0 and prior to version 1.73.5, the RC endpoint operations/fsinfo is exposed without AuthRequired: true and accepts attacker-controlled fs input. Because rc.GetFs(...) supports inline backend definitions, an unauthenticated attacker can instantiate an attacker-controlle

2

28 Jul 2026, 06:59 UTC≈1,800 views13 reactionsread 8 August 2026
Photo

Hey Hunter's, DarkShadow is here back again! 💀File upload extension bypass new method✅ in media upload section you can upload files like: .png .jpg .txt .mov but if you upload any php file it block: .php .jpg.php .php7 .shtml The bypass is: ".php " (just add a simple space after .php) This is a very effective and simple way to bypass file upload vulnerbaility. so guy's if you really enjoy to read my methods sho

9❤‍🔥3🎉1

26 Jul 2026, 12:57 UTC≈1,690 viewsread 8 August 2026
File

CVE-2026-52813 Gogs is an open source self-hosted Git service. Prior to 0.14.3, organization names containing path traversal sequences (../) are accepted by Gogs, and repositories under them are written to paths following these path traversals. This allows storing/retrieving data for repositories at arbitrary locations on the filesystem. By creating nested structure of Git repositories, one can overwrite the other's

25 Jul 2026, 13:06 UTC≈1,840 viewsread 8 August 2026
File

CVE-2025-32432 Craft is a flexible, user-friendly CMS for creating custom digital experiences on the web and beyond. Starting from version 3.0.0-RC1 to before 3.9.15, 4.0.0-RC1 to before 4.14.15, and 5.0.0-RC1 to before 5.6.17, Craft is vulnerable to remote code execution. This is a high-impact, low-complexity attack vector. This issue has been patched in versions 3.9.15, 4.14.15, and 5.6.17, and is an additional fi

Showing the 12 most recent of 17 posts we hold for @cve0day. 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.

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 30 August 2026 — this entry's latest reading, not the date you are reading this.

“CVE” (@cve0day), 4,373 subscribers as measured 30 August 2026. Telegram Register, tgregister.com/channel/cve0day.

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.