Telegram RegisterThe public register of Telegram
Telegram profile photo for 🛡 Cybersecurity & Privacy 🛡 - CVEs

Channel

🛡 Cybersecurity & Privacy 🛡 - CVEs

@cibsecurity_CVEs

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

459subscribers

+5 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-1002131512958
TypeChannel
Username@cibsecurity_CVEs
CreatedBetween 1 November 2023 and 31 May 2024— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded8 August 2026
Last confirmed live30 August 2026
Measurements held4
Confirmed unchanged1 time, most recently 30 August 2026
On Telegramt.me/cibsecurity_CVEs

Growth

454459456.57 August 2026 — 454 subscribers8 August 2026 — 454 subscribers15 August 2026 — 457 subscribers30 August 2026 — 459 subscribers7 August 202630 August 2026
4 measurements spanning 23 days, net +5. 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 453–460 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
30 Aug 2026, 08:35459+2
15 Aug 2026, 15:26457+3
8 Aug 2026, 05:00454no change
7 Aug 2026, 12:32454first reading

Engagement

20 posts held, back to 4 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
1.07%
avg views ÷ 459 subscribers
Avg views / post
4.9
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 5 August 2026
Posts held20 (4 August 20265 August 2026)
Views total98
Reactions total
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken8 Aug 2026, 05:00 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

5 Aug 2026, 02:30 UTC19 viewsread 8 August 2026

‼️ CVE-2026-18895 ‼️ A vulnerability was found in UTT HiPER 1250GW up to 3.2.7210907180535. Impacted is the function strcpy of the file goformAPSecurity5g. Performing a manipulation of the argument cipher results in stackbased buffer overflow. It is possible to initiate the attack remotely. The exploit has been made public and could be used. The vendor was contacted early about this disclosure but did not respond in

5 Aug 2026, 01:30 UTC19 viewsread 8 August 2026

‼️ CVE-2026-18859 ‼️ A vulnerability was identified in ESAFENET CDG up to 20260615. Affected is an unknown function of the file CDGServer3ukeyusbkeylogindojojs. Such manipulation of the argument keyid leads to sql injection. The attack may be performed from remote. The exploit is publicly available and might be used. The vendor was contacted early about this disclosure but did not respond in any way. 📖 Read more.

5 Aug 2026, 01:30 UTC8 viewsread 8 August 2026

‼️ CVE-2026-18856 ‼️ A vulnerability was determined in Poesis Rhymix CMS up to 2.1.33. This impacts the function procImporterAdminCheckXmlFile of the file modulesimporterimporter.admin.controller.php of the component Data Import Module. This manipulation of the argument filename causes serverside request forgery. The attack is possible to be carried out remotely. The exploit has been publicly disclosed and may be ut

5 Aug 2026, 00:30 UTC4 viewsread 8 August 2026

‼️ CVE-2026-46334 ‼️ OpenSIPS is a Session Initiation Protocol SIP server implementation. Versions prior to 3.6.6 and 4.0.0rc1 contain a denial of service vulnerability in the SDP bandwidthline parsing logic. A SIP request with ContentType applicationsdp and a malformed sessionlevel SDP bandwidth line missing the required colon delimiter can corrupt parsed SDP bandwidth metadata. When a route or module subsequently

5 Aug 2026, 00:30 UTC4 viewsread 8 August 2026

‼️ CVE-2026-45809 ‼️ OpenSIPS is a Session Initiation Protocol SIP server implementation. Versions prior to 3.6.6 and 4.0.0rc1 contain a denial of service vulnerability in the watcherinfo generation functionality. An attacker can create an oversized watcher entry by sending a SUBSCRIBE Event presence request with a long From URI, and then trigger presence.winfo watcherinfo XML generation for the same presentity. Ope

5 Aug 2026, 00:30 UTC4 viewsread 8 August 2026

‼️ CVE-2026-45705 ‼️ OpenSIPS is a Session Initiation Protocol SIP server implementation. In versions prior to 3.6.6 and 4.0.0rc1, the findlinedelimiter function in the multipart body parser performs an outofbounds read via strncmp when searching for MIME boundary delimiters. After finding a pattern near the end of the body, the function compares delimiter.len bytes typically 2070 starting from a position at or pas

5 Aug 2026, 00:30 UTC4 viewsread 8 August 2026

‼️ CVE-2026-18854 ‼️ A vulnerability has been found in Shandong Hoteam PDM Product Data Management System up to 8.3.10. The impacted element is the function GetStoredClassByFilter of the file BaseBaseService.asmxDataService. The manipulation of the argument FilterString leads to sql injection. Remote exploitation of the attack is possible. The exploit has been disclosed to the public and may be used. The vendor was

5 Aug 2026, 00:30 UTC4 viewsread 8 August 2026

‼️ CVE-2026-18853 ‼️ A security vulnerability has been detected in ZomboDroid Meme Generator App 4.6830 on Android. This issue affects the function t5.l.c of the component com.zombodroid.MemeGenerator. Such manipulation leads to path traversal. Local access is required to approach this attack. The exploit has been disclosed publicly and may be used. The vendor was contacted early about this disclosure but did not re

5 Aug 2026, 00:30 UTC3 viewsread 8 August 2026

‼️ CVE-2026-18852 ‼️ A vulnerability has been found in epsillacloud vectordb up to 0.3.18df5a5f5afb85a2376a0f2f316c79dea9b2c6ac7a. This impacts the function SplitTokensShuntingYard of the file enginequeryexprexpr.cpp of the component Filter Parser. Such manipulation leads to improper check for unusual conditions. The attack needs to be performed locally. The exploit has been disclosed to the public and may be used.

5 Aug 2026, 00:30 UTC4 viewsread 8 August 2026

‼️ CVE-2026-18103 ‼️ A flaw was found in dhcpserver. A remote attacker with network access to the OMAPI Open Management Application Programming Interface port, especially if not secured with TSIG Transaction Signature key authentication, could send a specially crafted lease creation request. This request, containing an overly long InfiniBand MAC address, triggers a buffer overflow in the printhwaddr function. Succes

4 Aug 2026, 23:30 UTC4 viewsread 8 August 2026

‼️ CVE-2026-45537 ‼️ OpenSIPS is a Session Initiation Protocol SIP server implementation. In versions prior to 3.6.6 and 4.0.0rc1, the constructuri function concatenates multiple URI components protocol, username, domain, port, params into a fixed 1024byte global BSS buffer without any bounds checking. When a routing script calls constructuri with an attackercontrolled username, a combined component length exceeding

4 Aug 2026, 23:30 UTC4 viewsread 8 August 2026

‼️ CVE-2026-18819 ‼️ A security vulnerability has been detected in RackTables up to 0.22.0e5fff9f8aab339798ed47e8c6d7d977ed97a82bd. This vulnerability affects unknown code. The manipulation leads to crosssite request forgery. The attack is possible to be carried out remotely. The exploit has been disclosed publicly and may be used. The project maintainer confirms "It seems plausible, in that RackTables does not at t

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

“🛡 Cybersecurity & Privacy 🛡 - CVEs” (@cibsecurity_CVEs), 459 subscribers as measured 30 August 2026. Telegram Register, tgregister.com/channel/cibsecurity_CVEs.

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.