NetSight

Security Dashboard

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

Reset
27 matching advisories · page 1 of 1Index updated just now · Subscribe · RSS
SeverityIDTitleAffectedAge
low3.4 CVE-2026-126359 Hono: `css` helper does not escape a closing tag split between the template and an interpolated value, allowing HTML injection npm · hono 9 days ago low3.8 CVE-2026-106468 The Code Snippets WordPress plugin before 4.1.0 does not verify network-level capabilities before honouring a network-scope parameter on its snippet import rou… Unknown · Code Snippets, codesnippetspro · Code Snippets 11 days ago low4.7 GHSA-6623-4q32-82v8 Duplicate Advisory: hono/jsx renders plain strings unescaped in boundary components, leading to XSS npm · hono 2026-09-19 low3.7 CVE-2026-71849 Hono is a Web application framework that provides support for any JavaScript runtime. npm · hono 2026-08-07 low3.7 CVE-2026-56764 Hono before 4.11.10 contains a timing attack vulnerability in the basicAuth and bearerAuth middlewares due to non-constant-time string comparison in the timing… Hono 2026-07-15 low3.8 CVE-2026-44459 Hono is a Web application framework that provides support for any JavaScript runtime. npm · hono 2026-05-09 low3.7 GHSA-gq3j-xvxp-8hrf Hono added timing comparison hardening in basicAuth and bearerAuth npm · hono 2026-02-19 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 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 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 low2.9 CVE-2023-51433 Some Honor products are affected by incorrect privilege assignment vulnerability, successful exploitation could cause information leak. hihonor · magic_ui 2023-12-29 low3.2 CVE-2023-51432 Some Honor products are affected by out of bounds read vulnerability, successful exploitation could cause information leak. hihonor · magic_ui 2023-12-29 low3.3 CVE-2023-23440 Some Honor products are affected by information leak vulnerability, successful exploitation could cause the information leak. hihonor · lge-an00_firmware 2023-12-29 low3.3 CVE-2023-23437 Some Honor products are affected by information leak vulnerability, successful exploitation could cause the information leak hihonor · vmall 2023-12-29 low3.3 CVE-2023-23430 Some Honor products are affected by incorrect privilege assignment vulnerability, successful exploitation could cause device service exceptions. hihonor · magichome 2023-12-29 low3.3 CVE-2023-23428 Some Honor products are affected by incorrect privilege assignment vulnerability, successful exploitation could cause device service exceptions. honor · magicos 2023-12-29 low2.7 CVE-2023-27266 Mattermost fails to honor the ShowEmailAddress setting when constructing a response to the /api/v4/users/me/teams API endpoint, allowing an attacker with team … mattermost · mattermost_server 2023-02-27 low2.7 CVE-2023-27265 Mattermost fails to honor the ShowEmailAddress setting when constructing a response to the "Regenerate Invite Id" API endpoint, allowing an attacker with team … mattermost · mattermost_server 2023-02-27 low2.6 CVE-2020-15168 The `size` option isn't honored after following a redirect in node-fetch npm · node-fetch 2020-09-10 low2.4 CVE-2020-1833 Honor 9X smartphones with versions earlier than 9.1.1.172(C00E170R8P1) have an improper authentication vulnerability. huawei · honor_9x_firmware 2020-05-29 low3.5 CVE-2019-5252 There is an improper authentication vulnerability in Huawei smartphones (Y9, Honor 8X, Honor 9 Lite, Honor 9i, Y6 Pro). huawei · enjoy_8_plus_firmware, huawei · y9_firmware, huawei · honor_8x_firmware +3 2019-12-14 low3.3 CVE-2019-5292 Honor 10 Lite, Honor 8A, Huawei Y6 mobile phones with the versions before 9.1.0.217(C00E215R3P1), the versions before 9.1.0.205(C00E97R1P9), the versions befor… huawei · honor_10_lite_firmware, huawei · honor_8a_firmware, huawei · huawei_y6_firmware 2019-11-13 low2.4 CVE-2019-5213 Honor play smartphones with versions earlier than Cornell-AL00A 9.1.0.321(C00E320R1P1T8) have an insufficient authentication vulnerability. huawei · honor_play_firmware 2019-11-12 low3.3 CVE-2019-5301 Huawei smart phones Honor V20 with the versions before 9.0.1.161(C00E161R2P2) have an information leak vulnerability. huawei · honor_v20_firmware 2019-08-08 low2.3 CVE-2017-15307 Huawei Honor 8 smartphone with software versions earlier than FRD-L04C567B389 and earlier than FRD-L14C567B389 have a permission control vulnerability due to i… huawei · honor_8_firmware 2017-12-22 low2.1 CVE-2005-4344 Adobe (formerly Macromedia) ColdFusion MX 7.0 does not honor when the CFOBJECT /CreateObject(Java) setting is disabled, which allows local users to create an o… macromedia · coldfusion 2005-12-19

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.