NetSight

Security Dashboard

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

Reset
20 matching advisories · page 1 of 1Index updated 12 minutes ago · Subscribe · RSS
SeverityIDTitleAffectedAge
high8.7 CVE-2021-48022 Rocket.Chat versions 0.61.0 before 3.11.4, 3.12.x before 3.12.4 and 3.13.x before 3.13.2 contain a missing authorization vulnerability allowing unauthenticated… Rocket.Chat · Rocket.Chat 3 days ago high7.5 CVE-2026-65644 Rocket.Chat in versions before 8.8.0, 8.7.1, 8.6.2, 8.5.3, 8.4.6, 8.3.8, 8.2.8, 8.1.8, and 7.10.15 has a REST API endpoint POST /api/v1/livechat/visitor that a… rocket.chat · rocket.chat 2026-08-21 high8.1 CVE-2026-55762 Rocket.Chat is an open-source, secure, fully customizable communications platform. 2026-06-24 high7.4 CVE-2026-55759 Rocket.Chat is an open-source, secure, fully customizable communications platform. 2026-06-24 high8.5 CVE-2026-45687 Rocket.Chat is an open-source, secure, fully customizable communications platform. 2026-06-24 high8.7 CVE-2026-45677 Rocket.Chat is an open-source, secure, fully customizable communications platform. 2026-06-24 high7.5 CVE-2026-48929 Rocket.Chat in versions <8.5.1, <8.4.4, <8.3.6, <8.2.6, <8.1.6, <8.0.7, <7.13.9, and <7.10.13 is vulnerable to unauthenticated file deletion. rocket.chat · rocket.chat 2026-06-17 high7.5 CVE-2026-32995 The Rocket.Chat DDP method autoTranslate.translateMessage in versions <8.5.0, <8.4.2, <8.3.4, <8.2.4, <8.1.5, <8.0.5, <7.13.8, and <7.10.12 accepts a client-su… versions, and 2026-05-28 high7.7 CVE-2026-23477 Rocket.Chat is an open-source, secure, fully customizable communications platform. rocket.chat · rocket.chat 2026-01-14 high7.5 CVE-2025-7974 rocket.chat Incorrect Authorization Information Disclosure Vulnerability. rocket.chat · rocket.chat 2025-09-02 high7.5 CVE-2024-46936 Rocket.Chat 6.12.0, 6.11.2, 6.10.5, 6.9.6, 6.8.6, 6.7.8, and before is vulnerable to a message forgery / impersonation issue. 2024-09-25 high7.5 CVE-2024-46935 Denial of service in rocket chat message parser npm · @rocket.chat/message-parser 2024-09-25 high8.6 CVE-2024-39713 Rocket.Chat Server-Side Request Forgery (SSRF) vulnerability npm · rocket.chat 2024-08-05 high7.5 CVE-2023-28356 A vulnerability has been identified where a maliciously crafted message containing a specific chain of characters can cause the chat to enter a hot loop on one… rocket.chat · rocket.chat 2023-05-11 high7.5 CVE-2023-23911 An improper access control vulnerability exists prior to v6 that could allow an attacker to break the E2E encryption of a chat room by a user changing the grou… rocket.chat · rocket.chat 2023-03-10 high8.8 CVE-2023-23917 A prototype pollution vulnerability exists in Rocket.Chat server <5.2.0 that could allow an attacker to a RCE under the admin account. rocket.chat · rocket.chat 2023-02-23 high8.8 CVE-2022-35248 A improper authentication vulnerability exists in Rocket.Chat <v5, <v4.8.2 and <v4.7.5 that allowed two factor authentication can be bypassed when telling the … rocket.chat · rocket.chat 2022-09-23 high8.8 CVE-2022-32211 A SQL injection vulnerability exists in Rocket.Chat <v3.18.6, <v4.4.4 and <v4.7.3 which can allow an attacker to retrieve a reset password token through or a 2… rocket.chat · rocket.chat 2022-09-23 high7.5 CVE-2020-26763 The Rocket.Chat desktop application 2.17.11 opens external links without user interaction. rocket.chat · rocket.chat 2021-07-05 high7.5 CVE-2021-22892 An information disclosure vulnerability exists in the Rocket.Chat server fixed v3.13, v3.12.2 & v3.11.3 that allowed email addresses to be disclosed by enumera… rocket.chat · rocket.chat 2021-05-27

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.