NetSight

Security Dashboard

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

Reset
52 matching advisories · page 1 of 2Index updated 3 minutes ago · Subscribe · RSS
SeverityIDTitleAffectedAge
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 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 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 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 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 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 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 high7.8 CVE-2022-40304 An issue was discovered in libxml2 before 2.10.3. xmlsoft · libxml2, netapp · active_iq_unified_manager, netapp · clustered_data_ontap +9 2022-11-23 high7.5 CVE-2022-40303 An issue was discovered in libxml2 before 2.10.3. xmlsoft · libxml2, netapp · active_iq_unified_manager, netapp · clustered_data_ontap +9 2022-11-23 high7.5 CVE-2022-23308 valid.c in libxml2 before 2.9.13 has a use-after-free of ID and IDREF attributes. xmlsoft · libxml2, fedoraproject · fedora, debian · debian_linux +9 2022-02-26 high8.8 CVE-2021-30560 Nokogiri has vulnerable dependencies on libxml2 and libxslt rubygems · nokogiri 2021-08-03 high7.8 CVE-2021-3516 There's a flaw in libxml2's xmllint in versions before 2.9.11. xmlsoft · xmllint, debian · debian_linux, fedoraproject · fedora +6 2021-06-01 high8.6 CVE-2021-3517 Nokogiri contains libxml Out-of-bounds Write vulnerability rubygems · nokogiri 2021-05-19 high8.8 CVE-2021-3518 Nokogiri Implements libxml2 version vulnerable to use-after-free rubygems · nokogiri 2021-05-18 high7.5 CVE-2020-7595 libxml as used in Nokogiri has an infinite loop in a certain end-of-file situation rubygems · nokogiri 2020-01-21 high7.5 CVE-2019-20388 xmlSchemaPreRun in xmlschemas.c in libxml2 2.9.10 allows an xmlSchemaValidateStream memory leak. xmlsoft · libxml2, debian · debian_linux, netapp · cloud_backup +9 2020-01-21 high7.5 CVE-2019-19956 xmlParseBalancedChunkMemoryRecover in parser.c in libxml2 before 2.9.10 has a memory leak related to newDoc->oldNs. xmlsoft · libxml2, debian · debian_linux, oracle · real_user_experience_insight +9 2019-12-24 high7.5 CVE-2019-5815 Nokogiri implementation of libxslt vulnerable to heap corruption rubygems · nokogiri 2019-12-11 high7.5 CVE-2019-18197 Nokogiri affected by libxslt Use of Uninitialized Resource/Use After Free vulnerability rubygems · nokogiri 2019-10-18 high7.5 CVE-2019-13118 libxslt Type Confusion vulnerability that affects Nokogiri rubygems · nokogiri 2019-07-01 high8.8 CVE-2017-15412 Nokogiri gem, via libxml, is affected by DoS vulnerabilities rubygems · nokogiri 2018-08-28 high7.5 CVE-2016-9597 It was found that Red Hat JBoss Core Services erratum RHSA-2016:2957 for CVE-2016-3705 did not actually include the fix for the issue found in libxml2, making … canonical · ubuntu_linux, xmlsoft · libxml2, debian · debian_linux +3 2018-07-30 high7.5 CVE-2018-14404 Nokogiri NULL Pointer Dereference rubygems · nokogiri 2018-07-19 high8.8 CVE-2017-5130 An integer overflow in xmlmemory.c in libxml2 before 2.9.5, as used in Google Chrome prior to 62.0.3202.62 and other products, allowed a remote attacker to pot… google · chrome, debian · debian_linux, xmlsoft · libxml2 2018-02-07 high7.5 CVE-2017-16932 Nokogiri gem, via libxml, is affected by DoS vulnerabilities rubygems · nokogiri 2017-11-23 high7.5 CVE-2017-9050 Out-of-bounds read in nokogiri rubygems · nokogiri 2017-05-18

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.