Channel
@CVEtracker
On this record: Growth · Engagement · Posts · Citations · Cite this entry
383subscribers
+14 since we began measuring on 8 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1002230009192 |
|---|---|
| Type | Channel |
| Username | @CVEtracker |
| Created | Between 1 June 2024 and 30 September 2024 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 8 August 2026 |
| Last confirmed live | 30 August 2026 |
| Measurements held | 5 |
| Confirmed unchanged | 1 time, most recently 30 August 2026 |
| On Telegram | t.me/CVEtracker |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 30 Aug 2026, 07:54 | 383 | +5 |
| 22 Aug 2026, 11:49 | 378 | +6 |
| 15 Aug 2026, 03:12 | 372 | +3 |
| 8 Aug 2026, 08:38 | 369 | no change |
| 8 Aug 2026, 06:31 | 369 | first reading |
20 posts held, back to 8 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.
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.
| Window | Rolling 30 days · latest post in window 8 August 2026 |
|---|---|
| Posts held | 20 (8 August 2026 – 8 August 2026) |
| Views total | 34 |
| Reactions total | — |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 8 Aug 2026, 06:31 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.
CVE-2026-13505 - Zeroisation of sensitive key material on garbage collection relies on finalization CVE ID :CVE-2026-13505 Published : Aug. 8, 2026, 2:17 a.m. | 1 hour, 56 minutes ago Description :In Bouncy Castle for Java FIPS (BC-FJA) before bc-fips 1.0.2.7 (1.0.X series), 2.0.2 (2.0.X series) and 2.1.3 (2.1.X series), sensitive key material held by the AES and DESede engines, the SP 800-90A DRBGs, SymmetricSecret…
CVE-2026-8798 - Native entropy source retries the CPU entropy instructions without limit CVE ID :CVE-2026-8798 Published : Aug. 8, 2026, 1:16 a.m. | 2 hours, 57 minutes ago Description :In Bouncy Castle for Java FIPS (BC-FJA) before bc-fips 2.1.3, the native entropy source used on Intel platforms retried the CPU entropy instructions without any bound. RDSEED and RDRAND report failure through their carry flag, and th…
CVE-2026-52879 - Klever-Go: Unbounded goroutine spawn on direct-message ingress enables peer-driven DoS CVE ID :CVE-2026-52879 Published : Aug. 7, 2026, 11:17 p.m. | 56 minutes ago Description :Klever-Go is the Go implementation of the Klever blockchain protocol. In versions 1.7.14 through 1.7.17, the direct-message ingress handler spawns a new goroutine for every incoming direct message before the processor-level a…
CVE-2026-52880 - Klever-Go: REST API slow-header connection exhaustion via Gin Engine.Run CVE ID :CVE-2026-52880 Published : Aug. 7, 2026, 11:17 p.m. | 56 minutes ago Description :Klever-Go is the Go implementation of the Klever blockchain protocol. Versions from 1.7.14 through 1.7.17 are vulnerable to a remotely triggerable denial of service. Both REST APIs are started with the Gin Engine.Run convenience method, wh…
CVE-2026-52878 - Klever-Go: Unauthenticated nil-pointer DoS in P2P transaction validation can halt the chain CVE ID :CVE-2026-52878 Published : Aug. 7, 2026, 11:17 p.m. | 56 minutes ago Description :Klever-Go is the Go implementation of the Klever blockchain protocol. Versions 1.7.14 through 1.7.17 are vulnerable to a nil-pointer panic triggered by a protobuf Transaction whose embedded RawData sub-message is omitted…
CVE-2026-48122 - Workspace settings can override executable and Gemfile paths used by the Ruby LSP VS Code extension CVE ID :CVE-2026-48122 Published : Aug. 7, 2026, 11:17 p.m. | 56 minutes ago Description :Ruby LSP is an implementation of the language server protocol for Ruby. Several workspace-level settings in the Ruby LSP VS Code extension prior to version 0.10.4 could override the path to the Ruby executable, t…
CVE-2026-49343 - Klever-Go KVM: Throttler slot leak in trie account-data sync causes epoch bootstrap / state sync DoS CVE ID :CVE-2026-49343 Published : Aug. 7, 2026, 11:17 p.m. | 56 minutes ago Description :Klever-Go is the Go implementation of the Klever blockchain protocol. In versions prior to 1.7.18, the account-data trie syncers are vulnerable to a resource-exhaustion flaw that leaks bounded throttler slots on…
CVE-2026-48120 - Kakoune has a Critical RCE via Autorestore Backup Filename Injection CVE ID :CVE-2026-48120 Published : Aug. 7, 2026, 11:17 p.m. | 56 minutes ago Description :Kakoune is a code editor. Prior to version 2026.05.21, the bundled, enabled by default, `autorestore.kak` script can be exploited by malicious backup files leading to arbitrary kakoune and shell commands being executed by simply opening a file…
CVE-2026-48026 - lakeFS vulnerable to stored XSS in rendered markdown previews via raw HTML CVE ID :CVE-2026-48026 Published : Aug. 7, 2026, 11:17 p.m. | 56 minutes ago Description :lakeFS is an open-source tool that transforms object storage into a Git-like repositories. Prior to version 1.81.1 of the open source edition and 1.84.0 of the enterprise edition, lakeFS Web UI renders markdown files from repository obje…
CVE-2026-48047 - XWiki Platform vulnerable to potential arbitrary file writing using path traversal from (subwiki) admin CVE ID :CVE-2026-48047 Published : Aug. 7, 2026, 11:17 p.m. | 56 minutes ago Description :XWiki Platform WebJars API is a package for XWiki, a generic wiki platform. Starting with version 9.6-rc-1 and prior to versions 16.10.17, 17.4.9, and 17.10.3, a potential path traversal vulnerability allow a…
CVE-2026-47249 - Klever-Go KVM: Hash-array amplification in P2P resolver request handling CVE ID :CVE-2026-47249 Published : Aug. 7, 2026, 11:17 p.m. | 56 minutes ago Description :Klever-Go is the Go implementation of the Klever blockchain protocol. Prior to 1.7.18, the P2P resolver request handling logic is vulnerable to hash-array amplification. A connected peer can send a compressed RequestDataType_HashArrayType …
CVE-2026-47127 - Ghostfolio has a Stripe subscription bypass CVE ID :CVE-2026-47127 Published : Aug. 7, 2026, 11:17 p.m. | 56 minutes ago Description :Ghostfolio is an open source wealth management software. Prior to version 3.4.0, Ghostfolio's Stripe checkout success-URL handler at `GET /api/v1/subscription/stripe/callback?checkoutSessionId=` retrieves the Stripe Checkout Session by ID and unconditionally grants a …
Showing the 12 most recent of 20 posts we hold for @CVEtracker. 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.
Citation-graph rank — 961,531 of 1,629,452 entries in the measured graph. A weighted position computed from the forward and mention edges below — republished posts weigh more than named mentions — and recomputed periodically, over the whole graph. Published only as this ordinal position, never as a score: a position is a fact, and a score printed beside one channel’s name would read as a verdict this register does not make. The two counts beneath stay separate for the same reason mentions are never summed with forwards anywhere else on this page — a named-by count costs nothing to manufacture. The top 100 by this measure, or how it is computed.
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.
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 tracker” (@CVEtracker), 383 subscribers as measured 30 August 2026. Telegram Register, tgregister.com/channel/CVEtracker.
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.