Telegram RegisterThe public register of Telegram
Telegram profile photo for Latest Published CVE

Channel

Latest Published CVE

@latest_published_cve

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

190subscribers

+8 since we began measuring on 7 August 2026

Risers and fallers across the register · movement among entries of Under 1,000.

Register entry

Telegram ID-1002006315788
TypeChannel
Username@latest_published_cve
CreatedBetween 1 November 2023 and 30 April 2024— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded8 August 2026
Last confirmed live29 August 2026
Measurements held5
Confirmed unchanged1 time, most recently 29 August 2026
On Telegramt.me/latest_published_cve

Growth

1821901867 August 2026 — 182 subscribers8 August 2026 — 182 subscribers14 August 2026 — 183 subscribers21 August 2026 — 187 subscribers29 August 2026 — 190 subscribers7 August 202629 August 2026
5 measurements spanning 21 days, net +8. 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 181–191 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
29 Aug 2026, 02:13190+3
21 Aug 2026, 04:33187+4
14 Aug 2026, 17:25183+1
8 Aug 2026, 12:46182no change
7 Aug 2026, 18:17182first reading

Engagement

20 posts held, back to 8 August 2026the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 1 pageof Telegram’s post history, 20 posts per page.

ERR · 30 days
0.579%
avg views ÷ 190 subscribers
Avg views / post
1.1
20 posts measured
Reaction rate
this channel exposes no reaction counts
Posts in window
20
of 20 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.

What these figures were computed from
WindowRolling 30 days · latest post in window 8 August 2026
Posts held20 (8 August 20268 August 2026)
Views total22
Reactions total
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken8 Aug 2026, 12:46 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.

Recent posts

8 Aug 2026, 11:00 UTC1 viewsread 8 August 2026

2026-08-08 20:00:35.283966 (UTC +09:00) 1. CVE-2026-8798 - Source: 91579145-5d7b-4cc5-b925-a0262ff19630 - Published: 2026-08-08T01:16:31.393 - LastModified: 2026-08-08T01:16:31.393 - CVSS: None (None) - Exploitability: None - Impact: None - CWE: CWE-835 Loop with Unreachable Exit Condition ('Infinite Loop') In Bouncy Castle for Java FIPS (BC-FJA) before bc-fips 2.1.3, the native entropy source used on Intel platfor

8 Aug 2026, 09:00 UTC1 viewsread 8 August 2026

>>> Continue... (1) https://github.com/klever-io/klever-go/releases/tag/v1.7.18 (2) https://github.com/klever-io/klever-go/security/advisories/GHSA-fw38-pc54-jvx9 18. CVE-2026-52878 - Source: [email protected] - Published: 2026-08-07T23:17:04.593 - LastModified: 2026-08-07T23:17:04.593 - CVSS: 7.5 (HIGH) - Exploitability: 3.9 - Impact: 3.6 - CWE: CWE-476 NULL Pointer Dereference Klever-Go is the Go i

8 Aug 2026, 09:00 UTC1 viewsread 8 August 2026

>>> Continue... - Published: 2026-08-07T23:17:03.670 - LastModified: 2026-08-07T23:17:03.670 - CVSS: 7.5 (HIGH) - Exploitability: 3.9 - Impact: 3.6 - CWE: CWE-400 Uncontrolled Resource Consumption Klever-Go is the Go implementation of the Klever blockchain protocol. Prior to 1.7.18, the P2P resolver request handling logic is vulne... >> https://www.cve.org/CVERecord?id=CVE-2026-47249 - Ref. (1) https://github.com/

8 Aug 2026, 07:02 UTC1 viewsread 8 August 2026

>>> Continue... (2) https://github.com/home-assistant/core/security/advisories/GHSA-2xqv-hwrf-983f 34. CVE-2026-66061 - Source: [email protected] - Published: 2026-08-07T21:17:29.693 - LastModified: 2026-08-07T21:17:29.693 - CVSS: 7.1 (HIGH) - Exploitability: 2.5 - Impact: 4.0 - CWE: CWE-862 Missing Authorization Home Assistant is open source home automation software focused on local control and priv

8 Aug 2026, 07:02 UTC1 viewsread 8 August 2026

>>> Continue... - Exploitability: None - Impact: None - CWE: CWE-285 Improper Authorization Pathling is a set of tools that make it easier to use FHIR and clinical terminology within health data analytics. Prior to version 2.0.... >> https://www.cve.org/CVERecord?id=CVE-2026-47663 - Ref. (1) https://github.com/aehrc/pathling/security/advisories/GHSA-q62q-2m46-r7rv 29. CVE-2026-47664 - Source: security-advisories

