NetSight

Security Dashboard

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

Reset
147 matching advisories · page 1 of 5Index updated 3 minutes ago · Subscribe · RSS
SeverityIDTitleAffectedAge
high7.5 CVE-2026-55367 h2o is an HTTP server with support for HTTP/1.x, HTTP/2 and HTTP/3. 17 days ago high8.1 CVE-2026-55368 h2o is an HTTP server with support for HTTP/1.x, HTTP/2 and HTTP/3. h2o · h2o, h2o · H2O 17 days ago medium6.5 CVE-2026-59993 Picotls is a TLS protocol library that allows users select different crypto backends based on their use case. h2o · picotls 22 days ago critical GHSA-8cp4-v6r9-3xh5 Malicious code in knoll-u8h2o-1k3qx-comet-project (npm)Malware npm · knoll-u8h2o-1k3qx-comet-project 2026-09-17 medium6.5 CVE-2021-43613 An issue was discovered in SysPasswordDxe in Insyde InsydeH2O. 2026-09-03 critical9.8 CVE-2026-65700 h2oGPT through 0.2.1 contains a path traversal vulnerability in the OpenAI-compatible files API that allows unauthenticated remote attackers to read, write, an… h2oGPT 2026-07-23 high7.5 CVE-2026-54340 h2o is an HTTP server with support for HTTP/1.x, HTTP/2 and HTTP/3. h2o · h2o 2026-07-17 high7.5 CVE-2026-44453 h2o is an HTTP server with support for HTTP/1.x, HTTP/2 and HTTP/3. h2o · h2o 2026-07-16 medium5.9 CVE-2026-44452 h2o is an HTTP server with support for HTTP/1.x, HTTP/2 and HTTP/3. h2o · h2o 2026-07-16 high7.5 CVE-2026-44436 Quicly is an IETF QUIC protocol implementation intended primarily for use within the H2O HTTP server. h2o · quicly 2026-07-16 high7.5 CVE-2026-44435 Quicly is an IETF QUIC protocol implementation intended primarily for use within the H2O HTTP server. h2o · quicly 2026-07-16 medium5.3 CVE-2026-44434 Quicly is an IETF QUIC protocol implementation intended primarily for use within the H2O HTTP server. h2o · quicly 2026-07-16 medium5.3 CVE-2026-44433 Quicly is an IETF QUIC protocol implementation intended primarily for use within the H2O HTTP server. h2o · quicly 2026-07-16 high7.5 CVE-2026-55213 h2o is an HTTP server with support for HTTP/1.x, HTTP/2 and HTTP/3. 2026-07-10 medium5.3 CVE-2026-8752 A weakness has been identified in h2oai h2o-3 up to 7402. h2o · h2o 2026-05-17 high7.3 CVE-2026-8751 A security flaw has been discovered in h2oai h2o-3 up to 7402. h2o · h2o 2026-05-17 medium5.3 CVE-2026-8750 A vulnerability was identified in h2oai h2o-3 up to 7402. h2o · h2o 2026-05-17 critical9.8 CVE-2026-3960 A critical remote code execution vulnerability exists in the unauthenticated REST API endpoint /99/ImportSQLTable in H2O-3 version 3.46.0.9 and prior. maven · ai.h2o:h2o-core 2026-04-23 critical9.1 CVE-2024-5986 A vulnerability in h2oai/h2o-3 version 3.46.0.1 allows remote attackers to write arbitrary data to any file on the server. maven · ai.h2o:h2o-core, pip · h2o 2026-02-02 high7.5 CVE-2025-61684 Quicly, an IETF QUIC protocol implementation, is susceptible to a denial-of-service attack prior to commit d9d3df6a8530a102b57d840e39b0311ce5c9e14e. h2o · quicly 2026-01-19 medium6.3 CVE-2025-10769 A vulnerability has been found in h2oai h2o-3 up to 3.46.08. h2o · h2o 2025-09-21 medium6.3 CVE-2025-10768 A flaw has been found in h2oai h2o-3 up to 3.46.08. h2o · h2o 2025-09-21 critical9.8 CVE-2025-6544 A deserialization vulnerability exists in h2oai/h2o-3 versions <= 3.46.0.8, allowing attackers to read arbitrary system files and execute arbitrary code. maven · ai.h2o:h2o-core, pip · h2o 2025-09-21 high8.8 CVE-2025-52389 An Insecure Direct Object Reference (IDOR) in Envasadora H2O Eireli - Soda Cristal v40.20.4 allows authenticated attackers to access sensitive data for other u… 2025-09-08 critical9.8 CVE-2025-5662 A deserialization vulnerability exists in the H2O-3 REST API (POST /99/ImportSQLTable) that affects all versions up to 3.46.0.7. all 2025-09-02 critical9.8 CVE-2025-6507 A vulnerability in the h2oai/h2o-3 repository allows attackers to exploit deserialization of untrusted data, potentially leading to arbitrary code execution an… 2025-09-01 high7.5 CVE-2024-55567 Improper input validation was discovered in UsbCoreDxe in Insyde InsydeH2O kernel 5.4 before 05.47.01, 5.5 before 05.55.01, 5.6 before 05.62.01, and 5.7 before… insyde · insydeh2o 2025-06-12 high7.9 CVE-2024-52880 An issue was discovered in Insyde InsydeH2O kernel 5.2 before version 05.29.50, kernel 5.3 before version 05.38.50, kernel 5.4 before version 05.46.50, kernel … insyde · kernel 2025-05-15 high7.5 CVE-2024-52879 An issue was discovered in Insyde InsydeH2O kernel 5.2 before version 05.29.50, kernel 5.3 before version 05.38.50, kernel 5.4 before version 05.46.50, kernel … insyde · insydeh2o 2025-05-15 high7.5 CVE-2024-52878 An issue was discovered in Insyde InsydeH2O kernel 5.2 before version 05.29.50, kernel 5.3 before version 05.38.50, kernel 5.4 before version 05.46.50, kernel … insyde · insydeh2o 2025-05-15

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.