NetSight

Security Dashboard

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

Reset
891 matching advisories · page 2 of 30Index updated 9 minutes ago · Subscribe · RSS
SeverityIDTitleAffectedAge
high8.5 CVE-2026-18597 The PDF creation feature of Foxit PDF Services API supports referencing external files. 2026-08-06 high7.8 CVE-2026-57260 The application opened a PDF file containing an abnormal Unity 3D object. foxit · pdf_editor, foxit · pdf_reader 2026-07-08 high7.8 CVE-2026-57256 When the application opens a PDF and executes JavaScript, it performs abnormal operations on the list box field, and this operation is repeated after the form … foxit · pdf_editor, foxit · pdf_reader 2026-07-08 high7.8 CVE-2026-57254 There is an abnormal annotation within the PDF that is referenced by other objects. foxit · pdf_editor, foxit · pdf_reader 2026-07-08 high7.8 CVE-2026-57252 When the application opens a PDF file, during the process of JavaScript deleting pages and removing attachment annotations, it will cause the attachment panel … foxit · pdf_editor, foxit · pdf_reader 2026-07-08 high7.8 CVE-2026-57251 The application opens a PDF, but the cloud-like appearance of the construction process lacks proper setting of an upper limit and consistency checks. foxit · pdf_editor, foxit · pdf_reader 2026-07-08 high7.8 CVE-2026-57250 When the application opens a PDF and JavaScript resets the form fields, the script re-enters the interface. foxit · pdf_editor, foxit · pdf_reader 2026-07-08 high7.8 CVE-2026-57249 After the application opened the PDF file, the script first reset the annotation status, then triggered the reset form event by additional action. foxit · pdf_editor, foxit · pdf_reader 2026-07-08 high7.8 CVE-2026-57248 When the application opens a PDF file and JavaScript writes annotation attributes, there is a lack of sufficient object type and argument checks. foxit · pdf_editor, foxit · pdf_reader 2026-07-08 high7.8 CVE-2026-57247 The application re-enters the document structure via field processing and deletes the current page, and then continues using the field objects obtained before … foxit · pdf_editor, foxit · pdf_reader 2026-07-08 high7.8 CVE-2026-57246 When dealing with abnormally constructed objects, there is a lack of argument validation; JavaScript triggers signature verification, but the signature plugin … foxit · pdf_editor, foxit · pdf_reader 2026-07-08 high7.8 CVE-2026-57245 When the application opens a PDF, traverses and builds the annotation elements related to hyperlinks, it fails to validate the abnormal annotation relationship… foxit · pdf_editor, foxit · pdf_reader 2026-07-08 high7.8 CVE-2026-57244 After JavaScript resetting the form, the synchronization process lacks re-entry protection and object lifecycle verification, resulting in the failure of the c… foxit · pdf_editor, foxit · pdf_reader 2026-07-08 high7.8 CVE-2026-57242 The application opens the PDF, and JavaScript modifies the form. foxit · pdf_editor, foxit · pdf_reader 2026-07-08 high7.8 CVE-2026-57240 When the application opens a PDF file and JavaScript deletes the PDF fields, the subsequent logic still uses the old field pointers, resulting in invalid point… foxit · pdf_editor, foxit · pdf_reader 2026-07-08 high8.2 CVE-2026-57239 The user-controllable executable files will be directly executed by high-privilege processes, allowing low-privilege users to have the opportunity to elevate t… foxit · pdf_editor, foxit · pdf_reader 2026-07-08 high7.8 CVE-2026-57238 After the application opened the PDF, JavaScript deleted the form field object. foxit · pdf_editor, foxit · pdf_reader 2026-07-08 high7.8 CVE-2026-57237 When the application opens a PDF and JavaScript modifies the properties of form fields, it causes the state of the underlying objects referenced by the program… foxit · pdf_editor, foxit · pdf_reader 2026-07-08 high7.8 CVE-2026-13129 When the application opens a PDF file, JavaScript uses the damaged field tree to trigger field traversal, resulting in the program holding an invalid form obje… foxit · pdf_editor, foxit · pdf_reader 2026-07-08 high7.8 CVE-2026-13128 Embedding JavaScript within a PDF file will cause the page to be deleted. foxit · pdf_editor, foxit · pdf_reader 2026-07-08 high7.8 CVE-2026-13127 The application opens the PDF file. foxit · pdf_editor, foxit · pdf_reader 2026-07-08 high7.8 CVE-2026-13126 The embedded JavaScript in the PDF deleted the pages, making the object invalid. foxit · pdf_editor, foxit · pdf_reader 2026-07-08 high8.6 CVE-2026-12057 When the application executes the JavaScript script embedded in the PDF within the sandbox, it fails to intercept some dangerous interfaces, which allows remot… foxit · ai 2026-06-15 high7.8 CVE-2026-5943 Document structural anomalies caused inconsistencies between page element relationships and internal index states. foxit · pdf_editor, foxit · pdf_reader 2026-04-27 high7.8 CVE-2026-5941 Parsing logic flaws cause non-signature data to be misidentified as valid signatures when processing malformed form field hierarchies, leading to invalid memor… foxit · pdf_editor, foxit · pdf_reader 2026-04-27 high7.8 CVE-2026-5940 Calling a function that triggers a UI refresh after removing comments via a script may access an invalidated object, leading to program crashes. foxit · pdf_editor, foxit · pdf_reader 2026-04-27 high8.5 CVE-2026-5936 An attacker can control a server-side HTTP request by supplying a crafted URL, causing the server to initiate requests to arbitrary destinations. foxit · pdf_services_api 2026-04-13 high7.1 CVE-2026-4947 Addressed a potential insecure direct object reference (IDOR) vulnerability in the signing invitation acceptance process. foxit · esign 2026-04-01 high7.3 CVE-2026-3780 The application's installer runs with elevated privileges but resolves system executables and DLLs using untrusted search paths that can include user-writable … foxit · pdf_editor, foxit · pdf_reader 2026-04-01 high7.8 CVE-2026-3779 The application's list box calculate array logic keeps stale references to page or form objects after they are deleted or re-created, which allows crafted docu… foxit · pdf_editor, foxit · pdf_reader 2026-04-01

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.