8 Aug 2026, 07:02 UTC1 viewsread 8 August 2026

>>> Continue... >> https://www.cve.org/CVERecord?id=CVE-2026-19244 - Ref. (1) https://gist.github.com/YLChen-007/3de5f50d167a878f7530f57ed018d508 (2) https://github.com/HKUDS/nanobot/ (3) https://github.com/HKUDS/nanobot/issues/4435 (4) https://github.com/HKUDS/nanobot/pull/4436 (5) https://github.com/HKUDS/nanobot/releases/tag/v0.3.0 (6) https://vuldb.com/cve/CVE-2026-19244 (7) https://vuldb.com/submit/865116 (8)

8 Aug 2026, 07:02 UTC1 viewsread 8 August 2026

>>> Continue... - Published: 2026-08-07T20:16:52.457 - LastModified: 2026-08-07T20:16:52.457 - CVSS: 7.5 (HIGH) - Exploitability: 3.9 - Impact: 3.6 - CWE: CWE-20 Improper Input Validation, CWE-400 Uncontrolled Resource Consumption, CWE-674 Uncontrolled Recursion HAPI FHIR is a complete implementation of the HL7 FHIR standard for healthcare interoperability in Java. Prior to 6.9.11, XhtmlParser.j... >> https://www.c

8 Aug 2026, 07:02 UTC1 viewsread 8 August 2026

>>> Continue... Consul Community Edition and Consul Enterprise 1.18.21 through 2.0.2 are vulnerable to a partial arbitrary file read when configured to... >> https://www.cve.org/CVERecord?id=CVE-2026-19017 - Ref. (1) https://discuss.hashicorp.com/t/hcsec-2026-25-multiple-vulnerabilities-impacting-hashicorp-consul/77629 8. CVE-2026-19113 - Source: [email protected] - Published: 2026-08-07T20:16:50.787 - LastM

8 Aug 2026, 07:02 UTC1 viewsread 8 August 2026

2026-08-08 16:02:16.308216 (UTC +09:00) 1. CVE-2026-15970 - Source: [email protected] - Published: 2026-08-07T20:16:49.863 - LastModified: 2026-08-07T20:16:49.863 - CVSS: 4.2 (MEDIUM) - Exploitability: 1.6 - Impact: 2.5 - CWE: CWE-647 Use of Non-Canonical URL Paths for Authorization Decisions Consul Community Edition and Consul Enterprise 1.20.1 through 2.0.2 are vulnerable to an L7 intention authorization byp

8 Aug 2026, 05:01 UTC3 viewsread 8 August 2026

>>> Continue... crypto-js is a JavaScript library of crypto standards. Versions of crypto-js prior to 4.0.0 generate randomness in CryptoJS.lib.WordArr... >> https://www.cve.org/CVERecord?id=CVE-2026-71851 - Ref. (1) https://github.com/brix/crypto-js/commit/b405ff597fb3ac76a7bdfbc72dca10ba1079b1d5 (2) https://github.com/brix/crypto-js/security/advisories/GHSA-rg76-677x-56q9 (3) https://www.coinspect.com/blog/ill-bl

8 Aug 2026, 05:01 UTC1 viewsread 8 August 2026

>>> Continue... (3) https:github.com/getkirby/kirby/commit/469c5a1a2973811591d996bc967eead3565df1f0 29. CVE-2026-70561 - Source: [email protected] - Published: 2026-08-07T19:18:53.277 - LastModified: 2026-08-07T19:18:53.277 - CVSS: 6.5 (MEDIUM) - Exploitability: 2.8 - Impact: 3.6 - CWE: CWE-639 Authorization Bypass Through User-Controlled Key TestLink 1.9.20 and prior contains an insecure direct object ref

8 Aug 2026, 05:01 UTC1 viewsread 8 August 2026

>>> Continue... (1) https://github.com/Andyov0/cve/issues/1 (2) https://vuldb.com/cve/CVE-2026-19230 (3) https://vuldb.com/submit/864910 (4) https://vuldb.com/vuln/386994 (5) https://vuldb.com/vuln/386994/cti (6) https://www.sourcecodester.com/ 24. CVE-2026-19231 - Source: [email protected] - Published: 2026-08-07T19:17:40.840 - LastModified: 2026-08-07T19:17:40.840 - CVSS: 7.3 (HIGH) - Exploitability: 3.9 - Impact: 3

Showing the 12 most recent of 20 posts we hold for @latest_published_cve. 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 29 August 2026 — this entry's latest reading, not the date you are reading this.

“Latest Published CVE” (@latest_published_cve), 190 subscribers as measured 29 August 2026. Telegram Register, tgregister.com/channel/latest_published_cve.

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.