🔴 CVE-2025-34468 · CRITICAL (9.8) Title: libcoap versions up to and including 4.3.5, prior to commit 30db3ea, contain a stack-based buffer ov TL;DR: libcoap versions up to and including 4.3.5, prior to commit 30db3ea, contain a stack-based buffer overflow in address resolution when attacker-controlled hostname data is copied into a fixed 256-byte stack buffer without proper bounds checking. A rem... 🔧 Fix: Advisor…

Channel
SOCHUB CVE - CHANNEL
@sochub_ar
On this record: Topic · Growth · Engagement · Posts · Cite this entry
347subscribers
+18 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 | -1001171474366 |
|---|---|
| Type | Channel |
| Username | @sochub_ar |
| Created | Between 1 March 2018 and 31 July 2021 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 8 August 2026 |
| Last confirmed live | 3 November 2026 |
| Measurements held | 13 |
| Confirmed unchanged | 1 time, most recently 3 November 2026 |
| On Telegram | t.me/sochub_ar |
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 22 September 2026 and assigned it the closest of 31 fixed categories, at 100% 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 the other topics.
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 3 Nov 2026, 14:29 | 347 | +2 |
| 28 Oct 2026, 09:19 | 345 | +7 |
| 20 Oct 2026, 08:30 | 338 | +3 |
| 14 Oct 2026, 09:19 | 335 | +2 |
| 6 Oct 2026, 17:16 | 333 | +5 |
| 26 Sept 2026, 08:17 | 328 | +2 |
| 13 Sept 2026, 14:21 | 326 | -2 |
| 6 Sept 2026, 08:21 | 328 | +1 |
| 30 Aug 2026, 00:24 | 327 | +2 |
| 22 Aug 2026, 21:43 | 325 | -2 |
| 16 Aug 2026, 06:36 | 327 | -2 |
| 8 Aug 2026, 07:18 | 329 | no change |
| 7 Aug 2026, 23:36 | 329 | first reading |
Engagement
20 posts held, back to 14 July 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 14 July 2026. An engagement rate over an empty window would be a number about nothing.
Recent posts
🔴 CVE-2025-34282 · CRITICAL (9.1) Title: ThingsBoard versions < 4.2.1 contain a server-side request forgery (SSRF) vulnerability in the dashb TL;DR: ThingsBoard versions < 4.2.1 contain a server-side request forgery (SSRF) vulnerability in the dashboard's Image Upload Gallery feature. An attacker can upload a malicious SVG file that references a remote URL. If the server processes the SVG file in... 🔧 Fix: Advisor…
🔴 CVE-2025-34267 · CRITICAL (9.9) Title: Flowise v3.0.1 < 3.0.8 and all versions after with 'ALLOW_BUILTIN_DEP' enabled contain an authentica TL;DR: Flowise v3.0.1 < 3.0.8 and all versions after with 'ALLOW_BUILTIN_DEP' enabled contain an authenticated remote code execution vulnerability and node VM sandbox escape due to insecure use of integrated modules (Puppeteer and Playwright) within the nod... 🔧 Fix: Advisor…
🔴 CVE-2025-34157 · CRITICAL (9.0) Title: Coolify versions prior to v4.0.0-beta.420.6 are vulnerable to a stored cross-site scripting (XSS) at TL;DR: Coolify versions prior to v4.0.0-beta.420.6 are vulnerable to a stored cross-site scripting (XSS) attack in the project creation workflow. An authenticated user with low privileges can create a project with a maliciously crafted name containing embed... 🔧 Fix: Advisor…
🔴 CVE-2024-11680 · CRITICAL (9.8) Title: ProjectSend versions prior to r1720 are affected by an improper authentication vulnerability. Remote TL;DR: ProjectSend versions prior to r1720 are affected by an improper authentication vulnerability. Remote, unauthenticated attackers can exploit this flaw by sending crafted HTTP requests to options.php, enabling unauthorized modification of the applicati... 🔥 CISA KEV | …
🔴 CVE-2024-23687 · CRITICAL (9.1) Title: Hard-coded credentials in FOLIO mod-data-export-spring versions before 1.5.4 and from 2.0.0 to 2.0.2 TL;DR: Hard-coded credentials in FOLIO mod-data-export-spring versions before 1.5.4 and from 2.0.0 to 2.0.2 allows unauthenticated users to access critical APIs, modify user data, modify configurations including single-sign-on, and manipulate fees/fines. 🔧 Fix: Advisory avai…
🔴 CVE-2024-23679 · CRITICAL (9.8) Title: Enonic XP versions less than 7.7.4 are vulnerable to a session fixation issue. An remote and unauthe TL;DR: Enonic XP versions less than 7.7.4 are vulnerable to a session fixation issue. An remote and unauthenticated attacker can use prior sessions due to the lack of invalidating session attributes. 🔧 Fix: Advisory available 🔗 View on VulnDB · NVD
🔴 CVE-2024-22051 · CRITICAL (9.8) Title: CommonMarker versions prior to 0.23.4 are at risk of an integer overflow vulnerability. This vulnera TL;DR: CommonMarker versions prior to 0.23.4 are at risk of an integer overflow vulnerability. This vulnerability can result in possibly unauthenticated remote attackers to cause heap memory corruption, potentially leading to an information leak or remote c... 🔧 Fix: Advisor…
🔴 CVE-2025-3248 · CRITICAL (9.8) Title: Langflow versions prior to 1.3.0 are susceptible to code injection in the /api/v1/validate/code end TL;DR: Langflow versions prior to 1.3.0 are susceptible to code injection in the /api/v1/validate/code endpoint. A remote and unauthenticated attacker can send crafted HTTP requests to execute arbitrary code. 🔥 CISA KEV | 💣 Exploitable | ⭐ Notable 🔧 Fix: Advisory available…
🔴 CVE-2026-48334 · CRITICAL (9.3) Title: Illustrator is affected by an Improper Input Validation vulnerability that could result in arbitrary TL;DR: Illustrator is affected by an Improper Input Validation vulnerability that could result in arbitrary code execution in the context of the current user. Exploitation of this issue requires user interaction in that a victim must open a malicious file. ... 🔧 Fix: Advisor…
🔴 CVE-2026-45363 · CRITICAL (9.1) Title: ruby-jwt is a Ruby implementation of the RFC 7519 OAuth JSON Web Token standard. Prior to 2.10.3 and TL;DR: ruby-jwt is a Ruby implementation of the RFC 7519 OAuth JSON Web Token standard. Prior to 2.10.3 and 3.2.0, JWT.decode(token, '', true, algorithm: 'HS256') accepts an attacker-forged token because OpenSSL::HMAC.digest('SHA256', '', payload) returns a... 🔧 Fix: No fix …
🔴 CVE-2026-53486 · CRITICAL (9.1) Title: The decompress package for Node.js extracts archives. Prior to 10.2.1 and 11.1.3, archive extraction TL;DR: The decompress package for Node.js extracts archives. Prior to 10.2.1 and 11.1.3, archive extraction can create files and links outside the target directory. When extracting an archive to a directory, a crafted archive can read or write files outside... 🔧 Fix: No fix …
Showing the 12 most recent of 20 posts we hold for @sochub_ar. 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 3 November 2026 — this entry's latest reading, not the date you are reading this.
“SOCHUB CVE - CHANNEL” (@sochub_ar), 347 subscribers as measured 3 November 2026. Telegram Register, tgregister.com/channel/sochub_ar.
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.