NetSight

Security Dashboard

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

Reset
95 matching advisories · page 1 of 4Index updated just now · Subscribe · RSS
SeverityIDTitleAffectedAge
critical10.0 CVE-2026-110264 An issue has been discovered in GitLab CE/EE affecting all versions from 7.0 before 18.11.13, 19.0 before 19.0.10, 19.1 before 19.1.9, 19.2 before 19.2.9, 19.3… gitlab · gitlab 31 days ago critical10.0 CVE-2026-97229 GitLab has remediated an issue in GitLab CE/EE affecting all versions from 19.2 before 19.2.8, 19...Exploited gitlab · gitlab, ruby-lang · ruby 40 days ago critical9.9 CVE-2026-90970 GitLab has remediated a vulnerability in the GitLab AI Gateway component affecting all versions of the AI Gateway from 18.1.6 before 19.2.4, 19.3 before 19.3.2… AI Gateway from, 19.3, 19.4 50 days ago critical9.9 CVE-2026-93577 GitLab has remediated an issue in GitLab CE/EE affecting all versions from 19.2 before 19.2.7, 19.3 before 19.3.3, and 19.4 before 19.4.1 that under certain co… gitlab · gitlab 59 days ago critical9.9 CVE-2026-89078 GitLab has remediated an issue in GitLab CE/EE affecting all versions from 19.2 before 19.2.7, 19.3 before 19.3.3, and 19.4 before 19.4.1 that under certain co… gitlab · gitlab 59 days ago critical9.8 CVE-2026-61560 @zereight/mcp-gitlab: Unauthenticated arbitrary file read via `upload_markdown` enables PAT exfiltration and full account takeover npm · @zereight/mcp-gitlab 2026-09-15 critical9.6 CVE-2026-61559 `@zereight/mcp-gitlab` is a Model Context Protocol server for GitLab. npm · @zereight/mcp-gitlab 2026-09-15 critical9.6 CVE-2026-61568 @zereight/mcp-gitlab: DNS rebinding reaches local Streamable HTTP MCP transport npm · @zereight/mcp-gitlab 2026-09-15 critical GHSA-cx2p-rcq4-2gwr Malicious code in gitlab-accountid (npm)Malware npm · gitlab-accountid 2026-09-13 critical9.9 CVE-2026-87719 GitLab has remediated an issue in GitLab EE affecting all versions from 18.3 before 18.11.12, 19.0 before 19.0.9, 19.1 before 19.1.8, 19.2 before 19.2.6, and 1… gitlab · gitlab 2026-09-12 critical10.0 CVE-2026-85706 GitLab Community Edition and Enterprise Edition Path Traversal VulnerabilityExploited GitLab · GitLab, gitlab · gitlab 2026-09-11 critical9.4 CVE-2026-19478 GitLab has remediated an issue in GitLab CE/EE affecting all versions from 18.2 before 18.11.11, 19.0 before 19.0.8, 19.1 before 19.1.6, and 19.2 before 19.2.4… gitlab · gitlab 2026-08-17 critical GHSA-j9fh-75xr-wfjx Malware in delivery-ci-update-gitlabMalware npm · delivery-ci-update-gitlab 2026-08-05 critical GHSA-m4w6-4923-8gc3 Malware in tinkoff-boxy-gitlab-labelsMalware npm · tinkoff-boxy-gitlab-labels 2026-08-05 critical GHSA-ffm2-vc93-55ph Malicious code in @mlspace/env-gitlab (npm)Malware npm · @mlspace/env-gitlab 2026-07-27 critical GHSA-84vc-rx5g-gvqr Malicious code in @immobiliarelabs/backstage-plugin-gitlab-backend (npm)Malware npm · @immobiliarelabs/backstage-plugin-gitlab-backend, npm · @immobiliarelabs/backstage-plugin-gitlab-backend, npm · @immobiliarelabs/backstage-plugin-gitlab-backend +2 2026-07-27 critical GHSA-93qj-59x5-pqcv Malicious code in @immobiliarelabs/backstage-plugin-gitlab (npm)Malware npm · @immobiliarelabs/backstage-plugin-gitlab, npm · @immobiliarelabs/backstage-plugin-gitlab, npm · @immobiliarelabs/backstage-plugin-gitlab +4 2026-07-27 critical GHSA-r4r5-rj2h-xfvg Malware in @immobiliarelabs/backstage-plugin-gitlabMalware npm · @immobiliarelabs/backstage-plugin-gitlab, npm · @immobiliarelabs/backstage-plugin-gitlab, npm · @immobiliarelabs/backstage-plugin-gitlab +4 2026-07-27 critical GHSA-rf84-c9g3-j9w6 Malicious code in kwai-gitlab (RubyGems)Malware rubygems · kwai-gitlab 2026-07-18 critical GHSA-9953-358v-57cx Malicious code in gitlab-glfm-markdown (RubyGems)Malware rubygems · gitlab-glfm-markdown 2026-07-18 critical GHSA-fpg3-pj6c-r8g2 Malicious code in gitlab-orchestrator (RubyGems)Malware rubygems · gitlab-orchestrator, rubygems · gitlab-orchestrator 2026-07-18 critical GHSA-wggv-fp48-h6pm Malicious code in gemnasium-gitlab-service (RubyGems)Malware rubygems · gemnasium-gitlab-service, rubygems · gemnasium-gitlab-service, rubygems · gemnasium-gitlab-service +13 2026-07-18 critical9.2 CVE-2026-44895 @yoda.digital/gitlab-mcp-server's SSE transport has no authentication and wildcard CORS, exposing all 86 GitLab tools npm · @yoda.digital/gitlab-mcp-server 2026-05-09 critical9.9 CVE-2026-1868 GitLab has remediated a vulnerability in the Duo Workflow Service component of GitLab AI Gateway affecting all versions of the AI Gateway from 18.1.6, 18.2.6, … 2026-02-09 critical GHSA-5ccp-9vgw-jc6q Malware in @gitlab-lsp/pkg-1Malware npm · @gitlab-lsp/pkg-1 2025-10-29 critical GHSA-m8h7-p99w-5443 Malware in @gitlab-lsp/pkg-2Malware npm · @gitlab-lsp/pkg-2 2025-10-29 critical GHSA-jf26-fhf9-jxfg Malware in @gitlab-lsp/workflow-apiMalware npm · @gitlab-lsp/workflow-api 2025-10-29 critical GHSA-7rgx-56c7-wpg8 Malware in @gitlab-test/yarn-v4Malware npm · @gitlab-test/yarn-v4 2025-10-29 critical GHSA-36w6-qwwg-gx4w Malware in @gitlab-test/pnpm-v9Malware npm · @gitlab-test/pnpm-v9 2025-10-29 critical GHSA-4gc6-vwp5-9rjg Malware in @gitlab-test/bun-v1Malware npm · @gitlab-test/bun-v1 2025-10-29

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.