Telegram RegisterThe public register of Telegram
Telegram profile photo for БДУ ФСТЭК России

Channel

БДУ ФСТЭК России

@bdufstecru

On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Telegram's recommendations · Cite this entry

10,554subscribers

+5 since we began measuring on 6 August 2026

Risers and fallers across the register · movement among entries of 10,000–31,623.

Register entry

Telegram ID-1001623043171
TypeChannel
Username@bdufstecru
DescriptionНовости БДУ ФСТЭК России bdu.fstec.ru Наш канал БДУ ФСТЭК России теперь в Отечественном многофункциональном сервисе обмена информацией: https://max.ru/id3666088317_gos
Created7 March 2022measured — cross-checked against a third-party dataset (ext.tg_channel)
First recorded6 August 2026
Last confirmed live19 August 2026
Measurements held12
Confirmed unchanged1 time, most recently 19 August 2026
On Telegramt.me/bdufstecru

Growth

10,54510,55510,5506 August 2026 — 10,549 subscribers6 August 2026 — 10,549 subscribers7 August 2026 — 10,546 subscribers8 August 2026 — 10,547 subscribers10 August 2026 — 10,545 subscribers11 August 2026 — 10,551 subscribers12 August 2026 — 10,550 subscribers13 August 2026 — 10,555 subscribers16 August 2026 — 10,552 subscribers17 August 2026 — 10,550 subscribers18 August 2026 — 10,553 subscribers19 August 2026 — 10,554 subscribers10,5546 August 202619 August 2026
12 measurements spanning 13 days, net +5. 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 10,544–10,557 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
19 Aug 2026, 19:2610,554+1
18 Aug 2026, 18:0310,553+3
17 Aug 2026, 20:1510,550-2
16 Aug 2026, 16:0610,552-3
13 Aug 2026, 13:3710,555+5
12 Aug 2026, 11:4310,550-1
11 Aug 2026, 13:5510,551+6
10 Aug 2026, 13:4110,545-2
8 Aug 2026, 11:5210,547+1
7 Aug 2026, 09:5010,546-3
6 Aug 2026, 10:1510,549no change
6 Aug 2026, 09:5610,549first reading

Engagement

51 posts held, back to 27 July 2026the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 22 pagesof Telegram’s post history, 20 posts per page.

ERR · 30 days
14.1%
avg views ÷ 10,554 subscribers
Avg views / post
1,480
51 posts measured
Reaction rate
0.172%
reactions ÷ views · ER floor
Posts in window
51
of 51 held

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.

What these figures were computed from
WindowRolling 30 days · latest post in window 19 August 2026
Posts held51 (27 July 202619 August 2026)
Views total75,724
Reactions total130
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken20 Aug 2026, 01:32 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.

What this channel posts

Links
3,330

Lifetime counters from Telegram’s own channel header, read 20 August 2026 — not the date at the top of this page, which is when the subscriber count was last read. A count marked was rounded by Telegram before we ever saw it — t.me prints these counters in full below 1,000 and to three significant figures above, so ≈142,000 means somewhere between 141,500 and 142,499.

Reaction mix

130 reactions across 51 posts, in 5 distinct kinds. The most used accounts for 90.0% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
👍11790.0%
🔥64.62%
43.08%
😈21.54%
😢10.769%

No sentiment is inferred, and none should be read in. This table is ordered by count and by nothing else. Emoji do not carry stable meaning across languages or communities — 🙏 is thanks in one channel and mourning in another — so we publish which ones were pressed and how often, and pass no judgement on what an audience meant by them.

Precision. Telegram publishes reaction counts per emoji and short-forms each one — 4.34K, 1.2M — so any single kind at or above 1,000 reaches us at three significant figures, and only counts below 1,000 are exact. The shares above are ratios of those figures and carry the same error. This is also why the total here can differ slightly from a reaction total printed elsewhere on the page: both are sums of the same rounded parts, taken over samples with different edges.

Coverage. Reactions were read on 51 of the 51 sampled posts in this sample. Summed by Telegram’s own count on each post — not by adding up the per-emoji breakdown above — those same posts carry 130reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 51 most recent posts we hold, published 27 July 2026 to 19 August 2026, using the newest reading held for each. Telegram Stars are excluded: they are a payment, not a reaction, and they have their own section.

Recent posts

19 Aug 2026, 14:27 UTC734 views2 reactionsread 20 August 2026

Уязвимость функции to_char(timestamptz) системы управления базами данных PostgreSQL связана с переполнением буфера в динамической памяти. Эксплуатация уязвимости может позволить нарушителю, действующему удаленно, выполнить произвольный код BDU:2026-11894 CVE-2026-14669 Использование рекомендаций производителя: https://www.postgresql.org/support/security/CVE-2026-14669 Компенсирующие меры: - ограничение прав на вып

👍2

19 Aug 2026, 14:26 UTC707 views2 reactionsread 20 August 2026

Уязвимость программного обеспечения управления ИТ-инфраструктурой Microsoft Configuration Manager связана с ошибками разграничения доступа. Эксплуатация уязвимости может позволить нарушителю повысить свои привилегии BDU:2026-11890 CVE-2026-47301 Использование рекомендаций производителя: https://msrc.microsoft.com/update-guide/vulnerability/CVE-2026-47301

👍2

19 Aug 2026, 14:25 UTC645 views2 reactionsread 20 August 2026

