NetSight

Security Dashboard

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

Reset
95 matching advisories · page 2 of 4Index updated 3 minutes ago · Subscribe · RSS
SeverityIDTitleAffectedAge
critical GHSA-v46q-wq68-6mm5 Malware in @gitlab-test/npm-v10Malware npm · @gitlab-test/npm-v10 2025-10-29 critical9.6 CVE-2024-7102 An issue was discovered in GitLab CE/EE affecting all versions starting from 16.4 prior to 17.5.0 which allows an attacker to trigger a pipeline as another use… gitlab · gitlab 2025-02-13 critical9.6 CVE-2024-9164 An issue was discovered in GitLab EE affecting all versions starting from 12.5 prior to 17.2.9, starting from 17.3, prior to 17.3.5, and starting from 17.4 pri… gitlab · gitlab 2024-10-11 critical9.9 CVE-2024-6678 An issue was discovered in GitLab CE/EE affecting all versions starting from 8.14 prior to 17.1.7, starting from 17.2 prior to 17.2.5, and starting from 17.3 p… gitlab · gitlab 2024-09-12 critical10.0 CVE-2024-45409 The Ruby SAML library vulnerable to a SAML authentication bypass via Incorrect XPath selector rubygems · ruby-saml 2024-09-10 critical9.6 CVE-2024-6385 An issue was discovered in GitLab CE/EE affecting all versions starting from 15.8 prior to 16.11.6, starting from 17.0 prior to 17.0.4, and starting from 17.1 … gitlab · gitlab 2024-07-11 critical9.6 CVE-2024-5655 An issue was discovered in GitLab CE/EE affecting all versions starting from 15.8 prior to 16.11.5, starting from 17.0 prior to 17.0.3, and starting from 17.1 … gitlab · gitlab 2024-06-27 critical9.9 CVE-2024-0402 An issue has been discovered in GitLab CE/EE affecting all versions from 16.0 prior to 16.6.6, 16.7 prior to 16.7.4, and 16.8 prior to 16.8.1 which allows an a… gitlab · gitlab 2024-01-26 critical10.0 CVE-2023-7028 GitLab Community and Enterprise Editions Improper Access Control VulnerabilityExploited gitlab · gitlab 2024-01-12 critical GHSA-fp25-pgmj-46qw Malware in gatsby-starter-gitlabMalware npm · gatsby-starter-gitlab 2023-11-06 critical GHSA-j3j5-6vwf-m387 Malware in gitlabhookMalware npm · gitlabhook 2023-06-19 critical10.0 CVE-2023-2825 An issue has been discovered in GitLab CE/EE affecting only version 16.0.0. gitlab · gitlab 2023-05-26 critical9.6 CVE-2023-2478 An issue has been discovered in GitLab CE/EE affecting all versions starting from 15.4 before 15.9.7, all versions starting from 15.10 before 15.10.6, all vers… gitlab · gitlab 2023-05-08 critical9.8 CVE-2018-17452 An issue was discovered in GitLab Community and Enterprise Edition before 11.1.7, 11.2.x before 11.2.4, and 11.3.x before 11.3.1. gitlab · gitlab 2023-04-15 critical9.3 CVE-2022-3572 A cross-site scripting issue has been discovered in GitLab CE/EE affecting all versions from 13.5 prior to 15.3.5, 15.4 prior to 15.4.4, and 15.5 prior to 15.5… gitlab · gitlab 2023-01-26 critical9.9 CVE-2022-2992 A vulnerability in GitLab CE/EE affecting all versions from 11.10 prior to 15.1.6, 15.2 to 15.2.4, 15.3 to 15.3.2 allows an authenticated user to achieve remot… gitlab · gitlab 2022-10-17 critical9.9 CVE-2022-2884 A vulnerability in GitLab CE/EE affecting all versions from 11.3.4 prior to 15.1.5, 15.2 to 15.2.3, 15.3 to 15.3 to 15.3.1 allows an an authenticated user to a… gitlab · gitlab 2022-10-17 critical9.9 CVE-2022-2185 A critical issue has been discovered in GitLab affecting all versions starting from 14.0 prior to 14.10.5, 15.0 prior to 15.0.4, and 15.1 prior to 15.1.1 where… gitlab · gitlab 2022-07-01 critical GHSA-xfqj-fr54-78mc Malware in gitlab-linter-cliMalware npm · gitlab-linter-cli 2022-06-20 critical9.9 CVE-2022-1680 An account takeover issue has been discovered in GitLab EE affecting all versions starting from 11.10 before 14.9.5, all versions starting from 14.10 before 14… gitlab · gitlab 2022-06-06 critical9.8 CVE-2022-0272 XML External Entity Reference in detekt maven · io.gitlab.arturbosch.detekt:detekt-core 2022-04-21 critical9.1 CVE-2022-1162 A hardcoded password was set for accounts registered using an OmniAuth provider (e.g. gitlab · gitlab 2022-04-04 critical10.0 CVE-2022-0735 An issue has been discovered in GitLab CE/EE affecting all versions starting from 12.10 before 14.6.5, all versions starting from 14.7 before 14.7.4, all versi… gitlab · gitlab 2022-03-28 critical9.8 CVE-2022-24331 In JetBrains TeamCity before 2021.1.4, GitLab authentication impersonation was possible. jetbrains · teamcity 2022-02-25 critical9.6 CVE-2021-22234 An issue has been discovered in GitLab CE/EE affecting all versions starting from 13.11 before 13.11.7, all versions starting from 13.12 before 13.12.8, and al… gitlab · gitlab 2021-08-05 critical10.0 CVE-2021-22205 GitLab Community and Enterprise Editions Remote Code Execution VulnerabilityExploited gitlab · gitlab 2021-04-23 critical9.6 CVE-2021-22201 An issue has been discovered in GitLab CE/EE affecting all versions starting from 13.9. gitlab · gitlab 2021-04-02 critical9.9 CVE-2021-22192 An issue has been discovered in GitLab CE/EE affecting all versions starting from 13.2 allowing unauthorized authenticated users to execute arbitrary code on t… gitlab · gitlab 2021-03-24 critical9.1 CVE-2020-13347 A command injection vulnerability was discovered in Gitlab runner versions prior to 13.2.4, 13.3.2 and 13.4.1. gitlab · gitlab 2020-10-07 critical10.0 CVE-2020-5415 Concourse, versions prior to 6.3.1 and 6.4.1, in installations which use the GitLab auth connector, is vulnerable to identity spoofing by way of configuring a … go · github.com/concourse/concourse, go · github.com/concourse/dex 2020-08-12

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.