Telegram RegisterThe public register of Telegram
Telegram profile photo for Vulnerability

Channel

Vulnerability

@newvulnerability

On this record: Topic · Growth · Engagement · Posts · Telegram's recommendations · Cite this entry

614subscribers

-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-1001258761276
TypeChannel
Username@newvulnerability
CreatedBetween 1 March 2018 and 31 August 2021 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live13 September 2026
Measurements held5
Confirmed unchanged1 time, most recently 13 September 2026
On Telegramt.me/newvulnerability

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

6146226187 August 2026 — 622 subscribers7 August 2026 — 622 subscribers20 August 2026 — 617 subscribers5 September 2026 — 618 subscribers13 September 2026 — 614 subscribers7 August 202613 September 2026
5 measurements spanning 37 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 613–623 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
13 Sept 2026, 16:38614-4
5 Sept 2026, 04:57618+1
20 Aug 2026, 22:13617-5
7 Aug 2026, 06:32622no change
7 Aug 2026, 06:27622first reading

Engagement

20 posts held, back to 16 September 2025the 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 27 January 2026. An engagement rate over an empty window would be a number about nothing.

Recent posts

27 Jan 2026, 22:35 UTC305 viewsread 7 August 2026

Administrative FortiCloud SSO authentication bypass PSIRT | FortiGuard Labs https://share.google/4I25IKEgkZhijHlYE @newvulnerability

27 Jan 2026, 09:49 UTC306 viewsread 7 August 2026
Photo

🛑 URGENT: Microsoft rushed out out-of-band fixes for an actively exploited Office zero-day. CVE-2026-21509 (CVSS 7.8) lets attackers bypass Office security using a malicious file that must be opened by the victim. 🔗 Details → https://thehackernews.com/2026/01/microsoft-issues-emergency-patch-for.html @newvulnerability

22 Oct 2025, 23:00 UTC382 viewsread 7 August 2026

Security Update – Wazuh Server Vulnerability: Remote Code Execution CVE: CVE-2025-24016 Severity: 9.9 (Critical) Summary: Wazuh Server versions 4.4.0 through 4.9.0 are vulnerable to remote code execution. The flaw allows an authenticated attacker with limited privileges to execute arbitrary code with elevated permissions, potentially leading to full compromise of the affected system. The issue arises due to improper

22 Oct 2025, 22:59 UTC213 viewsread 7 August 2026

Security Update – Apache Tomcat Vulnerability: Remote Code Execution / Information Disclosure / Data Corruption via partial PUT CVE: CVE-2025-24813 Severity: 10.0 (Critical) Summary: Apache Tomcat versions listed (see Affected Products) are impacted by a critical vulnerability in the HTTP PUT handling that can be abused to perform partial PUT requests leading to remote code execution, information disclosure, or corru

17 Oct 2025, 01:18 UTC222 views0 reactionsread 7 August 2026

Security Update – Apache ActiveMQ NMS AMQP Client Vulnerability: Remote Code Execution – Deserialization of Untrusted Data CVE: CVE-2025-54539 Severity: 9.8 (Critical) Summary: Apache ActiveMQ NMS AMQP Client versions up to and including 2.3.0 are affected by a critical deserialization vulnerability. The flaw allows an unauthenticated remote attacker to send specially crafted AMQP messages that trigger deserializatio

16 Oct 2025, 22:52 UTC167 viewsread 7 August 2026

Security Update – Adobe Experience Manager Vulnerability: Remote Code Execution – Misconfiguration allowing arbitrary code execution CVE: CVE-2025-54253 Severity: 10.0 (Critical) Summary: Adobe Experience Manager (AEM) up to and including version 6.5.23 contains a misconfiguration that allows an unauthenticated, remote attacker to bypass security mechanisms and execute arbitrary code on affected servers. Exploitation

16 Oct 2025, 06:16 UTC147 viewsread 7 August 2026

