NetSight

Security Dashboard

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

Reset
168 matching advisories · page 2 of 6Index updated just now · Subscribe · RSS
SeverityIDTitleAffectedAge
medium5.4 CVE-2026-1312 Django has an SQL Injection issue pip · Django 2026-02-03 high8.1 CVE-2026-1287 Django has an SQL Injection issue pip · Django 2026-02-03 high7.5 CVE-2026-1285 Django has Inefficient Algorithmic Complexity pip · Django 2026-02-03 high8.1 CVE-2026-1207 Django has an SQL Injection issue pip · Django 2026-02-03 high7.5 CVE-2025-14550 Django has Inefficient Algorithmic Complexity pip · Django 2026-02-03 medium5.3 CVE-2025-13473 Django has Observable Timing Discrepancy pip · Django 2026-02-03 high7.5 CVE-2025-64460 Django is vulnerable to DoS via XML serializer text extraction pip · Django 2025-12-02 medium4.3 CVE-2025-13372 Django is vulnerable to SQL injection in column aliases pip · Django 2025-12-02 critical9.1 CVE-2025-64459 Django vulnerable to SQL injection via _connector keyword argument in QuerySet and Q objects. pip · django 2025-11-05 high7.5 CVE-2025-64458 Django has a denial-of-service vulnerability in HttpResponseRedirect and HttpResponsePermanentRedirect on Windows pip · django 2025-11-05 low3.1 CVE-2025-59682 Django vulnerable to partial directory traversal via archives pip · django 2025-10-01 high7.1 CVE-2025-59681 An issue was discovered in Django 4.2 before 4.2.25, 5.1 before 5.1.13, and 5.2 before 5.2.7. pip · django 2025-10-01 high7.1 CVE-2025-57833 Django is subject to SQL injection through its column aliases pip · Django 2025-09-03 medium4.0 CVE-2025-48432 Django Improper Output Neutralization for Logs vulnerability pip · Django 2025-06-05 medium5.3 CVE-2025-32873 Django has a denial-of-service possibility in strip_tags() pip · Django 2025-05-08 medium5.8 CVE-2025-27556 Django Potential Denial of Service (DoS) on Windows pip · Django 2025-04-02 medium5.0 CVE-2025-26699 Django Vulnerable to Allocation of Resources Without Limits or Throttling pip · Django 2025-03-06 medium5.8 CVE-2024-56374 Django has a potential denial-of-service vulnerability in IPv6 validation pip · Django 2025-01-14 critical9.8 CVE-2024-53908 Django SQL injection in HasKey(lhs, rhs) on Oracle pip · Django, pip · django 2024-12-06 high7.5 CVE-2024-53907 Django denial-of-service in django.utils.html.strip_tags() pip · Django, pip · django 2024-12-06 medium3.7 CVE-2024-45231 Django allows enumeration of user e-mail addresses pip · Django 2024-10-08 high7.5 CVE-2024-45230 Django vulnerable to denial-of-service attack via the urlize() and urlizetrunc() template filters pip · Django 2024-10-08 critical9.1 CVE-2024-42005 Django SQL injection vulnerability pip · Django 2024-08-07 high7.5 CVE-2024-41991 Django vulnerable to denial-of-service attack pip · Django 2024-08-07 high7.5 CVE-2024-41990 Django vulnerable to a denial-of-service attack pip · Django 2024-08-07 high7.5 CVE-2024-41989 Django memory consumption vulnerability pip · Django 2024-08-07 high7.5 CVE-2024-39614 Django vulnerable to Denial of Service pip · Django 2024-07-10 high7.5 CVE-2024-39330 Django Path Traversal vulnerability pip · Django 2024-07-10 medium5.3 CVE-2024-39329 Django vulnerable to user enumeration attack pip · Django 2024-07-10 high7.5 CVE-2024-38875 Django vulnerable to Denial of Service pip · Django 2024-07-10

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.