{
  "fix": "python3-libxml2 2.9.4\u002Bdfsg1-6.1ubuntu1.9\u002Besm9",
  "url": "https://patchblox.com/security/fix/linux/ubuntu-bionic-python3-libxml2-2.9.4-dfsg1-6.1ubuntu1.9-esm9",
  "summary": "python3-libxml2 2.9.4\u002Bdfsg1-6.1ubuntu1.9\u002Besm9, released October 9, 2026, fixes 5 CVEs in python3-libxml2. None of them is reported as exploited. Patch Radar priority: High. The product is no longer supported.",
  "platform": "linux",
  "type": "package",
  "title": "python3-libxml2 2.9.4\u002Bdfsg1-6.1ubuntu1.9\u002Besm9 for Ubuntu 18.04.6 LTS (bionic)",
  "released": "2026-10-09T22:35:50Z",
  "priority": "High",
  "priorityTier": 3,
  "priorityReason": "Closes CVE-2026-86143, high severity",
  "supported": false,
  "cveCount": 5,
  "exploitedCveCount": 0,
  "kevCveCount": 0,
  "ransomwareCveCount": 0,
  "maxEpss": 0.00194,
  "maxCvss": 8.5,
  "appliesTo": [
    {
      "product": "python3-libxml2",
      "productUrl": "https://patchblox.com/security/product/linux/python3-libxml2",
      "release": "Ubuntu 18.04.6 LTS (bionic)",
      "fixedVersion": "2.9.4\u002Bdfsg1-6.1ubuntu1.9\u002Besm9",
      "supported": true
    }
  ],
  "cves": [
    {
      "cveId": "CVE-2026-86143",
      "url": "https://patchblox.com/security/cve/CVE-2026-86143",
      "title": "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.",
      "priority": "High",
      "severity": "Moderate",
      "cvss": 8.5,
      "epss": 0.00194,
      "kev": false,
      "ransomware": false,
      "exploited": false,
      "disclosed": false
    },
    {
      "cveId": "CVE-2026-86144",
      "url": "https://patchblox.com/security/cve/CVE-2026-86144",
      "title": "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).",
      "priority": "High",
      "severity": "Moderate",
      "cvss": 8.5,
      "epss": 0.00186,
      "kev": false,
      "ransomware": false,
      "exploited": false,
      "disclosed": false
    },
    {
      "cveId": "CVE-2026-86142",
      "url": "https://patchblox.com/security/cve/CVE-2026-86142",
      "title": "In libxml2 before 2.15.4, there is a heap-based buffer overflow in xmlXPtrEvalXPtrPart because of xmlXPtrEval xpointer length saturation.",
      "priority": "High",
      "severity": "Moderate",
      "cvss": 8.5,
      "epss": 0.00157,
      "kev": false,
      "ransomware": false,
      "exploited": false,
      "disclosed": false
    },
    {
      "cveId": "CVE-2026-86138",
      "url": "https://patchblox.com/security/cve/CVE-2026-86138",
      "title": "In libxml2 before 2.15.4, xmlDictAddQString in dict.c has an integer overflow and resultant heap-based buffer overflow.",
      "priority": "High",
      "severity": "Moderate",
      "cvss": 8.5,
      "epss": 0.00132,
      "kev": false,
      "ransomware": false,
      "exploited": false,
      "disclosed": false
    },
    {
      "cveId": "CVE-2026-76781",
      "url": "https://patchblox.com/security/cve/CVE-2026-76781",
      "title": "libxml2: A flaw was found in libxml2",
      "priority": "Routine",
      "severity": "Medium",
      "cvss": 5.5,
      "epss": 0.00157,
      "kev": false,
      "ransomware": false,
      "exploited": false,
      "disclosed": false
    }
  ],
  "dataAsOf": "2026-11-11T07:45:43Z",
  "attribution": {
    "text": "Data: Patchblox Patch Radar",
    "url": "https://patchblox.com/security/patch-radar",
    "terms": "https://patchblox.com/security/patch-radar/use-the-data"
  }
}