NetSight

Security Dashboard

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

Reset
50 matching advisories · page 1 of 2Index updated just now · Subscribe · RSS
SeverityIDTitleAffectedAge
high8.7 CVE-2026-49119 Gradio before 6.16.0 contain a path traversal vulnerability in the FileExplorer component's preprocess() method that allows unauthenticated attackers to escape… pip · gradio 2026-07-01 low2.5 CVE-2026-10783 Gradio: Audio cache key ignores metadata when saving numpy audio outputs pip · gradio 2026-06-04 high7.6 CVE-2026-48545 Gradio before version 6.15.0 contains a cookie injection vulnerability that allows remote attackers to perform cross-Space session fixation by exploiting a sha… pip · gradio 2026-05-27 high8.2 CVE-2026-28416 Gradio has SSRF via Malicious `proxy_url` Injection in `gr.load()` Config Processing pip · gradio 2026-02-27 medium4.3 CVE-2026-28415 Gradio has an Open Redirect in its OAuth Flow pip · gradio 2026-02-27 high7.5 CVE-2026-28414 Gradio is Vulnerable to Absolute Path Traversal on Windows with Python 3.13+ pip · gradio 2026-02-27 low CVE-2026-27167 Gradio: Mocked OAuth Login Exposes Server Credentials and Uses Hardcoded Session Secret pip · gradio 2026-02-27 medium5.3 CVE-2025-48889 Gradio Allows Unauthorized File Copy via Path Manipulation pip · gradio 2025-05-29 high7.5 CVE-2025-0187 A Denial of Service (DoS) vulnerability was discovered in the file upload feature of gradio-app/gradio version 0.39.1. gradio_project · gradio 2025-03-20 medium5.4 CVE-2024-8021 Gradio Vulnerable to Open Redirect pip · gradio 2025-03-20 high8.2 CVE-2024-10648 Gradio Vulnerable to Arbitrary File Deletion pip · gradio 2025-03-20 high7.5 CVE-2024-10624 Gradio Vulnerable to Denial of Service (DoS) via Crafted HTTP Request pip · gradio 2025-03-20 high7.5 CVE-2024-10569 Gradio Vulnerable to Denial of Service (DoS) via Crafted Zip Bomb pip · gradio 2025-03-20 critical9.1 CVE-2025-23042 Gradio Blocked Path ACL Bypass Vulnerability pip · gradio 2025-01-14 medium6.9 CVE-2024-51751 Gradio vulnerable to arbitrary file read with File and UploadButton components pip · gradio 2024-11-06 medium6.5 CVE-2024-48052 gradio Server Side Request Forgery vulnerability pip · gradio 2024-11-04 medium5.4 CVE-2024-47872 Gradio has an XSS on every Gradio server via upload of HTML files, JS files, or SVG files pip · gradio 2024-10-10 critical9.1 CVE-2024-47871 Gradio uses insecure communication between the FRP client and server pip · gradio 2024-10-10 high7.0 CVE-2024-47870 Gradio has a race condition in update_root_in_config may redirect user traffic pip · gradio 2024-10-10 medium3.7 CVE-2024-47869 Gradio performs a non-constant-time comparison when comparing hashes pip · gradio 2024-10-10 high7.5 CVE-2024-47868 Gradio has several components with post-process steps allow arbitrary file leaks pip · gradio 2024-10-10 high7.5 CVE-2024-47867 Gradio lacks integrity checking on the downloaded FRP client pip · gradio 2024-10-10 medium4.3 CVE-2024-47168 In Gradio, the `enable_monitoring` flag set to `False` does not disable monitoring pip · gradio 2024-10-10 critical9.8 CVE-2024-47167 Gradio vulnerable to SSRF in the path parameter of /queue/join pip · gradio 2024-10-10 medium5.3 CVE-2024-47166 Gradio has a one-level read path traversal in `/custom_component` pip · gradio 2024-10-10 medium5.4 CVE-2024-47165 Gradio's CORS origin validation accepts the null origin pip · gradio 2024-10-10 medium6.5 CVE-2024-47164 Gradio's `is_in_or_equal` function may be bypassed pip · gradio 2024-10-10 high8.8 CVE-2024-47084 Gradios's CORS origin validation is not performed when the request has a cookie pip · gradio 2024-10-10 critical9.8 CVE-2024-39236 Withdrawn Advisory: Gradio was discovered to contain a code injection vulnerability via the component /gradio/component_meta.py pip · Gradio 2024-07-01 medium5.4 CVE-2024-4940 Open redirect in gradio pip · gradio 2024-06-22

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.