Channel
@vulns
On this record: Growth · Engagement · Posts · Citations · Cite this entry
2,132subscribers
-1 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
| Telegram ID | -1001118254887 |
|---|---|
| Type | Channel |
| Username | @vulns |
| Created | 25 May 2017 — measured — cross-checked against a third-party dataset (TGDataset) |
| First recorded | 6 August 2026 |
| Last confirmed live | 13 August 2026 |
| Measurements held | 4 |
| Confirmed unchanged | 1 time, most recently 13 August 2026 |
| On Telegram | t.me/vulns |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 13 Aug 2026, 00:26 | 2,132 | +1 |
| 10 Aug 2026, 08:20 | 2,131 | -2 |
| 6 Aug 2026, 06:16 | 2,133 | no change |
| 6 Aug 2026, 02:17 | 2,133 | first reading |
20 posts held, back to 28 March 2021 — the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 2 pagesof 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 13 February 2025. An engagement rate over an empty window would be a number about nothing.
Here’s my new blog post: “Redacted bugs #3: Hunting for bugs worth $7,750 in an adult content platform.” Happy reading! https://securityrise.com/posts/redacted-bugs-3 Радий поділитися з вами новою заміткою: “Redacted bugs #3: Полювання на баги вартістю $7,750 у додатку для дорослих” https://securityrise.com/ua/posts/redacted-bugs-3
Hey! I just published a new article: “Gift card security testing research” https://securityrise.com/posts/gift-card-security-research/ Привіт! Щойно опублікував невелику статтю: “Дослідження безпеки подарункових карток” https://securityrise.com/ua/posts/gift-card-security-research/
Here’s my new blog post, “Bugs showcase #1: Chaining a lack of values correlation, linear growth of attempts, and other omissions in OTP implementations to achieve 2 ATOs”.🪲 I hope it’ll be interesting for you!
Photo, posted without a caption
Uber Investigating Breach of Its Computer Systems https://www.nytimes.com/2022/09/15/technology/uber-hacking-breach.html
Если кто-то любит мониторить страницы с обновлениями определенных сервисов (новые фичи=новые баги), я создал список changelog'ов для сайтов/моб приложений с bug bounty https://github.com/w9w/bugbounty_changelogs
CVE-2021-40438 Apache SSRF POC:
Photo, posted without a caption
Photo, posted without a caption
Похоже что фикс для CVE-2021-41773 можно обойти с помощью дабл юрл-энкода и Apache выпустили ещё один (CVE-2021-42013)
CVE-2021-41773 (Apache server path traversal) POC: /cgi-bin/.%2e/%2e%2e/%2e%2e/%2e%2e/etc/passwd
И давненько у нас не было хорошей уязвимости в Window. В данном случае уязвимость в HTTP Protocol Stack Windows IIS может быть использована для атак на Windows 10 и Windows Server. Microsoft уже выпустила апдейт в рамках майского апдейта. https://msrc.microsoft.com/update-guide/vulnerability/CVE-2021-31166 А тут и PoC уже подвезли https://www.bleepingcomputer.com/news/security/exploit-released-for-wormable-windows…
Showing the 12 most recent of 20 posts we hold for @vulns. 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.
Republishes
Channels on the register whose posts this channel has forwarded.
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.
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 August 2026 — this entry's latest reading, not the date you are reading this.
“SecurityRise appsec blog” (@vulns), 2,132 subscribers as measured 13 August 2026. Telegram Register, tgregister.com/channel/vulns.
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.