Channel
@BugAlerts
On this record: Growth · Engagement · Posts · Citations · Cite this entry
476subscribers
+270 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1003665431511 |
|---|---|
| Type | Channel |
| Username | @BugAlerts |
| Created | Between 1 December 2025 and 31 May 2026— 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 | 6 |
| Confirmed unchanged | 1 time, most recently 30 August 2026 |
| On Telegram | t.me/BugAlerts |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 30 Aug 2026, 08:15 | 476 | +72 |
| 23 Aug 2026, 14:28 | 404 | +61 |
| 16 Aug 2026, 07:48 | 343 | +130 |
| 8 Aug 2026, 16:02 | 213 | +7 |
| 8 Aug 2026, 11:16 | 206 | no change |
| 7 Aug 2026, 19:33 | 206 | 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 pageof 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 | 54 |
| Reactions total | — |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 8 Aug 2026, 11:16 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.
🕷 mu6tx Bugs Alerts ━━━━━━━━━━━━━━━━━━━━━ 🚨 New Vulnerability! 🆔 CVE ID: CVE-2026-68082 📊 Severity: 🔵 LOW / UNKNOWN 📅 Published: 2026-08-08 10:16 UTC 📝 Description: In the Linux kernel, the following vulnerability has been resolved: libceph: fix two unsafe bare decodes in decode_lockers() decode_lockers() in cls_lock_client.c contains two bare decode operations that allow a malicious or compromised OSD to trigge…
🕷 mu6tx Bugs Alerts ━━━━━━━━━━━━━━━━━━━━━ 🚨 New Vulnerability! 🆔 CVE ID: CVE-2026-68081 📊 Severity: 🔵 LOW / UNKNOWN 📅 Published: 2026-08-08 10:16 UTC 📝 Description: In the Linux kernel, the following vulnerability has been resolved: KVM: nVMX: Put vmcs12 pages if nested VM-Enter fails due to invalid guest state Put all vmcs12 pages if KVM synthesizes a nested VM-Exit due to invalid guest while emulating VMLAUNCH…
🕷 mu6tx Bugs Alerts ━━━━━━━━━━━━━━━━━━━━━ 🚨 New Vulnerability! 🆔 CVE ID: CVE-2026-19270 📊 Severity: 🟡 MEDIUM 📈 CVSS Score: 5.3 📅 Published: 2026-08-08 08:16 UTC 📝 Description: A security flaw has been discovered in Hulupeep mcp-ui-probe up to 0.2.0. Affected is the function get_journey/delete_journey/analyze_journey/usage_stats of the file src/journey/JourneyStorage.ts of the component Journey/Usage. The manipulat…
🕷 mu6tx Bugs Alerts ━━━━━━━━━━━━━━━━━━━━━ 🚨 New Vulnerability! 🆔 CVE ID: CVE-2026-19268 📊 Severity: 🟡 MEDIUM 📈 CVSS Score: 6.3 📅 Published: 2026-08-08 08:16 UTC 📝 Description: A vulnerability was identified in abdullah1854 MCPGateway up to 549f494a9e363f40530149de324b8097de424230. This impacts the function getUsageByDateRange of the file src/services/claude-usage.ts of the component Claude Usage Range Endpoint. Th…
🕷 mu6tx Bugs Alerts ━━━━━━━━━━━━━━━━━━━━━ 🚨 New Vulnerability! 🆔 CVE ID: CVE-2026-19266 📊 Severity: 🟡 MEDIUM 📈 CVSS Score: 5.5 📅 Published: 2026-08-08 08:16 UTC 📝 Description: A vulnerability was determined in Kirachon context-engine up to 1.9.0. This affects the function execGitCommand of the file src/mcp/utils/gitUtils.ts of the component review-git-diff Endpoint. Executing a manipulation of the argument args ca…
🕷 mu6tx Bugs Alerts ━━━━━━━━━━━━━━━━━━━━━ 🚨 New Vulnerability! 🆔 CVE ID: CVE-2026-19263 📊 Severity: 🟠 HIGH 📈 CVSS Score: 7.3 📅 Published: 2026-08-08 07:17 UTC 📝 Description: A vulnerability was found in INQUIRELAB mcp-bridge-api up to b30a82aa1d1d1139e0de846c41c8aadee6e06114. The impacted element is an unknown function of the file mcp-bridge.js of the component Servers Endpoint. Performing a manipulation of the ar…
🕷 mu6tx Bugs Alerts ━━━━━━━━━━━━━━━━━━━━━ 🚨 New Vulnerability! 🆔 CVE ID: CVE-2026-19259 📊 Severity: 🟡 MEDIUM 📈 CVSS Score: 5.3 📅 Published: 2026-08-08 07:17 UTC 📝 Description: A vulnerability has been found in MZ Automation libiec61850 up to 1.6.1. The affected element is the function MmsMapping_varAccessSpecToObjectReference of the file src/iec61850/common/iec61850_common.c of the component MMS Protocol Workflow.…
🕷 mu6tx Bugs Alerts ━━━━━━━━━━━━━━━━━━━━━ 🚨 New Vulnerability! 🆔 CVE ID: CVE-2026-16955 📊 Severity: 🔵 LOW / UNKNOWN 📅 Published: 2026-08-08 07:17 UTC 📝 Description: The AI Engine WordPress plugin before 3.6.6 does not confine a caller-supplied file path before reading it and forwarding the contents to an external service, allowing users with a subscriber-level account to read arbitrary files from the server and e…
🕷 mu6tx Bugs Alerts ━━━━━━━━━━━━━━━━━━━━━ 🚨 New Vulnerability! 🆔 CVE ID: CVE-2026-16953 📊 Severity: 🔵 LOW / UNKNOWN 📅 Published: 2026-08-08 07:17 UTC 📝 Description: The AI Engine WordPress plugin before 3.6.4 does not verify ownership of a guest's uploaded chatbot files before deletion, authorising the action solely by a client-supplied session cookie value, so an unauthenticated attacker who obtains a victim's s…
🕷 mu6tx Bugs Alerts ━━━━━━━━━━━━━━━━━━━━━ 🚨 New Vulnerability! 🆔 CVE ID: CVE-2026-16948 📊 Severity: 🔵 LOW / UNKNOWN 📅 Published: 2026-08-08 07:17 UTC 📝 Description: The Solace Extra WordPress plugin before 1.6.1 does not perform capability checks in several of its AJAX actions and exposes the nonce that protects them on admin pages reachable by low-privileged users, allowing users with a role as low as Subscriber …
🕷 mu6tx Bugs Alerts ━━━━━━━━━━━━━━━━━━━━━ 🚨 New Vulnerability! 🆔 CVE ID: CVE-2026-16608 📊 Severity: 🔵 LOW / UNKNOWN 📅 Published: 2026-08-08 07:17 UTC 📝 Description: The Download Monitor WordPress plugin before 5.2.6 does not perform authorization checks on one of its download-logging AJAX actions, and exposes the nonce protecting it to unauthenticated visitors, allowing unauthenticated users to inject arbitrary do…
🕷 mu6tx Bugs Alerts ━━━━━━━━━━━━━━━━━━━━━ 🚨 New Vulnerability! 🆔 CVE ID: CVE-2026-16595 📊 Severity: 🔵 LOW / UNKNOWN 📅 Published: 2026-08-08 07:17 UTC 📝 Description: The WP Directory Kit WordPress plugin before 1.5.5 does not perform authorization or nonce checks on one of its authenticated AJAX actions, allowing any authenticated user such as a Subscriber to disclose the site's user list and unpublished listings b…
Showing the 12 most recent of 20 posts we hold for @BugAlerts. 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 — 559,097 of 1,627,445entries 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.
Republished by
Channels on the register that have forwarded this channel's posts into their own feed.
Built only from forwarded posts we have actually read, on both sides. Coverage is early and deliberately incomplete: a missing link means we have not read the post that would prove it, never that the relationship does not exist. Counts are distinct forwarded posts observed, so they only ever go up as we read more.
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.
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.
“Bugs Alerts” (@BugAlerts), 476 subscribers as measured 30 August 2026. Telegram Register, tgregister.com/channel/BugAlerts.
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.