NetSight

Security Dashboard

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

Reset
68 matching advisories · page 1 of 3Index updated 2 minutes ago · Subscribe · RSS
SeverityIDTitleAffectedAge
medium5.9 CVE-2026-117610 libexpat through 2.9.0 contains a NULL pointer dereference vulnerability in externalEntityInitProcessor2() in lib/xmlparse.c that mishandles the XML_TOK_NONE t… libexpat_project · libexpat 25 days ago high8.2 CVE-2026-118370 libexpat through 2.9.0 contains a signed integer overflow vulnerability in storeAtts() in lib/xmlparse.c that allows attackers to trigger out-of-bounds writes … libexpat_project · libexpat, libexpat · libexpat, libexpat project · libexpat 25 days ago high7.5 CVE-2026-115506 libexpat through 2.9.0 contains a denial of service vulnerability because billion laughs protection in accountingDiffTolerated() in xmlparse.c detects entity a… libexpat_project · libexpat 30 days ago medium5.9 CVE-2026-113351 libexpat 2.7.2 through 2.9.0 contains a denial of service vulnerability because XML_ParserReset zeroes the direct byte count but never offsets tracked heap all… libexpat_project · libexpat 32 days ago medium5.9 CVE-2026-76956 In libexpat 2.8.2 and 2.8.3 before 2.8.4, misinterpretation of getentropy's return code leads to insufficient entropy, which results in being vulnerable to has… libexpat_project · libexpat 2026-08-20 medium4.9 CVE-2026-76957 libexpat before 2.8.4 lacks handler call depth tracking with custom encoding callbacks. libexpat_project · libexpat, libexpat project · libexpat 2026-08-20 high8.7 CVE-2026-66046 Expat through 2.8.3 contains a denial of service vulnerability caused by quadratic algorithmic complexity in the storeAtts() function in xmlparse.c, where proc… libexpat_project · libexpat, libexpat project · libexpat 2026-08-18 medium4.9 CVE-2026-56412 libexpat before 2.8.2 does not consider XML_TOK_DATA_CHARS in doCdataSection and thus lacks handler call depth tracking for various calls from within handlers … libexpat_project · libexpat, libexpat project · libexpat 2026-06-21 medium6.9 CVE-2026-56411 xmlwf in libexpat before 2.8.2 has an integer overflow in endDoctypeDecl via NOTATION declarations. libexpat_project · libexpat, libexpat project · libexpat 2026-06-21 medium6.9 CVE-2026-56410 xmlwf in libexpat before 2.8.2 has an integer overflow in resolveSystemId. libexpat_project · libexpat, libexpat project · libexpat 2026-06-21 medium6.5 CVE-2026-56409 xmlwf in libexpat before 2.8.2 has an integer overflow for the output filename when -d outputDir is used. libexpat_project · libexpat, libexpat project · libexpat 2026-06-21 medium6.9 CVE-2026-56408 libexpat before 2.8.2 has an integer overflow in copyString. libexpat_project · libexpat, libexpat project · libexpat 2026-06-21 medium6.9 CVE-2026-56407 libexpat before 2.8.2 has an integer overflow in doProlog that is related to storeEntityValue and entity textLen. libexpat_project · libexpat, libexpat project · libexpat 2026-06-21 medium6.9 CVE-2026-56406 libexpat before 2.8.2 has an integer overflow in XML_ParseBuffer because it lacked a check that was present in XML_Parse. libexpat_project · libexpat, libexpat project · libexpat 2026-06-21 medium6.9 CVE-2026-56405 libexpat before 2.8.2 has an integer overflow in getAttributeId. libexpat_project · libexpat, libexpat project · libexpat 2026-06-21 medium6.9 CVE-2026-56404 libexpat before 2.8.2 has an integer overflow in addBinding. libexpat_project · libexpat, libexpat project · libexpat 2026-06-21 medium6.9 CVE-2026-56403 libexpat before 2.8.2 has an integer overflow in storeAtts. libexpat_project · libexpat, libexpat project · libexpat 2026-06-21 medium6.9 CVE-2026-56132 In libexpat before 2.8.2, there is a heap-based buffer overflow in doProlog in xmlparse.c because scaffold backing array reallocation is mishandled when there … libexpat_project · libexpat, libexpat project · libexpat 2026-06-19 medium4.9 CVE-2026-56131 libexpat before 2.8.2 lacks handler call depth tracking for calls to XML_ResumeParser from within handlers in cases of a policy violation. libexpat_project · libexpat, libexpat project · libexpat 2026-06-19 medium4.9 CVE-2026-50219 libexpat before 2.8.2 lacks handler call depth tracking for calls to XML_GetBuffer, XML_Parse, XML_ParseBuffer, XML_ParserFree, or XML_ParserReset from within … libexpat_project · libexpat, libexpat project · libexpat 2026-06-04 high7.5 CVE-2026-45186 In libexpat before 2.8.1, the computational complexity of attribute name collision checks allows a denial of service via moderately sized crafted XML input. libexpat_project · libexpat, libexpat project · libexpat 2026-05-10 low2.9 CVE-2026-41080 libexpat before 2.8.0 uses insufficient entropy, and thus hash flooding can occur via a crafted XML document. libexpat_project · libexpat 2026-04-16 low2.9 CVE-2026-32778 libexpat before 2.7.5 allows a NULL pointer dereference in the function setContext on retry after an earlier ouf-of-memory condition. libexpat_project · libexpat, libexpat project · libexpat 2026-03-16 medium4.0 CVE-2026-32777 libexpat before 2.7.5 allows an infinite loop while parsing DTD content. libexpat_project · libexpat, libexpat project · libexpat 2026-03-16 medium4.0 CVE-2026-32776 libexpat before 2.7.5 allows a NULL pointer dereference with empty external parameter entity content. libexpat_project · libexpat, libexpat project · libexpat 2026-03-16 medium6.9 CVE-2026-25210 In libexpat before 2.7.4, the doContent function does not properly determine the buffer size bufSize because there is no integer overflow check for tag buffer … libexpat_project · libexpat, libexpat project · libexpat 2026-01-30 low2.9 CVE-2026-24515 In libexpat before 2.7.4, XML_ExternalEntityParserCreate does not copy unknown encoding handler user data. libexpat_project · libexpat, libexpat project · libexpat 2026-01-23 low2.9 CVE-2025-66382 In libexpat through 2.7.3, a crafted file with an approximate size of 2 MiB can lead to dozens of seconds of processing time. libexpat_project · libexpat 2025-11-28 high7.5 CVE-2025-59375 libexpat in Expat before 2.7.2 allows attackers to trigger large dynamic memory allocations via a small document that is submitted for parsing. libexpat_project · libexpat, libexpat project · libexpat 2025-09-15 medium5.9 CVE-2024-50602 An issue was discovered in libexpat before 2.6.4. netapp · active_iq_unified_manager, netapp · solidfire_\&_hci_management_node, netapp · solidfire_\&_hci_storage_node +9 2024-10-27

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.