NetSight

Security Dashboard

A live picture of new vulnerabilities, flaws exploited in the wild and malicious packages.

Reset
61 matching advisories · page 1 of 3Index updated just now · Subscribe · RSS
SeverityIDTitleAffectedAge
critical GHSA-wv8m-qjx2-frc6 Malicious code in quick-telegram-sender (PyPI)Malware pip · quick-telegram-sender 4 days ago critical GHSA-9hfr-xx64-hrq4 Malicious code in @velliajs/telegram (npm)Malware npm · @velliajs/telegram 12 days ago critical9.8 CVE-2026-109516 The Bot for Telegram on WooCommerce plugin for WordPress is vulnerable to Authentication Bypass leading to Account Takeover in all versions up to, and includin… Guru Team · Bot for Telegram on WooCommerce 24 days ago critical GHSA-c773-2559-g4g3 Malware in node-telegram-socketsMalware npm · node-telegram-sockets 40 days ago critical GHSA-vxg4-4jxm-7ff9 Malicious code in telegram-helper (PyPI)Malware pip · telegram-helper, pip · telegram-helper 2026-09-08 critical GHSA-26q2-fgwq-hw4p Malicious code in claude-channel-telegram (npm)Malware npm · claude-channel-telegram 2026-08-31 critical GHSA-3625-9m73-8r5p Malicious code in telegrampremiumfix (PyPI)Malware pip · telegrampremiumfix, pip · telegrampremiumfix, pip · telegrampremiumfix +2 2026-07-21 critical GHSA-xrpq-hc9r-7rfv Malicious code in telegramdatas (PyPI)Malware pip · telegramdatas 2026-07-21 critical GHSA-j88h-h9h2-8ph9 Malicious code in telegramlite (PyPI)Malware pip · telegramlite, pip · telegramlite 2026-07-21 critical GHSA-57r9-pwc3-fr5j Malicious code in telegramdoxing (PyPI)Malware pip · telegramdoxing 2026-07-21 critical GHSA-rqcp-79hw-74rq Malicious code in telegram-lite-grabber (PyPI)Malware pip · telegram-lite-grabber 2026-07-21 critical GHSA-vgpx-rgw9-4j9q Malicious code in pytelegramapi (PyPI)Malware pip · pytelegramapi, pip · pytelegramapi, pip · pytelegramapi +1 2026-07-21 critical GHSA-f76r-hpjf-frj5 Malicious code in python-aiogram-telegram-updater (PyPI)Malware pip · python-aiogram-telegram-updater 2026-07-21 critical GHSA-q3xw-wc7j-8hx2 Malicious code in aietelegram (PyPI)Malware pip · aietelegram 2026-07-21 critical GHSA-268c-w8m4-rmh2 Malicious code in telegram-bot_middleware (RubyGems)Malware rubygems · telegram-bot_middleware 2026-07-18 critical GHSA-948f-p3pj-wf99 Malicious code in telegram_bot-types (RubyGems)Malware rubygems · telegram_bot-types 2026-07-18 critical GHSA-3vqc-v65q-45c5 Malicious code in telegram-bot_ruby (RubyGems)Malware rubygems · telegram-bot_ruby 2026-07-18 critical GHSA-7544-xc33-j3j5 Malicious code in telegram-bot_api (RubyGems)Malware rubygems · telegram-bot_api 2026-07-18 critical GHSA-6fr9-9v8f-vgw6 Malicious code in telegram-meetup_bot (RubyGems)Malware rubygems · telegram-meetup_bot 2026-07-18 critical GHSA-2897-6wq7-h46j Malicious code in telegram-notifications (RubyGems)Malware rubygems · telegram-notifications 2026-07-18 critical GHSA-qj87-53m9-rvjp Malicious code in telegram_bot-ruby (RubyGems)Malware rubygems · telegram_bot-ruby 2026-07-18 critical GHSA-vgmw-c78j-jrcv Malicious code in ruboty_telegram (RubyGems)Malware rubygems · ruboty_telegram 2026-07-18 critical GHSA-9qhq-jcqv-78g2 Malicious code in lita_telegram-plus (RubyGems)Malware rubygems · lita_telegram-plus 2026-07-18 critical GHSA-9vx8-6j5w-2j42 Malicious code in lita_telegram (RubyGems)Malware rubygems · lita_telegram 2026-07-18 critical GHSA-g69f-2w7f-699g Malicious code in jaconda-telegram (RubyGems)Malware rubygems · jaconda-telegram 2026-07-18 critical GHSA-w59g-hhr4-fjpx Malicious code in capistrano-telegram-notification (RubyGems)Malware rubygems · capistrano-telegram-notification 2026-07-18 critical GHSA-w7f2-c9f3-8986 Malicious code in capistrano_telegram-notification (RubyGems)Malware rubygems · capistrano_telegram-notification 2026-07-18 critical GHSA-874g-gq93-656c Malicious code in capistrano_telegram (RubyGems)Malware rubygems · capistrano_telegram 2026-07-18 critical9.4 CVE-2026-52830 fast-mcp-telegram: Bearer token path traversal bypasses reserved Telegram session protection pip · fast-mcp-telegram 2026-07-02 critical9.8 CVE-2026-28454 OpenClaw versions prior to 2026.2.2 fail to validate webhook secrets in Telegram webhook mode (must be enabled), allowing unauthenticated HTTP POST requests to… npm · openclaw 2026-02-17