Уязвимость ядра операционных систем Windows связана с ненадежным разыменованием указателя. Эксплуатация уязвимости может позволить нарушителю повысить свои привилегии и вызвать отказ в обслуживании BDU:2026-11889 CVE-2026-62737 Использование рекомендаций производителя: https://msrc.microsoft.com/update-guide/vulnerability/CVE-2026-62737

👍2

19 Aug 2026, 14:25 UTC653 views2 reactionsread 20 August 2026

Уязвимость компонента RewriteValve сервера приложений Apache Tomcat связана с неправильной обработкой данных с кодированием URL. Эксплуатация уязвимости может позволить нарушителю, действующему удаленно, обойти существующие механизмы безопасности BDU:2026-11888 CVE-2026-59083 Использование рекомендаций производителя: https://lists.apache.org/thread/3g63zos2gkjo5vgnrk8kxmosv47w6wbq

👍2

19 Aug 2026, 14:23 UTC643 views2 reactionsread 20 August 2026

Уязвимость механизма check_unsafe_options библиотеки Python для взаимодействия с git-репозиториями GitPython связана с непринятием мер по нейтрализации специальных элементов. Эксплуатация уязвимости может позволить нарушителю, действующему удалённо, перезаписывать произвольные файлы в системе BDU:2026-11883 CVE-2026-73625 Использование рекомендаций производителя: https://github.com/gitpython-developers/GitPython/se

👍2

19 Aug 2026, 14:19 UTC796 views2 reactionsread 20 August 2026

Уязвимость программной платформы на базе git для совместной работы над кодом GitLab EE/ CE связана с неверным управлением генерацией кода. Эксплуатация уязвимости может позволить нарушителю, действующему удаленно, получить несанкционированный доступ к защищаемой информации и выполнить произвольный код BDU:2026-11879 CVE-2026-19478 Использование рекомендаций производителя: https://docs.gitlab.com/releases/patches/pa

👍2

19 Aug 2026, 14:17 UTC746 views2 reactionsread 20 August 2026

Обновление БДУ Обновлены сведения об уязвимостях программного обеспечения Добавлена информация о 65 уязвимостях программного обеспечения Внесены изменения в 395 записей об уязвимостях программного обеспечения 🔶БДУ ФСТЭК России в MAX

👍2

17 Aug 2026, 14:22 UTC≈1,240 views2 reactionsread 20 August 2026

Уязвимость функций IndexFile.checkout() и TagReference.create() библиотеки Python для взаимодействия с git-репозиториями GitPython связана с неверным ограничением имени пути к каталогу при обработке параметра kwargs. Эксплуатация уязвимости может позволить нарушителю, действующему удаленно, получить несанкционированный доступ к защищаемой информации BDU:2026-11719 CVE-2026-73620 Использование рекомендаций производи

👍2

17 Aug 2026, 14:20 UTC≈1,270 views2 reactionsread 20 August 2026

Уязвимость сервера Syslog Server средства управления виртуальной инфраструктурой VMware vCenter Server связана с неверным ограничением имени пути к каталогу. Эксплуатация уязвимости может позволить нарушителю, действующему удаленно, выполнить произвольный код BDU:2026-11333 CVE-2026-59310 Использование рекомендаций производителя: https://support.broadcom.com/web/ecx/support-content-notification/-/external/content/S

👍2

17 Aug 2026, 14:19 UTC≈1,180 views2 reactionsread 20 August 2026

Обновление БДУ Обновлены сведения об уязвимостях программного обеспечения Добавлена информация о 210 уязвимостях программного обеспечения Внесены изменения в 211 записей об уязвимостях программного обеспечения 🔶БДУ ФСТЭК России в MAX

👍2

14 Aug 2026, 13:17 UTC≈1,760 views4 reactionsread 20 August 2026

Уязвимость функции formDataToJSON() файла lib/helpers/formDataToJSON.js библиотеки axios связана с неконтролируемым расходом ресурсов. Эксплуатация уязвимости может позволить нарушителю, действующему удаленно, вызвать отказ в обслуживании BDU:2026-11552 CVE-2026-67313 Использование рекомендаций производителя: https://github.com/axios/axios/security/advisories/GHSA-42h9-826w-cgv3

👍4

14 Aug 2026, 13:16 UTC≈1,630 views4 reactionsread 20 August 2026

Уязвимость веб-консоли системы защиты от вредоносных программ PT MultiScanner, сетевой песочницы PT Sandbox, систем многоуровневой защиты корпоративной электронной почты PT Email Security и PT Email Gateway связана с непринятием мер по защите структуры веб-страницы. Эксплуатация уязвимости может позволить нарушителю, действующему удалённо, выполнить произвольный код BDU:2026-11526 PT-2026-23 Использование рекоменда

👍4

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

Citation-graph rank — 624,535 of 1,566,395entries 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.

Forward network

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.

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.

Утечки информации
@dataleak · 120,426
Telegram ranks this channel #43 of 83 here — alongside 82 others — read 14 August 2026
SecurityLab.ru
@SecLabNews · 83,618
Telegram ranks this channel #65 of 90 here — alongside 89 others — read 18 August 2026
Вестник Киберполиции России
@cyberpolice_rus · 84,248
Telegram ranks this channel #78 of 92 here — alongside 91 others — read 18 August 2026

This channel appears in 3 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 19 August 2026 — this entry's latest reading, not the date you are reading this.

“БДУ ФСТЭК России” (@bdufstecru), 10,554 subscribers as measured 19 August 2026. Telegram Register, tgregister.com/channel/bdufstecru.

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.