NetSight

Security Dashboard

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

Reset
18 matching advisories · page 1 of 1Index updated 2 minutes ago · Subscribe · RSS
SeverityIDTitleAffectedAge
medium6.1 CVE-2026-41568 Docker: Race condition in docker cp allows creation of arbitrary empty files on the host via symlink swap go · github.com/docker/docker, go · github.com/moby/moby/v2, go · github.com/moby/moby 2026-05-18 medium4.6 CVE-2025-54388 Moby firewalld reload makes published container ports accessible from remote hosts go · github.com/docker/docker 2025-07-29 medium6.5 CVE-2024-36620 NULL Pointer Dereference on moby image history go · github.com/moby/moby 2024-11-29 medium4.7 CVE-2024-32473 IPv6 enabled on IPv4-only network interfaces go · github.com/docker/docker 2024-04-18 medium5.9 CVE-2024-29018 Moby's external DNS requests from 'internal' networks could lead to data exfiltration go · github.com/docker/docker 2024-03-20 medium6.9 CVE-2024-24557 Classic builder cache poisoning go · github.com/docker/docker, go · github.com/moby/moby 2024-02-01 medium5.3 CVE-2024-23650 BuildKit vulnerable to possible panic when incorrect parameters sent from frontend go · github.com/moby/buildkit 2024-01-31 medium6.8 CVE-2023-28841 Docker Swarm encrypted overlay network traffic may be unencrypted go · github.com/docker/docker 2023-04-04 medium6.8 CVE-2023-28842 Docker Swarm encrypted overlay network with a single endpoint is unauthenticated go · github.com/docker/docker 2023-04-04 medium6.5 CVE-2023-26054 Buildkit credentials inlined to Git URLs could end up in provenance attestation go · github.com/moby/buildkit 2023-03-06 medium6.2 CVE-2021-32844 HyperKit is a toolkit for embedding hypervisor capabilities in an application. mobyproject · hyperkit 2023-02-17 medium6.2 CVE-2021-32843 HyperKit is a toolkit for embedding hypervisor capabilities in an application. mobyproject · hyperkit 2023-02-17 medium5.3 CVE-2022-36109 Docker supplementary group permissions not set up properly, allowing attackers to bypass primary group restrictions go · github.com/docker/docker 2022-09-09 medium4.8 CVE-2022-27652 Incorrect Default Permissions in CRI-O go · github.com/cri-o/cri-o 2022-04-18 medium5.9 CVE-2022-24769 Moby (Docker Engine) started with non-empty inheritable Linux process capabilities go · github.com/moby/moby, go · github.com/docker/docker 2022-03-24 medium5.9 CVE-2021-41091 Moby (Docker Engine) Insufficiently restricted permissions on data directory go · github.com/moby/moby, go · github.com/docker/docker 2021-10-04 medium5.3 CVE-2018-10892 The default OCI linux spec in oci/defaults{_linux}.go in Docker/Moby from 1.11 to current does not block /proc/acpi pathnames. docker · docker, mobyproject · moby, redhat · openstack +3 2018-07-06 medium5.9 CVE-2017-16539 Docker Moby /proc/scsi Path Exposure Allows Host Data Loss (SCSI MICDROP) go · github.com/moby/moby 2017-11-04

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.