NetSight

Security Dashboard

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

Reset
23 matching advisories · page 1 of 1Index updated just now · Subscribe · RSS
SeverityIDTitleAffectedAge
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 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 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 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 high7.5 CVE-2024-45490 An issue was discovered in libexpat before 2.6.3. libexpat_project · libexpat 2024-08-30 high7.5 CVE-2024-28757 libexpat through 2.6.1 allows an XML Entity Expansion attack when there is isolated use of external parsers (created via XML_ExternalEntityParserCreate). libexpat_project · libexpat, fedoraproject · fedora, netapp · active_iq_unified_manager +10 2024-03-10 high7.5 CVE-2023-52425 libexpat through 2.5.0 allows a denial of service (resource consumption) because many full reparsings are required in the case of a large token for which multi… libexpat_project · libexpat 2024-02-04 high7.5 CVE-2022-43680 In libexpat through 2.4.9, there is a use-after free caused by overeager destruction of a shared DTD in XML_ExternalEntityParserCreate in out-of-memory situati… libexpat_project · libexpat, debian · debian_linux, fedoraproject · fedora +9 2022-10-24 high8.1 CVE-2022-40674 libexpat before 2.4.9 has a use-after-free in the doContent function in xmlparse.c. libexpat_project · libexpat, debian · debian_linux, fedoraproject · fedora 2022-09-14 high7.5 CVE-2022-25314 In Expat (aka libexpat) before 2.4.5, there is an integer overflow in copyString. libexpat_project · libexpat, debian · debian_linux, fedoraproject · fedora +3 2022-02-18 high7.5 CVE-2022-23990 Expat (aka libexpat) before 2.4.4 has an integer overflow in the doProlog function. libexpat_project · libexpat, tenable · nessus, oracle · communications_metasolv_solution +3 2022-01-26 high8.8 CVE-2022-22827 storeAtts in xmlparse.c in Expat (aka libexpat) before 2.4.3 has an integer overflow. libexpat_project · libexpat, tenable · nessus, debian · debian_linux +1 2022-01-10 high8.8 CVE-2022-22826 nextScaffoldPart in xmlparse.c in Expat (aka libexpat) before 2.4.3 has an integer overflow. libexpat_project · libexpat, tenable · nessus, debian · debian_linux +1 2022-01-10 high8.8 CVE-2022-22825 lookup in xmlparse.c in Expat (aka libexpat) before 2.4.3 has an integer overflow. libexpat_project · libexpat, tenable · nessus, debian · debian_linux +1 2022-01-10 high8.1 CVE-2021-46143 In doProlog in xmlparse.c in Expat (aka libexpat) before 2.4.3, an integer overflow exists for m_groupSize. libexpat_project · libexpat, netapp · active_iq_unified_manager, netapp · clustered_data_ontap +5 2022-01-06 high8.8 CVE-2021-45960 In Expat (aka libexpat) before 2.4.3, a left shift by 29 (or more) places in the storeAtts function in xmlparse.c can lead to realloc misbehavior (e.g., alloca… libexpat_project · libexpat, tenable · nessus, debian · debian_linux +5 2022-01-01 high7.5 CVE-2019-15903 In libexpat before 2.2.8, crafted XML input could fool the parser into changing from DTD parsing to document parsing too early; a consecutive call to XML_GetCu… libexpat_project · libexpat, python · python 2019-09-04 high7.5 CVE-2018-20843 In libexpat in Expat before 2.2.7, XML input including XML names that contain a large number of colons could make the XML parser consume a high amount of RAM a… libexpat_project · libexpat, canonical · ubuntu_linux, debian · debian_linux +6 2019-06-24 high7.8 CVE-2017-11742 The writeRandomBytes_RtlGenRandom function in xmlparse.c in libexpat in Expat 2.2.1 and 2.2.2 on Windows allows local users to gain privileges via a Trojan hor… libexpat_project · libexpat 2017-07-30 high7.5 CVE-2017-9233 XML External Entity vulnerability in libexpat 2.2.0 and earlier (Expat XML Parser Library) allows attackers to put the parser in an infinite loop using a malfo… libexpat_project · libexpat, python · python, debian · debian_linux 2017-07-25 high8.1 CVE-2016-4472 The overflow protection in Expat is removed by compilers with certain optimization settings, which allows remote attackers to cause a denial of service (crash)… libexpat_project · libexpat, canonical · ubuntu_linux, mcafee · policy_auditor +1 2016-06-30 high7.5 CVE-2016-5300 The XML parser in Expat does not use sufficient entropy for hash initialization, which allows context-dependent attackers to cause a denial of service (CPU con… canonical · ubuntu_linux, debian · debian_linux, libexpat_project · libexpat +1 2016-06-16

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.