NetSight

Security Dashboard

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

Reset
69 matching advisories · page 2 of 3Index updated 2 minutes ago · Subscribe · RSS
SeverityIDTitleAffectedAge
medium4.8 CVE-2026-71852 pypdf: Possible long runtimes/large memory usage for large CID font width ranges pip · pypdf 2026-08-07 high7.5 CVE-2026-59936 pypdf: Possible infinite loop for not terminated inline images pip · pypdf 2026-07-08 high7.5 CVE-2026-59935 pypdf: Possible infinite loop for not terminated inline images (ASCII85 and ASCIIHex filter) pip · pypdf 2026-07-08 medium5.3 CVE-2026-59938 pypdf: Possible large memory usage for wrong image dimensions pip · pypdf 2026-07-08 high7.5 CVE-2026-59937 pypdf: Possible long runtimes for repeated malformed cross-reference entries pip · pypdf 2026-07-08 medium6.5 CVE-2026-57204 pypdf is a free and open-source pure-python PDF library. pypdf_project · pypdf, py-pdf · pypdf 2026-06-30 medium5.5 CVE-2026-54651 pypdf: Possible infinite loop when processing threads/articles in writer pip · pypdf 2026-06-22 medium5.5 CVE-2026-54531 pypdf: Possible infinite loop when processing outlines/bookmarks in writer pip · pypdf 2026-06-16 medium5.5 CVE-2026-54530 pypdf: Possible infinite loop when retrieving fonts for layout-mode text extraction pip · pypdf 2026-06-16 medium5.5 CVE-2026-49461 pypdf: Possible large memory usage for form XObjects during text extraction pip · pypdf 2026-06-16 medium5.1 CVE-2026-49460 pypdf: Inefficient decoding of FlateDecode PNG predictor streams pip · pypdf 2026-06-16 medium5.5 CVE-2026-48735 pypdf is a free and open-source pure-python PDF library. pip · pypdf 2026-05-28 medium3.3 CVE-2026-48156 pypdf: Possible long runtimes for zero-only width values in cross-reference streamsuntimes for zero-only width values in cross-reference streams pip · pypdf 2026-05-28 medium5.5 CVE-2026-48155 pypdf: Possible large memory usage for large offsets for layout mode text pip · pypdf 2026-05-28 medium6.5 CVE-2026-41314 pypdf: Manipulated FlateDecode image dimensions can exhaust RAM pip · pypdf 2026-04-16 medium6.5 CVE-2026-41313 pypdf: Possible long runtimes for wrong size values in incremental mode pip · pypdf 2026-04-16 medium6.5 CVE-2026-41312 pypdf: Manipulated FlateDecode predictor parameters can exhaust RAM pip · pypdf 2026-04-16 medium5.3 CVE-2026-41168 pypdf has long runtimes for wrong size values in cross-reference and object streams pip · pypdf 2026-04-15 medium5.3 CVE-2026-40260 pypdf: Manipulated XMP metadata entity declarations can exhaust RAM pip · pypdf 2026-04-10 high7.5 CVE-2026-33699 pypdf: Possible infinite loop during recovery attempts in DictionaryObject.read_from_stream pip · pypdf 2026-03-25 medium6.5 CVE-2026-33123 pypdf is a free and open-source pure-python PDF library. pip · pypdf 2026-03-18 medium5.5 CVE-2026-31826 pypdf is a free and open-source pure-python PDF library. pip · pypdf 2026-03-10 medium5.3 CVE-2026-28804 pypdf vulnerable to inefficient decoding of ASCIIHexDecode streams pip · pypdf 2026-03-02 medium5.3 CVE-2026-28351 pypdf: Manipulated RunLengthDecode streams can exhaust RAM pip · pypdf 2026-02-27 high7.5 CVE-2026-27888 pypdf: Manipulated FlateDecode XFA streams can exhaust RAM pip · pypdf 2026-02-26 high7.5 CVE-2026-27628 pypdf has a possible infinite loop when loading circular /Prev entries in cross-reference streams pip · pypdf 2026-02-25 medium5.5 CVE-2026-27026 pypdf possibly has long runtimes for malformed FlateDecode streams pip · pypdf 2026-02-18 medium5.5 CVE-2026-27025 pypdf has possible long runtimes/large memory usage for large /ToUnicode streams pip · pypdf 2026-02-18 medium5.5 CVE-2026-27024 pypdf has a possible infinite loop when processing TreeObject pip · pypdf 2026-02-18 medium4.3 CVE-2026-24688 pypdf has possible Infinite Loop when processing outlines/bookmarks pip · pypdf 2026-01-26

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.