NetSight

Security Dashboard

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

Reset
168 matching advisories · page 1 of 6Index updated 2 minutes ago · Subscribe · RSS
SeverityIDTitleAffectedAge
medium6.9 CVE-2026-114582 An issue was discovered in Django 6.1 before 6.1.3, 6.0 before 6.0.10, and 5.2 before 5.2.19. ... djangoproject · Django 18 days ago low2.1 CVE-2026-113733 An issue was discovered in Django 6.1 before 6.1.3 and 6.0 before 6.0.10. The `django.contrib... djangoproject · Django 18 days ago low2.3 CVE-2026-113593 An issue was discovered in Django 6.1 before 6.1.3, 6.0 before 6.0.10, and 5.2 before 5.2.19. The... djangoproject · Django 18 days ago medium6.9 CVE-2026-111362 An issue was discovered in Django 6.1 before 6.1.3, 6.0 before 6.0.10, and 5.2 before 5.2.19. ... djangoproject · Django 18 days ago medium6.9 CVE-2026-111211 An issue was discovered in Django 6.1 before 6.1.3, 6.0 before 6.0.10, and 5.2 before 5.2.19. ... djangoproject · Django 18 days ago medium6.9 CVE-2026-108147 An issue was discovered in Django 6.1 before 6.1.3, 6.0.4 before 6.0.10, and 5.2.13 before 5.2.19... djangoproject · Django 18 days ago medium6.1 CVE-2026-15920 An issue was discovered in Django 5.2 before 5.2.17 and 6.0 before 6.0.8. djangoproject · django 2026-08-04 medium5.3 CVE-2026-15830 Django GeoDjango vulnerable to denial of service through deeply nested geometry collections pip · django 2026-08-04 medium5.3 CVE-2026-15337 An issue was discovered in Django 5.2 before 5.2.17 and 6.0 before 6.0.8. djangoproject · django 2026-08-04 high8.8 CVE-2026-15307 Django GeoDjango spatial lookups allow file writes and outbound requests through GDAL raster parsing pip · Django 2026-08-04 medium6.1 CVE-2026-53878 Django: DomainNameValidator permits newline characters that may enable HTTP header injection pip · django 2026-07-07 medium4.8 CVE-2026-53877 An issue was discovered in Django 6.0 before 6.0.7 and 5.2 before 5.2.16. pip · django 2026-07-07 low3.1 CVE-2026-48588 Django: cache middleware may expose private responses when unrelated request cookies are present pip · django 2026-07-07 low3.1 CVE-2026-8404 Django: UpdateCacheMiddleware may disclose cached responses due to case-sensitive Cache-Control handling pip · django 2026-06-03 low3.1 CVE-2026-7666 Django fails to prevent reuse of a partially-initialized connection after a failed `STARTTLS` handshake pip · django 2026-06-03 low3.1 CVE-2026-6873 An issue was discovered in Django 6.0 before 6.0.6 and 5.2 before 5.2.15. pip · django 2026-06-03 low3.1 CVE-2026-48587 Django: has_vary_header may expose cached responses when Vary values contain whitespace pip · django 2026-06-03 low3.7 CVE-2026-44546 daphne before 4.2.2 reconstructs a raw HTTP request from Twisted's parsed headers and feeds it to autobahn for WebSocket handshake processing. pip · daphne 2026-06-03 medium5.3 CVE-2026-44545 daphne: Unauthenticated attackers can cause excessive memory consumption by sending arbitrarily large WebSocket messages/frames pip · daphne 2026-06-03 low3.1 CVE-2026-35193 Django: UpdateCacheMiddleware may disclose private cached responses by omitting Authorization from Vary pip · django 2026-06-03 medium4.3 CVE-2026-6907 An issue was discovered in 6.0 before 6.0.5 and 5.2 before 5.2.14. pip · Django 2026-05-05 medium5.3 CVE-2026-5766 An issue was discovered in 6.0 before 6.0.5 and 5.2 before 5.2.14. pip · Django 2026-05-05 medium6.5 CVE-2026-35192 An issue was discovered in 6.0 before 6.0.5 and 5.2 before 5.2.14. pip · Django 2026-05-05 low2.7 CVE-2026-4292 An issue was discovered in 6.0 before 6.0.4, 5.2 before 5.2.13, and 4.2 before 4.2.30. pip · Django 2026-04-07 critical9.8 CVE-2026-4277 An issue was discovered in 6.0 before 6.0.4, 5.2 before 5.2.13, and 4.2 before 4.2.30. pip · Django 2026-04-07 high7.5 CVE-2026-3902 An issue was discovered in 6.0 before 6.0.4, 5.2 before 5.2.13, and 4.2 before 4.2.30. pip · Django 2026-04-07 high7.5 CVE-2026-33034 Django: SGI requests with a missing or understated `Content-Length` header could bypass the `DATA_UPLOAD_MAX_MEMORY_SIZE` limit pip · Django 2026-04-07 medium6.5 CVE-2026-33033 An issue was discovered in 6.0 before 6.0.4, 5.2 before 5.2.13, and 4.2 before 4.2.30. pip · Django 2026-04-07 low3.7 CVE-2026-25674 Django has a Race Condition vulnerability pip · Django 2026-03-03 high7.5 CVE-2026-25673 Django vulnerable to Uncontrolled Resource Consumption pip · Django 2026-03-03

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.