NetSight

Security Dashboard

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

Reset
42 matching advisories · page 1 of 2Index updated 2 minutes ago · Subscribe · RSS
SeverityIDTitleAffectedAge
high8.0 CVE-2025-48384 Git Link Following VulnerabilityExploited git-scm · git, debian · debian_linux, apple · xcode 2025-07-08 critical GHSA-mpw9-5jq3-72q8 Malware in git-scm.comMalware npm · git-scm.com 2025-02-03 high7.3 CVE-2024-32465 Git is a revision control system. git-scm · git, fedoraproject · fedora, debian · debian_linux 2024-05-14 low3.9 CVE-2024-32021 Git is a revision control system. git-scm · git, fedoraproject · fedora, debian · debian_linux 2024-05-14 low3.9 CVE-2024-32020 Git is a revision control system. git-scm · git, fedoraproject · fedora 2024-05-14 high8.1 CVE-2024-32004 Git is a revision control system. git-scm · git, fedoraproject · fedora, debian · debian_linux 2024-05-14 high7.5 CVE-2023-25652 Git is a revision control system. git-scm · git, fedoraproject · fedora 2023-04-25 high7.0 CVE-2023-29007 Git is a revision control system. git-scm · git, fedoraproject · fedora, git · git +1 2023-04-25 medium6.2 CVE-2023-23946 Git, a revision control system, is vulnerable to path traversal prior to versions 2.39.2, 2.38.4, 2.37.6, 2.36.5, 2.35.7, 2.34.7, 2.33.7, 2.32.6, 2.31.7, and 2… git-scm · git 2023-02-14 medium5.5 CVE-2023-22490 Git is a revision control system. git-scm · git 2023-02-14 critical9.8 CVE-2022-41903 Git is distributed revision control system. git-scm · git 2023-01-17 critical9.8 CVE-2022-23521 Git is distributed revision control system. git-scm · git 2023-01-17 high8.6 CVE-2022-41953 Git GUI is a convenient graphical tool that comes with Git for Windows. git-scm · git 2023-01-17 high8.5 CVE-2022-39260 Git is an open source, scalable, distributed revision control system. git-scm · git, fedoraproject · fedora, apple · xcode +1 2022-10-19 medium5.5 CVE-2022-39253 Git is an open source, scalable, distributed revision control system. git-scm · git, fedoraproject · fedora, apple · xcode +1 2022-10-19 high7.8 CVE-2022-29187 Git is a distributed revision control system. git-scm · git, fedoraproject · fedora, apple · xcode +1 2022-07-12 medium6.0 CVE-2022-24765 Git for Windows is a fork of Git containing Windows-specific patches. git-scm · git, fedoraproject · fedora, apple · xcode +1 2022-04-12 high7.5 CVE-2022-24975 The --mirror documentation for Git through 2.35.1 does not mention the availability of deleted content, aka the "GitBleed" issue. git-scm · git 2022-02-11 high7.5 CVE-2021-40330 git_connect_git in connect.c in Git before 2.30.1 allows a repository path to contain a newline character, which may result in unexpected cross-protocol reques… git-scm · git, debian · debian_linux 2021-08-31 high8.0 CVE-2021-21300 Git is an open-source distributed revision control system. git-scm · git, fedoraproject · fedora, apple · xcode +1 2021-03-09 medium4.0 CVE-2020-11008 Affected versions of Git have a vulnerability whereby Git can be tricked into sending private credentials to a host controlled by an attacker. git-scm · git, canonical · ubuntu_linux, debian · debian_linux +1 2020-04-21 critical9.3 CVE-2020-5260 Affected versions of Git have a vulnerability whereby Git can be tricked into sending private credentials to a host controlled by an attacker. git · git, git-scm · git, canonical · ubuntu_linux +3 2020-04-14 critical9.8 CVE-2014-9390 JGit Improper Input Validation vulnerability maven · org.eclipse.jgit:org.eclipse.jgit, pip · mercurial 2020-02-12 critical9.8 CVE-2019-1353 An issue was found in Git before v2.24.1, v2.23.1, v2.22.2, v2.21.1, v2.20.2, v2.19.3, v2.18.2, v2.17.3, v2.16.6, v2.15.4, and v2.14.6. git-scm · git, opensuse · leap 2020-01-24 low3.3 CVE-2019-1348 An issue was found in Git before v2.24.1, v2.23.1, v2.22.2, v2.21.1, v2.20.2, v2.19.3, v2.18.2, v2.17.3, v2.16.6, v2.15.4, and v2.14.6. git-scm · git, opensuse · leap 2020-01-24 high8.8 CVE-2019-1387 An issue was found in Git before v2.24.1, v2.23.1, v2.22.2, v2.21.1, v2.20.2, v2.19.3, v2.18.2, v2.17.3, v2.16.6, v2.15.4, and v2.14.6. git-scm · git 2019-12-18 high7.8 CVE-2019-19604 Arbitrary command execution is possible in Git before 2.20.2, 2.21.x before 2.21.1, 2.22.x before 2.22.2, 2.23.x before 2.23.1, and 2.24.x before 2.24.1 becaus… git-scm · git, debian · debian_linux, fedoraproject · fedora +1 2019-12-11 critical9.8 CVE-2018-19486 Git before 2.19.2 on Linux and UNIX executes commands from the current working directory (as if '.' were at the end of $PATH) in certain cases involving the ru… git-scm · git, canonical · ubuntu_linux 2018-11-23 critical9.8 CVE-2018-17456 Git before 2.14.5, 2.15.x before 2.15.3, 2.16.x before 2.16.5, 2.17.x before 2.17.2, 2.18.x before 2.18.1, and 2.19.x before 2.19.1 allows remote code executio… git-scm · git, redhat · ansible_tower, redhat · enterprise_linux +8 2018-10-06 high7.8 CVE-2018-11235 In Git before 2.13.7, 2.14.x before 2.14.4, 2.15.x before 2.15.2, 2.16.x before 2.16.4, and 2.17.x before 2.17.1, remote code execution can occur. debian · debian_linux, canonical · ubuntu_linux, redhat · enterprise_linux +6 2018-05-30

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.