NetSight

Security Dashboard

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

Reset
16 matching advisories · page 1 of 1Index updated just now · Subscribe · RSS
SeverityIDTitleAffectedAge
high7.5 CVE-2026-15793 BuildKit custom frontends or clients using the raw low-level API can set git.checkoutbundle=true when checking out Git sources. mobyproject · buildkit 2026-07-21 high7.5 CVE-2026-15792 A malicious BuildKit client or frontend could craft a request that could lead to BuildKit daemon crashing with a panic. mobyproject · buildkit 2026-07-21 high7.5 CVE-2026-15791 A crafted message in the BuildKit low-level build API can be used to remove the contents of the /tmp directory. mobyproject · buildkit 2026-07-21 high7.5 CVE-2026-15789 A custom client can produce such an upload request to the BuildKit daemon that files can escape from the BuildKit-controlled state directory. mobyproject · buildkit 2026-07-21 high7.5 CVE-2026-15788 BuildKit's cache mount source= selector on Windows Container on Windows (WCOW) workers does not detect NTFS directory junctions placed inside the cache root. mobyproject · buildkit 2026-07-20 high7.2 CVE-2026-42306 Docker: Race condition in docker cp allows bind mount redirection to host path go · github.com/docker/docker, go · github.com/moby/moby/v2, go · github.com/moby/moby 2026-05-18 high7.5 CVE-2026-33748 BuildKit is a toolkit for converting source code to build artifacts in an efficient, expressive and repeatable manner. go · github.com/moby/buildkit 2026-03-26 high8.4 CVE-2026-33747 BuildKit is a toolkit for converting source code to build artifacts in an efficient, expressive and repeatable manner. go · github.com/moby/buildkit 2026-03-26 high8.1 CVE-2024-36623 Moby Race Condition vulnerability go · github.com/moby/moby 2024-11-29 high6.5 CVE-2024-36621 Moby Race Condition vulnerability go · github.com/moby/moby 2024-11-29 high8.7 CVE-2024-23651 BuildKit vulnerable to possible race condition with accessing subpaths from cache mounts go · github.com/moby/buildkit 2024-01-31 high7.5 CVE-2023-28840 Docker Swarm encrypted overlay network may be unauthenticated go · github.com/docker/docker 2023-04-04 high7.1 CVE-2021-32847 HyperKit is a toolkit for embedding hypervisor capabilities in an application. mobyproject · hyperkit 2023-02-20 high7.7 CVE-2021-32846 HyperKit is a toolkit for embedding hypervisor capabilities in an application. mobyproject · hyperkit 2023-02-17 high7.7 CVE-2021-32845 HyperKit is a toolkit for embedding hypervisor capabilities in an application. mobyproject · hyperkit 2023-02-17 high7.5 CVE-2018-12608 Docker Authentication Bypass go · github.com/docker/docker 2018-09-10

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.