Get notifications

Subscribe to new vulnerabilities and early warnings from the last seven days. Pick what matters to your stack and copy the address into any feed reader. More filters appear when you pick a type.

Format:
Open feed

Early warnings are advisories that are published before or without a CVE number, for example malicious packages, advisories with a CVE still pending and reports that are not reviewed yet. Confidence says how well an entry is checked: high, medium or low.

About this dashboard

The dashboard keeps its own index of security advisories and refreshes it every 30 minutes. It merges the national vulnerability database, package advisories, malware reports and the catalog of vulnerabilities that are exploited in the wild into one record per issue. Reports about the same flaw are combined, so nothing is listed twice.

Open any entry for the full record: description, severity vector, affected packages and versions, fixed versions, weakness class, exploitation probability and references.

Sources: the GitHub Advisory Database (reviewed advisories, malware reports and unreviewed reports), the National Vulnerability Database, the CVE Program (cve.org) for brand-new records, the OpenSSF malicious packages list, the CISA catalog of Known Exploited Vulnerabilities and Microsoft's blocklist of malicious VS Code extensions. Every entry names its sources on its detail page.

This product uses the NVD API but is not endorsed or certified by the NVD.

Reading the figures

  • Threat level: a rating computed from three numbers shown next to it: critical advisories in the last 24 hours, vulnerabilities newly confirmed as exploited this week and malware reports this week. It is a quick orientation, not an official warning level.
  • Severity: scores from 9.0 are critical, 7.0 to 8.9 high, 4.0 to 6.9 medium and 0.1 to 3.9 low. Severity describes how bad a flaw is in general. It does not know whether the component is reachable in your environment.
  • Known exploited: exploitation has been observed in real attacks. These are the entries to patch first. Entries with a fix deadline show how many days are left.
  • Early warnings: advisories that appear before or without a CVE number, for example malicious packages, reviewed advisories with a CVE still pending and reports that are not reviewed yet.
  • Priority queue: critical and high advisories of the last 7 days and everything newly exploited, ordered by exploitation status, severity and score.

Questions

Where does the data come from?
From public vulnerability databases, package advisories and the catalog of exploited vulnerabilities. NetSight collects them into its own index every 30 minutes and merges duplicates.
How do I check whether I am affected?
Search for your product or package name, open the record and compare your installed version with the affected and fixed versions. A product name alone does not mean your version is affected.
What does known exploited mean?
Exploitation of this vulnerability has been observed in real attacks. Such entries carry a date they were confirmed and, where one exists, a deadline for applying the fix.
What is an early warning?
An advisory that is published before or without a CVE number, such as a malicious package or a reviewed advisory whose CVE is still pending. They give you a head start, but the details can change.
Is a high severity always more urgent than a low one?
No. Severity measures technical impact in general. Exposure of the affected system, observed exploitation and the exploitation probability matter as much.
Can I follow new advisories automatically?
Yes. Use the notification builder further down to create an RSS, Atom or JSON feed filtered by severity, technology, ecosystem or exploitation status.