NetSight

Security Dashboard

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

Reset
1,737 matching advisories · page 14 of 58Index updated just now · Subscribe · RSS
SeverityIDTitleAffectedAge
high8.8 CVE-2026-73485 Flowise before 3.1.3 contains a code injection vulnerability in the Airtable Agent node that allows unauthenticated attackers to execute arbitrary Python code … flowiseai · flowise 2026-08-13 high8.1 CVE-2026-73484 Flowise before 3.1.3 contains a sandbox escape vulnerability in pythonCodeValidator.ts that fails to block native Pandas DataFrame methods like to_csv, to_json… flowiseai · flowise 2026-08-13 high8.1 CVE-2026-19594 Insufficient input sanitization in Snowflake Python API (`snowflake.core`) versions prior to 1.13.0 allowed confused-deputy privilege escalation through two re… Snowflake Python API (`snowflake.core`) 2026-08-12 medium4.4 CVE-2026-73036 Bash-it 3.2.0 contains a terminal escape sequence injection vulnerability in the barbuk theme's Python virtualenv prompt segment that allows local attackers to… Bash-it · Bash-it 2026-08-11 high7.8 CVE-2026-54981 Inclusion of functionality from untrusted control sphere in Visual Studio Code - Python extension allows an unauthorized attacker to bypass a security feature … microsoft · python, Microsoft · Python extension for Visual Studio Code 2026-08-11 low2.4 CVE-2026-18503 Attacker-controlled CSV samples can trigger super-linear regular-expression work during dialect sniffing and consume significant CPU when applications pass unb… Python Software Foundation · CPython 2026-08-10 high8.8 CVE-2026-76220 GitPython before 3.1.58 contains a command execution vulnerability in the check_unsafe_options guard that can be bypassed by combining a single-character kwarg… pip · GitPython 2026-08-07 high8.8 GHSA-jm78-9fvv-mhgr GitPython: git-config OPTION-name injection via =/#/whitespace bypasses name validator, enabling forged core.sshCommand/hooksPath (RCE) pip · GitPython 2026-08-07 high8.2 CVE-2026-76222 GitPython before 3.1.58 fails to validate submodule names from .gitmodules files, allowing attackers to create Git repositories at arbitrary filesystem paths o… pip · GitPython 2026-08-07 medium6.5 CVE-2026-76217 GitPython versions before 3.1.58 fail to validate options passed to git rm and git checkout commands in IndexFile.remove() and Head.checkout(). pip · GitPython 2026-08-07 high7.5 CVE-2026-76218 GitPython before 3.1.58 contains a remote code execution vulnerability in Repo.init that forwards unsafe git options without validation. pip · GitPython 2026-08-07 high8.1 CVE-2026-76219 GitPython versions before 3.1.58 contain an arbitrary file overwrite vulnerability in IndexFile.from_tree, IndexFile.reset, and IndexFile.merge_tree methods th… pip · GitPython 2026-08-07 medium5.3 CVE-2026-71554 h2 is a pure-Python implementation of a HTTP/2 protocol stack. pip · h2 2026-08-06 high7.4 CVE-2026-8470 IBM Langflow OSS 1.0.0 through 1.10.3, 1.0.0 through 1.10.3, 1.0.0 through 1.10.3, and 1.0.0 through 1.10.3 use Python's non-cryptographic random module for ge… langflow · langflow 2026-08-05 high8.8 CVE-2026-17632 IBM Langflow OSS 1.0.0 through 1.10.3 could allow a remote authenticated attacker to execute arbitrary code due to improper validation of Python code during AS… langflow · langflow 2026-08-05 high7.2 CVE-2026-71284 Fledge's backup-restore upload handler, upload_backup (python/fledge/services/core/api/backup_restore.py), takes the first extracted tar member's filename (tar… 2026-08-05 medium4.9 CVE-2026-71283 Fledge's backup-restore upload handler, upload_backup (python/fledge/services/core/api/backup_restore.py), calls tarfile.extractall(temp_path) on an admin-uplo… 2026-08-05 critical9.8 CVE-2026-69264 Prior to 3.1.3, Flowise CSVAgent interpolates an attacker-controlled segment of the csvFile data URI directly into a Python source-code template that is then e… npm · flowise, npm · flowise-components 2026-08-04 medium6.9 CVE-2026-69248 cryptography is a package designed to expose cryptographic primitives and recipes to Python developers. pip · cryptography 2026-08-03 high8.7 CVE-2026-69249 python-cryptography is a package designed to expose cryptographic primitives and recipes to Python developers. pip · cryptography 2026-08-03 medium5.3 CVE-2026-69243 AIOHTTP is an asynchronous HTTP client/server framework for asyncio and Python. pip · aiohttp 2026-08-03 medium5.4 GHSA-p538-c434-8v24 GitPython: Arbitrary file truncation via git rev-list --output argument injection in unguarded Commit.count pip · GitPython 2026-08-03 medium6.5 GHSA-539m-9xh6-q6rr GitPython: Incomplete unsafe_git_archive_options denylist omits --add-file / --add-virtual-file, enabling arbitrary file read via Repo.archive() pip · GitPython 2026-08-03 high8.1 GHSA-3f7w-8rr8-f37f GitPython: Unguarded git option forwarding in IndexFile.checkout() and TagReference.create() enables arbitrary file overwrite and arbitrary file read pip · GitPython 2026-08-03 high7.0 GHSA-9xx9-hw38-h2w9 Duplicate Advisory: GitPython: git-config section-name injection enables arbitrary config directives (core.sshCommand RCE) pip · gitpython 2026-08-03 high8.8 GHSA-6r2r-ww24-7h52 Duplicate Advisory: GitPython: Command Injection via git long-option prefix abbreviation bypass of CVE-2026-42215 blocklist pip · gitpython 2026-08-01 high7.5 GHSA-m4f3-g4cq-hqrx Duplicate Advisory: GitPython: Environment-variable exfiltration via os.path.expandvars() on Repo.clone_from() URL pip · gitpython 2026-08-01 high8.4 GHSA-4vpg-pfj8-m33q Duplicate Advisory: GitPython: command injection via unguarded Git options in `Repo.archive()`, `git.ls_remote()`, and arbitrary file overwrite via `Repo.iter_commits()` / `Repo.blame()` pip · gitpython 2026-08-01 critical9.8 GHSA-cw2r-r7mw-j3hc Duplicate Advisory: GitPython unsafe clone option gate bypass through joined short options pip · gitpython 2026-08-01 high7.0 CVE-2026-67326 GitPython before 3.1.50 fails to validate newline characters in the section parameter of config_writer(), allowing attackers to inject arbitrary section header… gitpython_project · gitpython 2026-08-01

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.