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
medium5.4 CVE-2026-56743 Cilium may unexpectedly allow ingress traffic from the local namespace when a Kubernetes NetworkPolicy is configured with an ipBlock match go · github.com/cilium/cilium 2026-07-15 medium5.9 CVE-2026-56742 Cilium: Namespaced HTTPRoutes can redirect traffic to other namespaces go · github.com/cilium/cilium, go · github.com/cilium/ciliumCilium 2026-07-15 medium6.9 CVE-2026-53935 CiliumLocalRedirectPolicy addressMatcher allows cross-namespace service traffic hijacking and can break service translation go · github.com/cilium/cilium 2026-07-06 medium5.5 CVE-2026-45886 In the Linux kernel, the following vulnerability has been resolved: bpf: Fix bpf_xdp_store_bytes proto for read-only arg While making some maps in Cilium read-… linux · linux_kernel 2026-05-27 medium5.4 CVE-2026-33726 Cilium is a networking, observability, and security solution with an eBPF-based dataplane. go · github.com/cilium/cilium 2026-03-26 medium6.1 CVE-2026-26963 Cilium may not enforce host firewall policies when Native Routing, WireGuard and Node Encryption are enabled go · github.com/cilium/cilium 2026-02-19 medium4.0 CVE-2025-64715 Cilium with misconfigured toGroups in policies can lead to unrestricted egress traffic go · github.com/cilium/cilium 2025-11-29 medium5.3 CVE-2025-48056 Character injection in Hubble CLI go · github.com/cilium/hubble 2025-05-20 medium4.0 CVE-2025-32793 In Cilium, packets from terminating endpoints may not be encrypted in Wireguard-enabled clusters go · github.com/cilium/cilium 2025-04-21 medium6.5 CVE-2025-23047 Cilium has an information leakage via insecure default Hubble UI CORS header go · github.com/cilium/cilium 2025-01-22 medium5.3 CVE-2025-23028 DoS in Cilium agent DNS proxy from crafted DNS responses go · github.com/cilium/cilium 2025-01-22 medium5.8 CVE-2024-52529 Cilium's Layer 7 policy enforcement may not occur in policies with wildcarded port ranges go · github.com/cilium/cilium 2024-11-25 medium4.0 CVE-2024-47825 Cilium's CIDR deny policies may not take effect when a more narrow CIDR allow is present go · github.com/cilium/cilium 2024-10-21 medium5.4 CVE-2024-42486 Cilium leaks information via incorrect ReferenceGrant update logic in Gateway API go · github.com/cilium/cilium 2024-08-16 medium6.8 CVE-2024-42488 Policy bypass for Host Firewall policy due to race condition in Cilium agent go · github.com/cilium/cilium 2024-08-15 medium4.0 CVE-2024-42487 Gateway API route matching order contradicts specification go · github.com/cilium/cilium 2024-08-15 medium6.1 CVE-2024-28250 Unencrypted traffic between nodes when using WireGuard and L7 policies go · github.com/cilium/cilium 2024-03-18 medium6.1 CVE-2024-28249 Unencrypted traffic between nodes when using IPsec and L7 policies go · github.com/cilium/cilium 2024-03-18 medium6.1 CVE-2024-25631 Unencrypted traffic between pods when using Wireguard and an external kvstore go · github.com/cilium/cilium 2024-02-20 medium6.1 CVE-2024-25630 Unencrypted ingress/health traffic when using Wireguard transparent encryption go · github.com/cilium/cilium 2024-02-20 medium6.9 CVE-2023-41333 Cilium vulnerable to bypass of namespace restrictions in CiliumNetworkPolicy go · github.com/cilium/cilium 2023-09-27 medium5.3 CVE-2023-30851 Potential HTTP policy bypass when using header rules in Cilium go · github.com/cilium/cilium 2023-05-22 medium4.8 CVE-2023-28114 `cilium-cli` disables etcd authorization for clustermesh clusters go · github.com/cilium/cilium-cli 2023-03-21 medium6.5 CVE-2023-27595 Cilium eBPF filters may be temporarily removed during agent restart go · github.com/cilium/cilium 2023-03-17 medium4.2 CVE-2023-27594 Potential network policy bypass when routing IPv6 traffic go · github.com/cilium/cilium 2023-03-17 medium4.4 CVE-2023-27593 cilium-agent container can access the host via `hostPath` mount go · github.com/cilium/cilium 2023-03-17 medium4.3 GHSA-pfhr-pccp-hwmh Network Policies & (Clusterwide) Cilium Network Policies with namespace label selectors may unexpectedly select pods with maliciously crafted labels go · github.com/cilium/cilium, go · github.com/cilium/cilium, go · github.com/cilium/cilium 2022-08-30

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.