NetSight

Security Dashboard

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

Reset
53 matching advisories · page 2 of 2Index updated 14 minutes ago · Subscribe · RSS
SeverityIDTitleAffectedAge
medium5.4 CVE-2025-11844 Hugging Face Smolagents XPath injection vulnerability in the search_item_ctrl_f function pip · smolagents 2025-10-22 high7.5 CVE-2025-6921 Hugging Face Transformers vulnerable to Regular Expression Denial of Service (ReDoS) in the AdamWeightDecay optimizer pip · transformers 2025-09-23 medium6.3 CVE-2025-10772 A vulnerability was identified in huggingface LeRobot up to 0.3.3. huggingface LeRobot 2025-09-22 medium5.3 CVE-2025-6051 Hugging Face Transformers library has Regular Expression Denial of Service pip · transformers 2025-09-14 high7.5 CVE-2025-6638 Hugging Face Transformers is vulnerable to ReDoS through its MarianTokenizer pip · transformers 2025-09-12 medium5.3 CVE-2025-5197 Hugging Face Transformers Regular Expression Denial of Service (ReDoS) vulnerability pip · transformers 2025-08-06 critical9.9 CVE-2025-5120 smolagents has Sandbox Escape Vulnerability in the local_python_executor.py Module pip · smolagents 2025-07-27 medium5.3 CVE-2025-3933 Transformers is vulnerable to ReDoS attack through its DonutProcessor class pip · transformers 2025-07-11 low3.5 CVE-2025-3777 Hugging Face Transformers versions up to 4.49.0 are affected by an improper input validation vulnerability in the `image_utils.py` file. pip · transformers 2025-07-07 medium5.3 CVE-2025-3264 Transformers vulnerable to ReDoS attack through its get_imports() function pip · transformers 2025-07-07 medium5.3 CVE-2025-3263 Transformers's ReDoS vulnerability in get_configuration_file can lead to catastrophic backtracking pip · transformers 2025-07-07 high7.5 CVE-2025-3262 Transformers vulnerable to ReDoS attack through its SETTING_RE variable pip · transformers 2025-07-07 high7.5 CVE-2025-2099 Hugging Face Transformers Regular Expression Denial of Service pip · transformers 2025-05-19 medium4.3 CVE-2025-1194 Transformers Regular Expression Denial of Service (ReDoS) vulnerability pip · transformers 2025-04-29 high7.5 CVE-2024-12720 Transformers Regular Expression Denial of Service (ReDoS) vulnerability pip · transformers 2025-03-20 high8.8 CVE-2024-11394 Deserialization of Untrusted Data in Hugging Face Transformers pip · transformers 2024-11-22 high8.8 CVE-2024-11393 Deserialization of Untrusted Data in Hugging Face Transformers pip · transformers 2024-11-22 high7.5 CVE-2024-11392 Deserialization of Untrusted Data in Hugging Face Transformers pip · transformers 2024-11-22 medium4.4 CVE-2024-3924 code injection vulnerability exists in the huggingface/text-generation-inference repository pip · text-generation 2024-05-30 critical9.6 CVE-2024-3568 The huggingface/transformers library is vulnerable to arbitrary code execution through deserialization of untrusted data within the `load_repo_checkpoint()` fu… pip · transformers 2024-04-10 high7.8 CVE-2023-7018 transformers has a Deserialization of Untrusted Data vulnerability pip · transformers 2023-12-20 critical9.0 CVE-2023-6730 transformers has a Deserialization of Untrusted Data vulnerability pip · transformers 2023-12-19 medium4.7 CVE-2023-2800 transformers has Insecure Temporary File pip · transformers 2023-05-18

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.