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 3 minutes ago · Subscribe · RSS
SeverityIDTitleAffectedAge
critical9.9 CVE-2026-77459 Argo CD: AppProject destination-namespace and resource restrictions bypassed by PreDelete/PostDelete resource hooks go · github.com/argoproj/argo-cd/v2, go · github.com/argoproj/argo-cd/v3 39 days ago critical9.9 CVE-2026-54526 Argo Workflows: ArtifactGC.PodSpecPatch bypasses Strict/Secure template reference allow-list (Incomplete fix for CVE-2026-31892) go · github.com/argoproj/argo-workflows/v4, go · github.com/argoproj/argo-workflows/v3, go · github.com/argoproj/argo-workflows 2026-07-16 critical9.6 CVE-2026-42880 Argo CD is a declarative, GitOps continuous delivery tool for Kubernetes. go · github.com/argoproj/argo-cd/v3 2026-05-07 critical9.8 CVE-2026-28229 Unauthorized access to Argo Workflows Template go · github.com/argoproj/argo-workflows/v4, go · github.com/argoproj/argo-workflows/v3 2026-03-11 critical9.9 CVE-2025-55190 Argo CD's Project API Token Exposes Repository Credentials go · github.com/argoproj/argo-cd/v2, go · github.com/argoproj/argo-cd/v3 2025-09-04 critical9.0 CVE-2025-47933 Argo CD allows cross-site scripting on repositories page go · github.com/argoproj/argo-cd, go · github.com/argoproj/argo-cd/v2, go · github.com/argoproj/argo-cd/v3 2025-05-28 critical9.9 CVE-2025-32445 Argo Events users can gain privileged access to the host system and cluster with EventSource and Sensor CR go · github.com/argoproj/argo-events 2025-04-14 critical9.0 CVE-2024-31989 ArgoCD Vulnerable to Use of Risky or Missing Cryptographic Algorithms in Redis Cache go · github.com/argoproj/argo-cd/v2, go · github.com/argoproj/argo-cd 2024-05-21 critical9.8 CVE-2024-21652 Bypassing Brute Force Protection via Application Crash and In-Memory Data Loss go · github.com/argoproj/argo-cd/v2 2024-03-18 critical9.0 CVE-2024-28175 Cross-site scripting on application summary component go · github.com/argoproj/argo-cd/v2, go · github.com/argoproj/argo-cd 2024-03-13 critical9.9 CVE-2023-40029 Argo CD cluster secret might leak in cluster details page go · github.com/argoproj/argo-cd/v2 2023-09-07 critical9.1 CVE-2023-23947 Users with any cluster secret update access may update out-of-bounds cluster secrets go · github.com/argoproj/argo-cd 2023-02-16 critical9.0 CVE-2023-22482 JWT audience claim is not verified go · github.com/argoproj/argo-cd 2023-01-25 critical9.0 CVE-2022-31035 Argo CD's external URLs for Deployments can include JavaScript go · github.com/argoproj/argo-cd, go · github.com/argoproj/argo-cd/v2 2022-06-21 critical10.0 CVE-2022-29165 Argo CD will blindly trust JWT claims if anonymous access is enabled go · github.com/argoproj/argo-cd/v2, go · github.com/argoproj/argo-cd 2022-05-20 critical9.9 CVE-2022-24768 Improper access control allows admin privilege escalation in Argo CD go · github.com/argoproj/argo-cd 2022-03-23

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.