p PatchFirst

PatchFirst · Aktuelle Sicherheitslücken

Sicherheitslücken in libxml2

In den letzten 30 Tagen veröffentlichte Sicherheitslücken für libxml2: 0. Davon im KEV-Katalog: 0.

Sicherheitslücken filtern
Filter zurücksetzen

Sicherheitslücken: 10

  1. CVE-2026-76781

    Mittel · CVSS 5.5EPSS 0,17%Korrektur verfügbar

    Libxml2: libxml2: null pointer dereference parsing nextcatalog without catalog attribute

    A flaw was found in libxml2. A local user or an attacker providing a specially crafted XML catalog can trigger a NULL pointer dereference during XML catalog parsing. This occurs when a `nextCatalog` element lacks its mandatory `catalog` attribute, leading to the application crashing and causing a Denial of Service (DoS).

    • Auf 2.15.2+dfsg-0.1ubuntu0.3 aktualisieren
    Veröffentlicht Aktualisiert
  2. CVE-2026-74860

    Hoch · CVSS 8.5EPSS 0,66%Korrektur verfügbar

    Libxml2: double-free/uaf in libxml2 python bindings

    A flaw was found in libxml2 with Python bindings enabled. A remote attacker could exploit this vulnerability by providing a specially crafted XML document containing a Document Type Definition (DTD) with enumerated attribute values. This triggers a double-free error in the SAX attributeDecl callback handler, where a string is freed twice. This flaw can lead to a denial of service (DoS) due to a reproducible crash in Python applications using the libxml2 SAX bindings.

    • Auf 2.15.2+dfsg-0.1ubuntu0.2 aktualisieren
    Veröffentlicht Aktualisiert
  3. CVE-2026-86144

    Mittel · CVSS 5.6EPSS 0,19%Korrektur verfügbar

    CVE-2026-86144

    In xinclude in libxml2 before 2.15.4, xmlXIncludeProcess and xmlXIncludeProcessTree do not propagate parseFlags. This has security relevance for, for example, the XML_PARSE_NONET flag, if (without it) a custom resource loader accesses the internet and triggers XML external entity injection, SSRF, or a denial of service (e.g., for an attacker-controlled internet resource that is intentionally slow).

    • Auf 2.15.2+dfsg-0.1ubuntu0.3 aktualisieren
    Veröffentlicht Aktualisiert
  4. CVE-2026-86143

    Mittel · CVSS 6.9EPSS 0,19%Korrektur verfügbar

    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 check for integer overflow before calling writecallback. This has security relevance for many types of uses of that length value within a callback.

    • Auf 2.15.2+dfsg-0.1ubuntu0.3 aktualisieren
    Veröffentlicht Aktualisiert
  5. CVE-2026-11979

    Niedrig · CVSS 1.8EPSS 0,15%Keine Korrektur veröffentlicht

    Stack-Based Buffer Overflow in libxml2

    libxml2 is vulnerable to multiple stack-based buffer overflows in the xmlcatalog utility when running in --shell mode. The usershell() function processes user input using fixed-size stack buffers without proper bounds checking. By supplying an overly long input line, an attacker can overflow internal buffers (command, arg, and argv) during input parsing. This results in memory corruption within the stack frame. Successful exploitation may cause a crash or potentially allow arbitrary code execution in the context of the xmlcatalog process. This issue has been fixed in the commit c2e233fc. NOTE: The maintainers of this project did not agree t

    Veröffentlicht Aktualisiert
  6. CVE-2026-6732

    Mittel · CVSS 6.5EPSS 0,63%Korrektur verfügbar

    Libxml2: libxml2: denial of service via crafted xsd-validated document

    A flaw was found in libxml2. This vulnerability occurs when the library processes a specially crafted XML Schema Definition (XSD) validated document that includes an internal entity reference. An attacker could exploit this by providing a malicious document, leading to a type confusion error that causes the application to crash. This results in a denial of service (DoS), making the affected system or application unavailable.

    • Auf 2.15.2+dfsg-0.1ubuntu0.1 aktualisieren
    Veröffentlicht Aktualisiert

Prüfen Sie Ihren Server

Gleichen Sie Ihren installierten Stack und seine Versionen mit den aktuellen Sicherheitsmeldungen ab.

Prüfen Sie Ihren Server →