NetSight

Security Dashboard

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

Reset
136 matching advisories · page 1 of 5Index updated 3 minutes ago · Subscribe · RSS
SeverityIDTitleAffectedAge
medium5.6 CVE-2026-86144 In xinclude in libxml2 before 2.15.4, xmlXIncludeProcess and xmlXIncludeProcessTree do not propagate parseFlags. xmlsoft · libxml2 2026-09-05 medium6.9 CVE-2026-86143 In xmlIO in libxml2 before 2.15.4, an inconsistency in xmlOutputWriteCallback and xmlBufUse causes negative lengths to reach write callbacks, aka a lack of a c… xmlsoft · libxml2 2026-09-05 medium6.9 CVE-2026-86142 In libxml2 before 2.15.4, there is a heap-based buffer overflow in xmlXPtrEvalXPtrPart because of xmlXPtrEval xpointer length saturation. xmlsoft · libxml2 2026-09-05 low2.9 CVE-2026-86141 xmlregexp in libxml2 before 2.15.4 has a NULL pointer dereference in xmlRegNewParserCtxt after a strdup failure, i.e., it does not calculate a string length af… xmlsoft · libxml2 2026-09-05 high8.0 CVE-2026-86140 In libxml2 before 2.15.4, xmlSnprintfElements in valid.c has a strcat stack-based buffer overflow. xmlsoft · libxml2 2026-09-05 medium6.9 CVE-2026-86139 In libxml2 before 2.15.4, xmlURIEscapeStr in uri.c has an integer overflow. xmlsoft · libxml2 2026-09-05 medium6.9 CVE-2026-86138 In libxml2 before 2.15.4, xmlDictAddQString in dict.c has an integer overflow and resultant heap-based buffer overflow. xmlsoft · libxml2 2026-09-05 low2.9 CVE-2026-86137 In libxml2 before 2.15.4, xmlFAParsePosCharGroup has an out-of-bounds read, aka an out-of-bounds read in the NXT macro in xmlregexp. xmlsoft · libxml2 2026-09-05 high7.8 CVE-2026-11979 libxml2 is vulnerable to multiple stack-based buffer overflows in the xmlcatalog utility when running in --shell mode. xmlsoft · libxml2 2026-06-29 critical9.8 CVE-2026-6653 Use After Free in libxml2's xmlParseInternalSubset from GNOME libxml2 version 2.9.11 to 2.11.0 allows a remote attacker to cause a denial-of-service via malici… xmlsoft · libxml2 2026-06-22 medium6.5 CVE-2026-6732 A flaw was found in libxml2. xmlsoft · libxml2, redhat · hardened_images, redhat · jboss_core_services +5 2026-04-23 low2.9 CVE-2026-0992 A flaw was found in the libxml2 library. redhat · hardened_images, redhat · jboss_core_services, redhat · openshift_container_platform +4 2026-01-15 medium5.9 CVE-2026-0990 A flaw was found in libxml2, an XML parsing library. redhat · hardened_images, redhat · jboss_core_services, redhat · openshift_container_platform +4 2026-01-15 low3.7 CVE-2026-0989 A flaw was identified in the RelaxNG parser of libxml2 related to how external schema inclusions are handled. xmlsoft · libxml2, redhat · hardened_images, redhat · jboss_core_services +4 2026-01-15 medium6.2 CVE-2025-9714 Uncontrolled recursion in XPath evaluation in libxml2 up to and including version 2.9.14 allows a local attacker to cause a stack overflow via crafted expressi… xmlsoft · libxml2 2025-09-10 low3.3 CVE-2025-8732 A vulnerability was found in libxml2 up to 2.14.5. xmlsoft · libxml2, siemens · ruggedcom_rst2428p_firmware, ibm · vios +1 2025-08-08 high7.5 CVE-2025-7424 A flaw was found in the libxslt library. xmlsoft · libxslt, redhat · openshift_container_platform, redhat · enterprise_linux 2025-07-10 low2.5 CVE-2025-6170 A flaw was found in the interactive shell of the xmllint command-line tool, used for parsing XML files. redhat · jboss_core_services, redhat · openshift_container_platform, redhat · enterprise_linux +21 2025-06-16 high7.5 CVE-2025-6021 A flaw was found in libxml2's xmlBuildQName function, where integer overflows in buffer size calculations can lead to a stack-based buffer overflow. xmlsoft · libxml2, redhat · jboss_core_services, redhat · openshift_container_platform +9 2025-06-12 low2.9 CVE-2025-32415 In libxml2 before 2.13.8 and 2.14.x before 2.14.2, xmlSchemaIDCFillNodeTables in xmlschemas.c has a heap-based buffer under-read. xmlsoft · libxml2 2025-04-17 medium5.6 CVE-2025-32414 In libxml2 before 2.13.8 and 2.14.x before 2.14.2, out-of-bounds memory access can occur in the Python API (Python bindings) because of an incorrect return val… xmlsoft · libxml2 2025-04-08 high7.8 CVE-2025-24855 numbers.c in libxslt before 1.1.43 has a use-after-free because, in nested XPath evaluations, an XPath context node can be modified but never restored. xmlsoft · libxslt 2025-03-14 high7.8 CVE-2024-55549 xsltGetInheritedNsList in libxslt before 1.1.43 has a use-after-free issue related to exclusion of result prefixes. xmlsoft · libxslt 2025-03-14 low2.9 CVE-2025-27113 libxml2 before 2.12.10 and 2.13.x before 2.13.6 has a NULL pointer dereference in xmlPatMatch in pattern.c. xmlsoft · libxml2 2025-02-18 high7.8 CVE-2025-24928 libxml2 before 2.12.10 and 2.13.x before 2.13.6 has a stack-based buffer overflow in xmlSnprintfElements in valid.c. netapp · active_iq_unified_manager, netapp · manageability_software_development_kit, netapp · ontap +8 2025-02-18 high7.8 CVE-2024-56171 libxml2 before 2.12.10 and 2.13.x before 2.13.6 has a use-after-free in xmlSchemaIDCFillNodeTables and xmlSchemaBubbleIDCNodeTables in xmlschemas.c. xmlsoft · libxml2, netapp · hci_compute_node, netapp · h410c_firmware +8 2025-02-18 high8.1 CVE-2022-49043 xmlXIncludeAddNode in xinclude.c in libxml2 before 2.11.0 has a use-after-free. xmlsoft · libxml2 2025-01-26 critical9.1 CVE-2024-40896 In libxml2 2.11 before 2.11.9, 2.12 before 2.12.9, and 2.13 before 2.13.3, the SAX parser can produce events for external entities even if custom SAX handlers … xmlsoft · libxml2, netapp · hci_compute_node, netapp · solidfire_\&_hci_management_node +6 2024-12-23 high7.5 CVE-2024-34459 An issue was discovered in xmllint (from libxml2) before 2.11.8 and 2.12.x before 2.12.7. xmlsoft · libxml2 2024-05-14 high7.5 CVE-2024-25062 An issue was discovered in libxml2 before 2.11.7 and 2.12.x before 2.12.5. xmlsoft · libxml2 2024-02-04

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.