NetSight

Security Dashboard

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

Reset
34 matching advisories · page 1 of 2Index updated just now · Subscribe · RSS
SeverityIDTitleAffectedAge
high8.8 CVE-2026-55797 Argo CD repo-server command injection via crafted SSH repository SOCKS5 proxy URL go · github.com/argoproj/argo-cd/v2, go · github.com/argoproj/argo-cd/v3 43 days ago high7.3 CVE-2026-45738 Argo CD: Stored XSS in application link annotations enables developer-to-admin privilege escalation go · github.com/argoproj/argo-cd/v3, go · github.com/argoproj/argo-cd/v2, go · github.com/argoproj/argo-cd 2026-05-19 high8.5 CVE-2026-42295 Argo Workflows is an open source container-native workflow engine for orchestrating parallel jobs on Kubernetes. go · github.com/argoproj/argo-workflows/v4 2026-05-04 high8.1 CVE-2026-42296 Argo has incomplete fix for CVE-2026-31892: hostNetwork, securityContext, serviceAccountName bypass templateReferencing Strict/Secure go · github.com/argoproj/argo-workflows/v3, go · github.com/argoproj/argo-workflows/v4 2026-05-04 high7.5 CVE-2026-42294 Argo Workflows is an open source container-native workflow engine for orchestrating parallel jobs on Kubernetes. go · github.com/argoproj/argo-workflows/v3, go · github.com/argoproj/argo-workflows/v4 2026-05-04 high8.3 CVE-2026-42297 Argo Workflows is an open source container-native workflow engine for orchestrating parallel jobs on Kubernetes. go · github.com/argoproj/argo-workflows/v4 2026-05-04 high7.7 CVE-2026-40886 Argo Workflows is an open source container-native workflow engine for orchestrating parallel jobs on Kubernetes. go · github.com/argoproj/argo-workflows/v4, go · github.com/argoproj/argo-workflows/v3 2026-04-23 high8.9 CVE-2026-31892 Argo Workflows: WorkflowTemplate Security Bypass via podSpecPatch in Strict/Secure Reference Mode go · github.com/argoproj/argo-workflows/v4, go · github.com/argoproj/argo-workflows/v3, go · github.com/argoproj/argo-workflows 2026-03-11 high7.3 CVE-2026-23960 Argo Workflows affected by stored XSS in the artifact directory listing go · github.com/argoproj/argo-workflows/v3, go · github.com/argoproj/argo-workflows 2026-01-21 high8.1 CVE-2025-66626 RCE via ZipSlip and symbolic links in argoproj/argo-workflows go · github.com/argoproj/argo-workflows/v3, go · github.com/argoproj/argo-workflows 2025-12-09 high8.5 CVE-2025-62157 Argo Workflow may expose artifact repository credentials go · github.com/argoproj/argo-workflows/v3 2025-10-14 high8.1 CVE-2025-62156 Argo Workflow has a Zipslip Vulnerability go · github.com/argoproj/argo-workflows/v3 2025-10-14 high7.5 CVE-2025-59538 Argo CD Unauthenticated Remote DoS via malformed Azure DevOps git.push webhook go · github.com/argoproj/argo-cd/v2, go · github.com/argoproj/argo-cd/v3 2025-09-30 high7.5 CVE-2025-59537 argo-cd vulnerable unauthenticated DoS via malformed Gogs webhook payload go · github.com/argoproj/argo-cd, go · github.com/argoproj/argo-cd/v2, go · github.com/argoproj/argo-cd/v3 2025-09-30 high7.5 CVE-2025-59531 Unauthenticated argocd-server panic via a malicious Bitbucket-Server webhook payload go · github.com/argoproj/argo-cd, go · github.com/argoproj/argo-cd/v2, go · github.com/argoproj/argo-cd/v3 2025-09-30 high7.5 CVE-2024-53862 Access to Archived Argo Workflows with Fake Token in `client` mode go · github.com/argoproj/argo-workflows/v3 2024-12-02 high7.5 CVE-2024-40634 Argo CD Unauthenticated Denial of Service (DoS) Vulnerability via /api/webhook Endpoint go · github.com/argoproj/argo-cd, go · github.com/argoproj/argo-cd/v2 2024-07-22 high7.5 CVE-2024-21662 Bypassing Rate Limit and Brute Force Protection Using Cache Overflow go · github.com/argoproj/argo-cd/v2 2024-03-18 high7.5 CVE-2024-21661 Denial of Service (DoS) Vulnerability Due to Unsafe Array Modification in Multi-threaded Environment go · github.com/argoproj/argo-cd, go · github.com/argoproj/argo-cd/v2 2024-03-18 high8.3 CVE-2024-22424 github.com/argoproj/argo-cd Cross-Site Request Forgery vulnerability go · github.com/argoproj/argo-cd, go · github.com/argoproj/argo-cd/v2 2024-01-19 high7.1 CVE-2023-40025 Argo CD web terminal session doesn't expire go · github.com/argoproj/argo-cd/v2 2023-08-23 high8.5 CVE-2023-22736 Controller reconciles apps outside configured namespaces when sharding is enabled go · github.com/argoproj/argo-cd/v2 2023-01-25 high8.3 CVE-2022-31105 Argo CD certificate verification is skipped for connections to OIDC providers go · github.com/argoproj/argo-cd 2022-07-12 high8.8 CVE-2022-1025 Argo CD improper access control bug can allow malicious user to escalate privileges to admin level go · github.com/argoproj/argo-cd, go · github.com/argoproj/argo-cd/v2 2022-07-12 high8.3 CVE-2022-31034 Insecure entropy in Argo CD's PKCE/Oauth2/OIDC params go · github.com/argoproj/argo-cd, go · github.com/argoproj/argo-cd/v2 2022-06-21 high7.5 CVE-2022-25856 Insecure path traversal in Git Trigger Source can lead to arbitrary file read go · github.com/argoproj/argo-events 2022-06-17 high7.5 CVE-2022-31054 Uses of deprecated API can be used to cause DoS in user-facing endpoints go · github.com/argoproj/argo-events 2022-06-13 high7.1 CVE-2022-29164 Malicious HTML+XHR Artifact Privilege Escalation in Argo Workflows go · github.com/argoproj/argo-workflows/v3 2022-05-06 high7.7 CVE-2022-24730 Path traversal and improper access control allows leaking out-of-bound files from Argo CD repo-server go · github.com/argoproj/argo-cd 2022-03-23 high7.7 CVE-2022-24348 Path traversal and dereference of symlinks in Argo CD go · github.com/argoproj/argo-cd/v2, go · github.com/argoproj/argo-cd 2022-02-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.