Channel
@daily_cve
On this record: Topic · Growth · Engagement · Posts · Cite this entry
204subscribers
+14 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1001397370362 |
|---|---|
| Type | Channel |
| Username | @daily_cve |
| Created | Between 1 August 2018 and 31 July 2021 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 3 October 2026 |
| Measurements held | 8 |
| Confirmed unchanged | 1 time, most recently 3 October 2026 |
| On Telegram | t.me/daily_cve |
Hacking & security — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-FP8, prompt version 1) read this channel’s own recent posts on 24 September 2026 and assigned it the closest of 31 fixed categories, at 98% confidence. This is a model’s judgement about what the channel is likely to be about, not a fact this register measured the way a subscriber count or a view count is measured — it can be revised on a later pass, and it carries no weight anywhere else on this page. How this classification works, and why it has no browse page of its own yet.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 3 Oct 2026, 11:56 | 204 | +5 |
| 11 Sept 2026, 09:58 | 199 | +2 |
| 2 Sept 2026, 00:34 | 197 | +2 |
| 27 Aug 2026, 00:03 | 195 | -1 |
| 20 Aug 2026, 12:52 | 196 | +5 |
| 13 Aug 2026, 06:18 | 191 | +1 |
| 7 Aug 2026, 07:15 | 190 | no change |
| 6 Aug 2026, 22:02 | 190 | first reading |
20 posts held, back to 7 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.
Nothing published in the last 30 days. ERR and ER are rolling 30-day measures, so there is nothing to compute — we hold 20 posts for this entry, the most recent from 7 August 2026. An engagement rate over an empty window would be a number about nothing.
🔴 #Oracle E-Business Suite HCM Configuration Workbench – Privilege Escalation via Rapid Implementation Component (#CVE-2026-60900) – High -DC-Aug2026-1418 🔗 https://dailycve.com/oracle-e-business-suite-hcm-configuration-workbench-privilege-escalation-via-rapid-implementation-component-cve-2026-60900-high-dc-aug2026-1418/ @Daily_CVE
🔴 #Oracle E-Business Suite, Improper Access Control, #CVE-2026-61327 (High) -DC-Aug2026-1419 🔗 https://dailycve.com/oracle-e-business-suite-improper-access-control-cve-2026-61327-high-dc-aug2026-1419/ @Daily_CVE
🔴 #Oracle Bills of Material Remote Privilege Escalation #CVE-2026-47031 (High) -DC-Aug2026-1420 🔗 https://dailycve.com/oracle-bills-of-material-remote-privilege-escalation-cve-2026-47031-high-dc-aug2026-1420/ @Daily_CVE
🔴 Traefik #Kubernetes Gateway API Provider Namespace Confusion Vulnerability #CVE-2026-65601 (Critical) -DC-Aug2026-1421 🔗 https://dailycve.com/traefik-kubernetes-gateway-api-provider-namespace-confusion-vulnerability-cve-2026-65601-critical-dc-aug2026-1421/ @Daily_CVE
🟠 #Oracle Product Workbench, Authorization Bypass, #CVE-2026-61269 (Medium) -DC-Aug2026-1422 🔗 https://dailycve.com/oracle-product-workbench-authorization-bypass-cve-2026-61269-medium-dc-aug2026-1422/ @Daily_CVE
🟠 #Oracle Advanced Benefits, Privilege Escalation via Self Service Benefits, #CVE-2026-62542 (Medium) -DC-Aug2026-1423 🔗 https://dailycve.com/oracle-advanced-benefits-privilege-escalation-via-self-service-benefits-cve-2026-62542-medium-dc-aug2026-1423/ @Daily_CVE
🟠 Mattermost Mobile Apps, SSO Authentication Bypass, #CVE‑2026‑22880 (MEDIUM) -DC-Aug2026-1424 🔗 https://dailycve.com/mattermost-mobile-apps-sso-authentication-bypass-cve-2026-22880-medium-dc-aug2026-1424/ @Daily_CVE
🔴 MessagePack (#Python), Out-of-bounds Read/Use-After-Free, #CVE-2026-57585 (High) -DC-Aug2026-1425 🔗 https://dailycve.com/messagepack-python-out-of-bounds-read-use-after-free-cve-2026-57585-high-dc-aug2026-1425/ @Daily_CVE
🟠 #Oracle E-Business Suite, Improper Authorization Vulnerability, #CVE-2026-62474 (MEDIUM) -DC-Aug2026-1426 🔗 https://dailycve.com/oracle-e-business-suite-improper-authorization-vulnerability-cve-2026-62474-medium-dc-aug2026-1426/ @Daily_CVE
🔴 Traefik, Cross-User Response Poisoning, #CVE-2026-71324 (Critical) -DC-Aug2026-1427 🔗 https://dailycve.com/traefik-cross-user-response-poisoning-cve-2026-71324-critical-dc-aug2026-1427/ @Daily_CVE
🔴 Traefik Authentication Bypass via Path Traversal in ReplacePathRegex Middleware, #CVE-2026-65600 (High) -DC-Aug2026-1428 🔗 https://dailycve.com/traefik-authentication-bypass-via-path-traversal-in-replacepathregex-middleware-cve-2026-65600-high-dc-aug2026-1428/ @Daily_CVE
🔴 Traefik #Kubernetes Gateway API Provider, Route Identity Collision, #CVE-2026-71327 (High) -DC-Aug2026-1429 🔗 https://dailycve.com/traefik-kubernetes-gateway-api-provider-route-identity-collision-cve-2026-71327-high-dc-aug2026-1429/ @Daily_CVE
Showing the 12 most recent of 20 posts we hold for @daily_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.
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 3 October 2026 — this entry's latest reading, not the date you are reading this.
“DailyCVE” (@daily_cve), 204 subscribers as measured 3 October 2026. Telegram Register, tgregister.com/channel/daily_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.