NetSight

Security Dashboard

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

Reset
305 matching advisories · page 5 of 11Index updated just now · Subscribe · RSS
SeverityIDTitleAffectedAge
high8.1 CVE-2025-62610 Hono Improper Authorization vulnerability npm · hono 2025-10-22 medium4.0 CVE-2025-57838 Some Honor products are affected by information leak vulnerability, successful exploitation of this vulnerability may affect service confidentiality. 2025-10-20 medium5.3 CVE-2025-59139 Hono has Body Limit Middleware Bypass npm · hono 2025-09-12 high7.5 CVE-2025-58362 Hono's flaw in URL path parsing could cause path confusion npm · hono 2025-09-03 high GHSA-3j63-5h8p-gf7c x402 SDK vulnerable in outdated versions in resource servers for builders npm · x402, npm · x402-next, npm · x402-express +1 2025-08-20 medium5.9 CVE-2025-36124 IBM WebSphere Application Server Liberty 17.0.0.3 through 25.0.0.8 could allow a remote attacker to bypass security restrictions caused by a failure to honor J… ibm · websphere_application_server 2025-08-12 high8.8 CVE-2025-46014 Several services in Honor Device Co., Ltd Honor PC Manager v16.0.0.118 was discovered to connect services to the named pipe iMateBookAssistant with default or … honor · pc_manager 2025-06-30 medium5.5 CVE-2025-38061 In the Linux kernel, the following vulnerability has been resolved: net: pktgen: fix access outside of user given buffer in pktgen_thread_write() Honour the us… linux · linux_kernel, debian · debian_linux 2025-06-18 medium5.5 CVE-2025-37816 In the Linux kernel, the following vulnerability has been resolved: mei: vsc: Fix fortify-panic caused by invalid counted_by() use gcc 15 honors the __counted_… linux · linux_kernel 2025-05-08 medium4.3 CVE-2025-2197 Browser is affected by type confusion vulnerability, successful exploitation of this vulnerability may affect service availability. honor · baidu 2025-04-17 high8.1 CVE-2025-2188 There is a whitelist mechanism bypass in GameCenter ,successful exploitation of this vulnerability may affect service confidentiality and integrity. honor · gamecenter 2025-04-17 high8.1 CVE-2025-1532 Phoneservice module is affected by code injection vulnerability, successful exploitation of this vulnerability may affect service confidentiality and integrity. honor · phoneservice 2025-04-17 high7.8 CVE-2021-47646 In the Linux kernel, the following vulnerability has been resolved: Revert "Revert "block, bfq: honor already-setup queue merges"" A crash [1] happened to be t… linux · linux_kernel 2025-02-26 low3.3 CVE-2024-47150 Some Honor products are affected by information leak vulnerability, successful exploitation could cause the information leak. honor · magicos 2024-12-26 low3.3 CVE-2024-47149 Some Honor products are affected by incorrect privilege assignment vulnerability, successful exploitation could cause device service exceptions. honor · magicos 2024-12-26 medium6.2 CVE-2024-8994 Some Honor products are affected by information leak vulnerability, successful exploitation could cause the information leak. honor · magicos 2024-12-26 medium6.2 CVE-2024-8993 Some Honor products are affected by information leak vulnerability, successful exploitation could cause the information leak. honor · magicos 2024-12-26 medium4.0 CVE-2024-8992 Some Honor products are affected by information leak vulnerability, successful exploitation could cause the information leak. honor · magicos 2024-12-26 low2.9 CVE-2024-47157 Some Honor products are affected by incorrect privilege assignment vulnerability, successful exploitation could cause device service exceptions. honor · magicos 2024-12-26 medium5.5 CVE-2024-47155 Some Honor products are affected by information leak vulnerability, successful exploitation could cause the information leak. honor · magicos 2024-12-26 medium5.5 CVE-2024-47154 Some Honor products are affected by information leak vulnerability, successful exploitation could cause the information leak. honor · magicos 2024-12-26 medium6.2 CVE-2024-47153 Some Honor products are affected by information leak vulnerability, successful exploitation could cause the information leak. honor · magicos 2024-12-26 medium4.0 CVE-2024-47148 Some Honor products are affected by incorrect privilege assignment vulnerability, successful exploitation could cause device service exceptions. honor · magicos 2024-12-26 low3.3 CVE-2024-47156 Some Honor products are affected by information leak vulnerability, successful exploitation could cause the information leak. honor · magicos 2024-12-26 medium6.3 CVE-2024-47151 Some Honor products are affected by file writing vulnerability, successful exploitation could cause code execution honor · magicos 2024-12-26 medium5.9 CVE-2024-48913 Hono allows bypass of CSRF Middleware by a request without Content-Type header. npm · hono 2024-10-15 high7.8 CVE-2024-43891 In the Linux kernel, the following vulnerability has been resolved: tracing: Have format file honor EVENT_FILE_FL_FREED When eventfs was introduced, special ca… linux · linux_kernel 2024-08-26 medium5.0 CVE-2024-43787 Hono CSRF middleware can be bypassed using crafted Content-Type header npm · hono 2024-08-22 high7.8 CVE-2024-42266 In the Linux kernel, the following vulnerability has been resolved: btrfs: make cow_file_range_inline() honor locked_page on error The btrfs buffered write pat… linux · linux_kernel 2024-08-17 critical9.8 CVE-2024-38395 In iTerm2 before 3.5.2, the "Terminal may report window title" setting is not honored, and thus remote code execution might occur but "is not trivially exploit… iterm2 · iterm2 2024-06-16

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.