Telegram RegisterThe public register of Telegram
Telegram profile photo for Dark Web Informer - CVE Alerts

Channel

Dark Web Informer - CVE Alerts

@DWI_CVE_Alerts

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

473subscribers

+130 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-1004337964619
TypeChannel
Username@DWI_CVE_Alerts
CreatedBetween 1 June 2026 and 8 August 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded8 August 2026
Last confirmed live17 September 2026
Measurements held8
Confirmed unchanged1 time, most recently 17 September 2026
On Telegramt.me/DWI_CVE_Alerts

Topic

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 21 September 2026 and assigned it the closest of 31 fixed categories, at 95% 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.

Growth

3414734077 August 2026 — 343 subscribers8 August 2026 — 343 subscribers8 August 2026 — 341 subscribers16 August 2026 — 354 subscribers23 August 2026 — 378 subscribers30 August 2026 — 413 subscribers10 September 2026 — 450 subscribers17 September 2026 — 473 subscribers7 August 202617 September 2026
8 measurements spanning 41 days, net +130. 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 321–493 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
17 Sept 2026, 15:37473+23
10 Sept 2026, 04:21450+37
30 Aug 2026, 21:25413+35
23 Aug 2026, 00:46378+24
16 Aug 2026, 02:27354+13
8 Aug 2026, 13:38341-2
8 Aug 2026, 07:01343no change
7 Aug 2026, 19:02343first reading

Engagement

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.

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 8 August 2026. An engagement rate over an empty window would be a number about nothing.

Recent posts

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

CVE Alert | DarkWebInformer.com Affected: Google - Chrome Severity: High (CVSS 8.3, v3.1) CVE ID: CVE-2026-19141 Description Use after free in Resources in Google Chrome on Android prior to 151.0.7922.109 allowed a remote attacker who had compromised the renderer process to potentially perform a sandbox escape via a crafted HTML page. (Chromium security severity: High) Vector CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:C/C:H/I…

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

CVE Alert | DarkWebInformer.com Affected: Google - Chrome Severity: High (CVSS 8.6, v3.1) CVE ID: CVE-2026-19143 Description Insufficient validation of untrusted input in WebAPKs in Google Chrome on Android prior to 151.0.7922.109 allowed a local attacker to potentially perform a sandbox escape via a malicious file. (Chromium security severity: High) Vector CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:H Published: …

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

CVE Alert | DarkWebInformer.com Affected: Google - Chrome Severity: High (CVSS 8.3, v3.1) CVE ID: CVE-2026-19152 Description Insufficient policy enforcement in Navigation in Google Chrome prior to 151.0.7922.109 allowed a remote attacker who had compromised the renderer process to potentially perform a sandbox escape via a crafted HTML page. (Chromium security severity: High) Vector CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:…

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

CVE Alert | DarkWebInformer.com Affected: Google - Chrome Severity: High (CVSS 8.3, v3.1) CVE ID: CVE-2026-19148 Description Out of bounds write in GPU in Google Chrome on Linux prior to 151.0.7922.109 allowed a remote attacker who had compromised the renderer process to potentially perform a sandbox escape via a crafted HTML page. (Chromium security severity: High) Vector CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:C/C:H/I:H/…

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

CVE Alert | DarkWebInformer.com Affected: Autodesk - Revit Severity: High (CVSS 7.8, v3.1) CVE ID: CVE-2026-8325 Description A maliciously crafted PDF file, when parsed through Autodesk Revit, can force an Out-of-Bounds Write vulnerability. A malicious actor may leverage this vulnerability to cause a crash, cause data corruption, or execute arbitrary code in the context of the current process. Vector CVSS:3.1/AV:L…

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

CVE Alert | DarkWebInformer.com Affected: Autodesk - Revit Severity: High (CVSS 7.8, v3.1) CVE ID: CVE-2026-1289 Description A maliciously crafted PDF file, when parsed through Autodesk Revit, can force a Use-After-Free vulnerability. A malicious actor can leverage this vulnerability to cause a crash, disclose sensitive data, or execute arbitrary code in the context of the current process. Vector CVSS:3.1/AV:L/AC:…

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

CVE Alert | DarkWebInformer.com Affected: Google - Chrome Severity: High (CVSS 8.8, v3.1) CVE ID: CVE-2026-19144 Description Use after free in HTML in Google Chrome prior to 151.0.7922.109 allowed a remote attacker to potentially exploit heap corruption via a crafted HTML page. (Chromium security severity: High) Vector CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H Published: 06 Aug 2026, 20:33 UTC Modified: 08 Aug…

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

CVE Alert | DarkWebInformer.com Affected: Google - Chrome Severity: High (CVSS 8.3, v3.1) CVE ID: CVE-2026-19147 Description Use after free in Aura in Google Chrome on Linux prior to 151.0.7922.109 allowed a remote attacker who had compromised the renderer process to potentially perform a sandbox escape via a crafted HTML page. (Chromium security severity: High) Vector CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:C/C:H/I:H/A:H …

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

CVE Alert | DarkWebInformer.com Affected: Sonatype - Nexus Repository Severity: High (CVSS 7.2, v4.0) CVE ID: CVE-2026-17593 Description An account holding the nexus:settings:update permission in Nexus Repository 3 (or the equivalent nexus:settings permission in the legacy Nexus Repository 2) could submit arbitrary values as realm identifiers through an internal configuration API that did not validate them against …

8 Aug 2026, 05:38 UTC5 viewsread 8 August 2026

CVE Alert | DarkWebInformer.com Affected: shapedplugin - Easy Accordion – AI-Powered FAQ & Accordion Blocks, Product FAQ Severity: Medium (CVSS 6.4, v3.1) CVE ID: CVE-2026-18988 Description The Easy Accordion plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'accordionTitleTag' block attribute in versions up to, and including, 3.1.8. This is due to insufficient input sanitization and output …

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

CVE Alert | DarkWebInformer.com Affected: Sonatype - Nexus Repository 3 Severity: Medium (CVSS 5.3, v4.0) CVE ID: CVE-2026-17595 Description Nexus Repository 3 did not fully sandbox JEXL expressions used in Content Selectors. An account holding the nexus:selectors:create permission could construct an expression that read Java object properties not intended to be exposed to the expression engine, disclosing internal…

8 Aug 2026, 04:38 UTC4 viewsread 8 August 2026

CVE Alert | DarkWebInformer.com Affected: brix - crypto-js Severity: Critical (CVSS 9, v3.1) CVE ID: CVE-2026-71851 Description crypto-js is a JavaScript library of crypto standards. Versions of crypto-js prior to 4.0.0 generate randomness in CryptoJS.lib.WordArray.random() using a custom variation of the Multiply-With-Carry pseudorandom number generator, seeded from Math.random(), instead of a cryptographically se…

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

Mentions

Named by 2 registered channels — 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.

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 17 September 2026 — this entry's latest reading, not the date you are reading this.

“Dark Web Informer - CVE Alerts” (@DWI_CVE_Alerts), 473 subscribers as measured 17 September 2026. Telegram Register, tgregister.com/channel/DWI_CVE_Alerts.

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.