NetSight

Security Dashboard

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

Reset
600 matching advisories · page 1 of 20Index updated just now · Subscribe · RSS
SeverityIDTitleAffectedAge
critical9.8 CVE-2026-104252 Vitess is a database clustering system for horizontal scaling of MySQL. go · vitess.io/vitess 39 days ago medium5.3 CVE-2026-106563 Backstage: Improper entity validation in deprecated Kubernetes services endpoint npm · @backstage/plugin-kubernetes-backend 45 days ago medium4.3 CVE-2026-106562 Backstage has incorrect authorization in search engine permission filtering npm · @backstage/plugin-search-backend, npm · @backstage/plugin-search-backend-module-elasticsearch 45 days ago medium5.0 CVE-2026-106561 Backstage has a sensitive information disclosure in Kubernetes resource queries npm · @backstage/plugin-kubernetes-backend 45 days ago high7.1 CVE-2026-106560 Backstage: Improper repository path validation in a Scaffolder backend module npm · @backstage/plugin-scaffolder-backend-module-confluence-to-markdown 45 days ago medium6.3 CVE-2026-106559 Backstage: Improper input validation in Confluence to Markdown scaffolder module npm · @backstage/plugin-scaffolder-backend-module-confluence-to-markdown 45 days ago high8.8 CVE-2026-106558 Backstage: Improper validation of TechDocs MkDocs configuration npm · @backstage/plugin-techdocs-node 45 days ago high7.7 CVE-2026-106556 Backstage is an open framework for building developer portals. linuxfoundation · backstage, linuxfoundation · backstage_plugin-techdocs-node 45 days ago high7.7 CVE-2026-106510 Backstage: Remote code execution via crafted markdown_extensions in TechDocs mkdocs.yml npm · @backstage/plugin-techdocs-node 45 days ago high7.7 CVE-2026-106509 Backstage: Improper validation of MkDocs theme configuration in TechDocs npm · @backstage/plugin-techdocs-node 46 days ago medium5.3 CVE-2026-106508 Backstage has potential file exposure through local TechDocs publisher npm · @backstage/plugin-techdocs-node 46 days ago medium5.3 CVE-2026-106507 Backstage is an open framework for building developer portals. linuxfoundation · backstage_plugin-techdocs-node, linuxfoundation · backstage 46 days ago medium5.3 CVE-2026-106506 Backstage has improper input validation in scaffolder task list ordering npm · @backstage/plugin-scaffolder-backend 46 days ago high7.7 CVE-2026-106505 Backstage: Bypass of MkDocs configuration sanitizer in TechDocs backend npm · @backstage/plugin-techdocs-node 46 days ago medium6.5 CVE-2026-106504 Backstage has sensitive information exposure in scaffolder task logs npm · @backstage/plugin-scaffolder-backend 46 days ago high8.1 CVE-2026-106503 Backstage is an open framework for building developer portals. npm · @backstage/plugin-scaffolder-backend 46 days ago medium5.3 CVE-2026-106502 Backstage may expose sensitive information in Scaffolder task failure events npm · @backstage/plugin-scaffolder-backend 46 days ago critical9.6 CVE-2026-106501 Backstage is an open framework for building developer portals. npm · @backstage/plugin-scaffolder-backend 46 days ago high8.5 CVE-2026-106500 Backstage: Improper task state validation in Scaffolder backend npm · @backstage/plugin-scaffolder-backend 46 days ago medium4.9 CVE-2026-106499 Backstage: Secret-derived values may be exposed in scaffolder task logs npm · @backstage/plugin-scaffolder-backend 46 days ago high7.7 CVE-2026-106498 Backstage: Improper URL validation in catalog entity placeholder resolution npm · @backstage/plugin-catalog-backend 46 days ago medium4.3 CVE-2026-106497 Backstage is an open framework for building developer portals. linuxfoundation · backstage_plugin-catalog-backend, linuxfoundation · backstage 46 days ago low3.1 CVE-2026-106496 Backstage: Inconsistent enforcement of allowed location types during catalog processing npm · @backstage/plugin-catalog-backend 46 days ago medium4.4 CVE-2026-106494 Backstage: Improper input validation in cloud storage URL readers npm · @backstage/backend-defaults 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 high7.6 CVE-2026-106492 Backstage: Improper preservation of access restrictions during service credential delegation npm · @backstage/backend-defaults 46 days ago medium6.4 CVE-2026-106491 Backstage is an open framework for building developer portals. npm · @backstage/plugin-proxy-backend 46 days ago medium6.5 CVE-2026-106490 Backstage: Improper input validation in TechDocs static content requests npm · @backstage/plugin-techdocs-backend 46 days ago medium6.5 CVE-2026-106489 Backstage: Improper authorization enforcement for TechDocs static content npm · @backstage/plugin-techdocs-backend 46 days ago high8.1 CVE-2026-106488 Backstage is an open framework for building developer portals. npm · @backstage/plugin-auth-backend-module-oidc-provider 46 days ago

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.