NetSight

Security Dashboard

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

Reset
69 matching advisories · page 1 of 3Index updated just now · Subscribe · RSS
SeverityIDTitleAffectedAge
high7.5 CVE-2026-134364 pypdf 3.7.1 before 7.0.0 contains an information disclosure vulnerability that allows attackers to guess placeholders in encrypted templated documents by analy… py-pdf · pypdf 81 minutes ago high7.5 CVE-2026-134366 pypdf before 7.0.0 contains a resource exhaustion vulnerability that allows attackers to cause large memory usage by supplying crafted PDF cross-reference stre… py-pdf · pypdf 81 minutes ago high7.5 CVE-2026-134367 pypdf 2.4.2 before 7.0.0 contains a resource exhaustion vulnerability in its handling of XFA forms that allows attackers to cause excessive memory consumption. py-pdf · pypdf 81 minutes ago high7.1 CVE-2026-119209 pypdf has possible large memory usage when parsing cross-reference streams pip · pypdf 23 days ago high7.1 CVE-2026-119208 pypdf has possible long runtimes/large memory usage for encrypted PDF files pip · pypdf 23 days ago high7.1 CVE-2026-119207 pypdf has possible large memory usage for exceptions in strict mode pip · pypdf 23 days ago high7.1 CVE-2026-119206 pypdf has possible long runtimes when retrieving page labels pip · pypdf 23 days ago high7.1 CVE-2026-119205 pypdf has possible infinite loop when cloning dictionaries pip · pypdf 23 days ago high7.1 CVE-2026-119204 pypdf has possible large memory usage when parsing page tree pip · pypdf 23 days ago high7.1 CVE-2026-119203 pypdf has possible infinite loop when hitting EOF in standard xref table during trailer search pip · pypdf 23 days ago medium5.5 CVE-2026-113795 pypdf: Possible large memory usage for streams with multiple filters pip · pypdf 31 days ago medium5.5 CVE-2026-113794 pypdf: Possible infinite loop when hitting EOF in standard xref table pip · pypdf 31 days ago medium4.3 CVE-2026-113793 pypdf is a free and open-source pure-python PDF library. pip · pypdf 31 days ago medium6.0 CVE-2026-113792 pypdf: Possible infinite loop in PdfWriter.find_outline_item pip · pypdf 31 days ago medium6.0 CVE-2026-113791 pypdf: Possible large memory usage when parsing content streams pip · pypdf 31 days ago medium6.0 CVE-2026-113790 pypdf: Possible large memory usage when parsing arrays and dictionaries pip · pypdf 31 days ago medium6.0 CVE-2026-113789 pypdf: Possible long runtimes/large memory usage when retrieving form fields pip · pypdf 31 days ago high7.5 CVE-2026-103000 pypdf: Possible large memory usage when retrieving alphabetical page labels pip · pypdf 52 days ago high7.5 CVE-2026-102999 pypdf: Possible long runtimes with large amount of embedded files pip · pypdf 52 days ago high7.5 CVE-2026-102998 pypdf: Possible long runtimes when generating appearance streams pip · pypdf 52 days ago high7.5 CVE-2026-102997 pypdf: Possible long runtimes for partially malformed FlateDecode streams (Follow-up) pip · pypdf 52 days ago high7.5 CVE-2026-102996 pypdf: Possible large memory usage when parsing font data pip · pypdf 52 days ago high7.5 CVE-2026-102995 pypdf: Possible large memory usage for large /ToUnicode streams (Follow-up 2) pip · pypdf 52 days ago high7.5 CVE-2026-102994 pypdf: Possible long runtimes/large memory usage when parsing indirect objects pip · pypdf 52 days ago high7.5 CVE-2026-102993 pypdf: Possible large memory usage when retrieving Roman page labels pip · pypdf 52 days ago medium4.8 CVE-2026-84311 pypdf: Possible long runtimes/large memory usage when extracting XForm objects pip · pypdf 2026-09-01 medium4.8 CVE-2026-84310 pypdf: Possible long runtimes/large memory usage when retrieving outlines pip · pypdf 2026-09-01 medium5.5 CVE-2026-84309 pypdf: Possible infinite loop for TreeObject.insert_child pip · pypdf 2026-09-01 medium5.3 CVE-2026-82398 pypdf: Inefficient handling of non-whitespace inputs in read_until_whitespace pip · pypdf 2026-08-31 medium4.8 CVE-2026-71870 pypdf: Possible large memory usage for large /ToUnicode streams pip · pypdf 2026-08-07

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.