F5 just confirmed a nation-state breach that went undetected for months. Hackers stole BIG-IP source code and data on undisclosed vulnerabilities. Full story ↓ https://thehackernews.com/2025/10/f5-breach-exposes-big-ip-source-code.html @newvulnerability

16 Oct 2025, 01:08 UTC600 viewsread 7 August 2026

Security Update – Cisco IOS XE Software Secure Boot Bypass Vulnerabilities Vulnerabilities: Multiple High-Severity Secure Boot Bypass Vulnerabilities in Cisco IOS XE Software CVEs: CVE-2025-20313 – Secure Boot Chain of Trust Bypass CVE-2025-20314 – Secure Boot Chain of Trust Bypass Severity: High (CVSS 6.7) Summary: Cisco has disclosed multiple vulnerabilities in Cisco IOS XE Software that could allow an authenticate

16 Oct 2025, 01:07 UTC512 viewsread 7 August 2026

Security Update – Cisco Desk Phone, IP Phone, and Video Phone SIP Software Vulnerabilities: Multiple High-Severity Vulnerabilities in Cisco Desk Phone 9800 Series, IP Phone 7800 and 8800 Series, and Video Phone 8875 with SIP Software CVEs: CVE-2025-20350 – Web UI Denial of Service (DoS) CVE-2025-20351 – Web UI Cross-Site Scripting (XSS) Severity: High (CVSS up to 7.5) Summary: Cisco has disclosed multiple high-severi

16 Oct 2025, 01:00 UTC90 viewsread 7 August 2026

https://www.cisa.gov/news-events/directives/ed-26-01-mitigate-vulnerabilities-f5-devices @newvulnerability

16 Oct 2025, 00:46 UTC117 viewsread 7 August 2026

Security Update – F5 BIG-IP, BIG-IP Next, F5OS, and Silverline Vulnerabilities: Multiple Critical Vulnerabilities and Active Security Incident Advisory Reference: F5 Security Incident and October 2025 Quarterly Security Notification Severity: Critical / High Summary: F5 has disclosed a cybersecurity incident impacting certain internal F5 systems, along with its October 2025 quarterly security notification detailing m

15 Oct 2025, 03:54 UTC137 viewsread 7 August 2026

Security Update – Microsoft October 2025 Patch Tuesday Vulnerabilities: Multiple Critical and Zero-Day Vulnerabilities Across Microsoft Products CVEs: CVE-2025-0033 – AMD Restricted Memory Page Corruption (Zero-Day / Critical) CVE-2025-24052 – Agere Modem Driver Elevation of Privilege (Zero-Day) CVE-2025-24990 – Agere Modem Driver Elevation of Privilege (Zero-Day) CVE-2025-2884 – TPM 2.0 Out-of-Bounds Read (Zero-Day)

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

Appears in Telegram’s recommendations for other channels

The reverse of the list above, and a different kind of signal. This does not require this channel to have ever been asked about directly — each row below is a channel we DID ask Telegram about, whose Telegram-generated list happened to include this one. A channel can appear here with an empty list above it, because being named by someone else’s query is independent of having been queried itself.

زبان آلمانی از A1 تا A2
@DeutschA1bisA2 · 32,664
Telegram ranks this channel #60 of 80 here — alongside 79 others — read 5 September 2026
AlmaniBeFarsi
@almanibefarsicom · 23,771
Telegram ranks this channel #74 of 76 here — alongside 75 others — read 17 September 2026
بانک کتاب صوتی
@soutidastan · 95,045
Telegram ranks this channel #75 of 80 here — alongside 79 others — read 16 August 2026
جبهه جهانی شباب المقاومة
@sh_almoqawamma · 24,395
Telegram ranks this channel #81 of 87 here — alongside 86 others — read 15 September 2026

This channel appears in 4 seed channels' Telegram-generated recommendation lists in total. Each is Telegram’s list for THAT channel, not this one — see how this is measured.

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

“Vulnerability” (@newvulnerability), 614 subscribers as measured 13 September 2026. Telegram Register, tgregister.com/channel/newvulnerability.

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.