NetSight

Security Dashboard

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

Reset
21 matching advisories · page 1 of 1Index updated just now · Subscribe · RSS
SeverityIDTitleAffectedAge
low3.1 CVE-2026-106496 Backstage: Inconsistent enforcement of allowed location types during catalog processing npm · @backstage/plugin-catalog-backend 46 days ago low3.0 CVE-2026-106493 Backstage: Cloud storage catalog locations may cross configured storage boundaries npm · @backstage/plugin-catalog-backend-module-azure, npm · @backstage/plugin-catalog-backend-module-aws, npm · @backstage/backend-defaults 46 days ago low3.5 CVE-2026-106487 Backstage: Unsupported catalog cluster authentication mode in kubernetes backend npm · @backstage/plugin-kubernetes-backend 46 days ago low2.0 CVE-2026-29184 @backstage/plugin-scaffolder-backend Vulnerable to Potential Session Token Exfiltration via Log Redaction Bypass npm · @backstage/plugin-scaffolder-backend 2026-03-05 low2.7 CVE-2026-29185 Backstage vulnerable to potential reading of SCM URLs using built in token npm · @backstage/integration 2026-03-05 low CVE-2026-24408 sigstore CSRF possibility in OIDC authentication during signing pip · sigstore 2026-01-26 low3.5 CVE-2026-24048 Backstage has a Possible SSRF when reading from allowed URL's in `backend.reading.allow` npm · @backstage/backend-defaults 2026-01-21 low3.3 CVE-2025-63396 An issue was discovered in PyTorch v2.5 and v2.7.1. linuxfoundation · pytorch 2025-11-12 low2.0 CVE-2025-59349 Dragonfly's directories created via os.MkdirAll are not checked for permissions go · github.com/dragonflyoss/dragonfly, go · d7y.io/dragonfly/v2 2025-09-17 low3.3 CVE-2025-3136 A vulnerability, which was classified as problematic, has been found in PyTorch 2.6.0. linuxfoundation · pytorch 2025-04-03 low3.3 CVE-2025-3121 A vulnerability classified as problematic has been found in PyTorch 2.6.0. linuxfoundation · pytorch 2025-04-02 low3.3 CVE-2025-2953 PyTorch susceptible to local Denial of Service pip · torch 2025-03-30 low2.5 CVE-2025-2149 PyTorch: Manipulation of the argument scale/zero_point leads to improper initialization via Quantized Sigmoid Module pip · torch 2025-03-10 low2.7 CVE-2024-22261 SQL Injection in Harbor scan log API go · github.com/goharbor/harbor 2024-06-02 low2.3 CVE-2024-20051 In flashc, there is a possible system crash due to an uncaught exception. linuxfoundation · yocto, rdkcentral · rdk-b, google · android +1 2024-04-01 low3.7 CVE-2023-37264 Pipelines do not validate child UIDs go · github.com/tektoncd/pipeline 2023-07-07 low2.7 CVE-2023-32684 In Lima, a malicious disk image could read a single file on the host filesystem as a qcow2/vmdk backing file go · github.com/lima-vm/lima 2023-05-30 low3.3 CVE-2023-20726 In mnld, there is a possible leak of GPS location due to a missing permission check. linuxfoundation · yocto, rdkcentral · rdkb, google · android +1 2023-05-15 low3.3 CVE-2021-4326 A vulnerability in Imperative framework which allows already-privileged local actors to execute arbitrary shell commands via plugin install/update commands, or… npm · @zowe/imperative 2023-03-01 low2.4 CVE-2022-4875 A vulnerability has been found in fossology and classified as problematic. linuxfoundation · fossology 2023-01-04 low3.0 CVE-2021-41190 Clarify Content-Type handling go · github.com/opencontainers/distribution-spec 2021-11-17

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.