NetSight

Security Dashboard

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

Reset
170 matching advisories · page 3 of 6Index updated 3 minutes ago · Subscribe · RSS
SeverityIDTitleAffectedAge
high7.5 GHSA-c447-w54g-f55j Duplicate Advisory: OpenClaw Telegram webhook request bodies were read before secret validation, enabling unauthenticated resource exhaustion npm · openclaw 2026-03-29 medium4.8 CVE-2026-35628 OpenClaw before 2026.3.25 contains a missing rate limiting vulnerability in Telegram webhook authentication that allows attackers to brute-force weak webhook s… npm · openclaw 2026-03-27 high7.1 CVE-2026-23807 Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in WP Socio WP Telegram Widget and Join Link wptelegram-widg… WP Telegram Widget and Join Link: from n/a through 2026-03-25 high7.5 CVE-2026-32980 OpenClaw before 2026.3.13 reads and buffers Telegram webhook request bodies before validating the x-telegram-bot-api-secret-token header, allowing unauthentica… npm · openclaw 2026-03-16 medium6.9 GHSA-xwcj-hwhf-h378 OpenClaw Telegram media fetch errors exposed bot tokens in logged file URLs npm · openclaw 2026-03-16 medium GHSA-h656-5vcf-cm23 OpenClaw: Unauthorized Telegram Senders Trigger Media Download and Disk Write Before Access Check npm · openclaw 2026-03-03 high7.1 GHSA-qj22-xqjr-v83v OpenClaw's Telegram message_reaction authorization bypass allows unauthorized system-event injection npm · openclaw 2026-03-03 medium5.5 CVE-2026-27004 OpenClaw session tool visibility hardening and Telegram webhook secret fallback npm · openclaw 2026-02-18 medium5.5 CVE-2026-27003 OpenClaw: Telegram bot token exposure via logs npm · openclaw 2026-02-18 medium6.5 CVE-2026-28480 OpenClaw versions prior to 2026.2.14 contain an authorization bypass vulnerability where Telegram allowlist matching accepts mutable usernames instead of immut… npm · openclaw, npm · clawdbot 2026-02-18 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 high7.5 CVE-2026-25474 OpenClaw has a Telegram webhook request forgery (missing `channels.telegram.webhookSecret`) → auth bypass npm · openclaw 2026-02-17 high7.5 CVE-2021-47793 Telegram Desktop 2.9.2 contains a denial of service vulnerability that allows attackers to crash the application by sending an oversized message payload. telegram · telegram_desktop 2026-01-16 medium5.3 CVE-2025-68589 Missing Authorization vulnerability in WP Socio WP Telegram Widget and Join Link wptelegram-widget allows Exploiting Incorrectly Configured Access Control Secu… WP Telegram Widget and Join Link: from n/a through 2025-12-24 medium4.3 CVE-2025-62993 Missing Authorization vulnerability in rainafarai Notification for Telegram notification-for-telegram allows Exploiting Incorrectly Configured Access Control S… Notification for Telegram: from n/a through 2025-12-09 high7.2 CVE-2025-13068 The Telegram Bot & Channel plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the Telegram username in all versions up to, and including, 4.… 2025-11-25 critical GHSA-vm7h-w3cw-c54c Malware in telegram-travis-apiMalware npm · telegram-travis-api 2025-11-10 critical GHSA-4wj5-jm79-gr5w Malware in telegram-bot-starterMalware npm · telegram-bot-starter 2025-10-31 critical GHSA-58wc-9w3h-63ch Malware in telegram-bot-startMalware npm · telegram-bot-start 2025-10-31 critical GHSA-pv3r-qjxv-f6rp Malware in custom-telegram-bot-apiMalware npm · custom-telegram-bot-api 2025-10-31 medium4.3 CVE-2025-58794 Cross-Site Request Forgery (CSRF) vulnerability in rainafarai Notification for Telegram notification-for-telegram allows Cross Site Request Forgery.This issue … Notification for Telegram: from n/a through 2025-09-05 critical9.8 CVE-2025-30949 Deserialization of Untrusted Data vulnerability in Guru Team Site Chat on Telegram site-chat-on-telegram allows Object Injection.This issue affects Site Chat o… Site Chat on Telegram: from n/a through 2025-07-16 critical GHSA-59f9-92h2-xwpj Malware in telegram-pk-auto-senderMalware npm · telegram-pk-auto-sender 2025-07-15 critical10.0 CVE-2025-52572 Hikka, a Telegram userbot, has vulnerability affects all users on all versions of Hikka. 2025-06-24 critical9.6 CVE-2025-52571 Hikka is a Telegram userbot. 2025-06-24 medium4.4 CVE-2025-5939 The Telegram for WP plugin for WordPress is vulnerable to Stored Cross-Site Scripting via admin settings in all versions up to, and including, 1.6.1 due to ins… 2025-06-13 medium6.4 CVE-2025-5236 The NinjaTeam Chat for Telegram plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the ‘username’ parameter in all versions up to, and inclu… ninjateam · chat_for_telegram 2025-05-30 critical GHSA-x392-2722-vc52 Malware in node-telegram-bots-apiMalware npm · node-telegram-bots-api 2025-05-22 critical GHSA-rqwq-r552-5mfq Malware in node-telegram-utilMalware npm · node-telegram-util 2025-05-22 critical GHSA-r25v-crj5-348p Malware in node-telegram-utilsMalware npm · node-telegram-utils 2025-05-22

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.