NetSight

Security Dashboard

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

Reset
57 matching advisories · page 1 of 2Index updated 2 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 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 medium6.5 CVE-2026-6732 A flaw was found in libxml2. xmlsoft · libxml2, redhat · hardened_images, redhat · jboss_core_services +5 2026-04-23 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 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 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 medium6.5 CVE-2023-45322 libxml2 through 2.11.5 has a use-after-free that can only occur after a certain memory allocation fails. xmlsoft · libxml2 2023-10-06 medium6.5 CVE-2023-39615 Xmlsoft Libxml2 v2.11.0 was discovered to contain an out-of-bounds read via the xmlSAX2StartElement() function at /libxml2/SAX2.c. xmlsoft · libxml2 2023-08-29 medium6.5 CVE-2023-29469 An issue was discovered in libxml2 before 2.10.4. xmlsoft · libxml2, debian · debian_linux 2023-04-24 medium6.5 CVE-2023-28484 In libxml2 before 2.10.4, parsing of certain invalid XSD schemas can lead to a NULL pointer dereference and subsequently a segfault. xmlsoft · libxml2, debian · debian_linux 2023-04-24 medium6.1 CVE-2016-3709 Possible cross-site scripting vulnerability in libxml after commit 960f0e2. xmlsoft · libxml2 2022-07-28 medium6.5 CVE-2022-29824 In libxml2 before 2.9.14, several buffer handling functions in buf.c (xmlBuf*) and tree.c (xmlBuffer*) don't check for integer overflows. xmlsoft · libxml2, xmlsoft · libxslt, fedoraproject · fedora +9 2022-05-03 medium6.5 CVE-2021-3541 A flaw was found in libxml2. xmlsoft · libxml2, redhat · jboss_core_services, oracle · zfs_storage_appliance_kit +9 2021-07-09 medium5.9 CVE-2021-3537 Nokogiri Implements libxml2 version vulnerable to null pointer dereferencing rubygems · nokogiri 2021-05-14 medium6.5 CVE-2020-24977 GNOME project libxml2 v2.9.10 has a global buffer over-read vulnerability in xmlEncodeEntitiesInternal at libxml2/entities.c. xmlsoft · libxml2, debian · debian_linux, fedoraproject · fedora +9 2020-09-04 medium5.3 CVE-2019-13117 Uninitialized read in Nokogiri gem rubygems · nokogiri 2019-07-01 medium6.5 CVE-2018-14567 libxml2 2.9.8, if --with-lzma is used, allows remote attackers to cause a denial of service (infinite loop) via a crafted XML file that triggers LZMA_MEMLIMIT_… xmlsoft · libxml2, canonical · ubuntu_linux, debian · debian_linux 2018-08-16 medium6.5 CVE-2016-9598 libxml2, as used in Red Hat JBoss Core Services, allows context-dependent attackers to cause a denial of service (out-of-bounds read and application crash) via… redhat · jboss_core_services, xmlsoft · libxml2 2018-08-16 medium6.5 CVE-2016-9596 libxml2, as used in Red Hat JBoss Core Services and when in recovery mode, allows context-dependent attackers to cause a denial of service (stack consumption) … redhat · jboss_core_services, xmlsoft · libxml2 2018-08-16 medium6.5 CVE-2017-18258 Uncontrolled resource consumption in nokogiri rubygems · nokogiri 2018-04-08 medium5.3 CVE-2018-9251 The xz_decomp function in xzlib.c in libxml2 2.9.8, if --with-lzma is used, allows remote attackers to cause a denial of service (infinite loop) via a crafted … xmlsoft · libxml2, debian · debian_linux 2018-04-04 medium4.7 CVE-2017-5969 libxml2 2.9.4, when used in recover mode, allows remote attackers to cause a denial of service (NULL pointer dereference) via a crafted XML document. xmlsoft · libxml2 2017-04-11 medium5.3 CVE-2015-9019 In libxslt 1.1.29 and earlier, the EXSLT math.random function was not initialized with a random seed during startup, which could cause usage of this function t… xmlsoft · libxslt 2017-04-05 medium5.5 CVE-2016-9318 libxml2 2.9.4 and earlier, as used in XMLSec 1.2.23 and earlier and other products, does not offer a flag directly indicating that the current document may be … xmlsoft · libxml2, canonical · ubuntu_linux 2016-11-16 medium6.5 CVE-2016-2073 The htmlParseNameComplex function in HTMLparser.c in libxml2 allows attackers to cause a denial of service (out-of-bounds read) via a crafted XML document. xmlsoft · libxml2, debian · debian_linux, canonical · ubuntu_linux 2016-02-12 medium5.0 CVE-2015-8317 The xmlParseXMLDecl function in parser.c in libxml2 before 2.9.3 allows context-dependent attackers to obtain sensitive information via an (1) unterminated enc… debian · debian_linux, canonical · ubuntu_linux, xmlsoft · libxml2 +6 2015-12-15 medium5.8 CVE-2015-8242 The xmlSAX2TextNode function in SAX2.c in the push interface in the HTML parser in libxml2 before 2.9.3 allows context-dependent attackers to cause a denial of… xmlsoft · libxml2, hp · icewall_federation_agent, hp · icewall_file_manager +9 2015-12-15

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.