Linux · openSUSE Leap · Security advisory · September 24, 2026

OPENSUSE-SU-2026:21945-1: expat security update

OPENSUSE-SU-2026:21945-1, released September 24, 2026, fixes 17 CVEs in expat (version 2.8.4-160000.1.1). None of them is reported as exploited. Patch Radar priority: High.

High
CVEs closed
17
None rated Critical
Exploited
0
None reported
Highest CVSS
8.2
Base score, 0 to 10
Highest EPSS
0.0074
54th percentile

Priority of the 17 CVEs

Patch now 0 Urgent 0 High 4 Routine 13

Fixed package versions

ProductReleaseFixed in
expatopensuse-leap 16.02.8.4-160000.1.1

CVEs this fix closes

PriorityCVETitleCVSSEPSSExploitation
High CVE-2026-66046 Expat Denial of Service via storeAtts() Quadratic Complexity7.5 0.0074 None reported
High 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.8.2 0.0048 None reported
High CVE-2026-76956 In libexpat 2.8.2 and 2.8.3 before 2.8.4, misinterpretation of getentropy's return code leads to insufficient entropy, which results in being vulnerable to hash flooding attacks, causing a denial of service via crafted XML content.7.5 0.0029 None reported
High CVE-2026-76957 libexpat before 2.8.4 lacks handler call depth tracking with custom encoding callbacks. Thus, a use-after-free can occur. NOTE: this is similar to CVE-2026-50219, CVE-2026-56131 and CVE-2026-56412.7.8 0.0011 None reported
Routine CVE-2026-41080 expat: libexpat before 2.8.0 uses insufficient entropy, and thus hash flooding can occur via a crafted XML document.2.9 0.0040 None reported
Routine CVE-2026-76641 expat: Expat through 2.8.3 contains an out-of-bounds read vulnerability that allows attackers to trigger memory corruption b...n/a 0.0035 None reported
Routine CVE-2026-72522 libexpat before 2.8.3 has an out-of-bounds read and resultant infinite loop because low surrogates are treated the same as high surrogates during Unicode processing in the *_toUtf16 functions.6.2 0.0019 None reported
Routine CVE-2026-50219 libexpat before 2.8.2 lacks handler call depth tracking for calls to XML_GetBuffer, XML_Parse, XML_ParseBuffer, XML_ParserFree, or XML_ParserReset from within handlers in cases of a policy violation. Thus, a use-after-free can occur,6.9 0.0018 None reported
Routine CVE-2026-56412 libexpat before 2.8.2 does not consider XML_TOK_DATA_CHARS in doCdataSection and thus lacks handler call depth tracking for various calls from within handlers in cases of a policy violation. Thus, a use-after-free can occur. NOTE: this issue exists because of an incomplete fix for CVE-2026-50219.5.9 0.0018 None reported
Routine CVE-2026-56131 libexpat before 2.8.2 lacks handler call depth tracking for calls to XML_ResumeParser from within handlers in cases of a policy violation. Thus, a use-after-free can occur (similar to the CVE-2026-50219 situation).4.9 0.0018 None reported
Routine CVE-2026-56406 libexpat before 2.8.2 has an integer overflow in XML_ParseBuffer because it lacked a check that was present in XML_Parse.6.9 0.0017 None reported
Routine CVE-2026-56407 libexpat before 2.8.2 has an integer overflow in doProlog that is related to storeEntityValue and entity textLen.6.9 0.0017 None reported
Routine CVE-2026-56132 In libexpat before 2.8.2, there is a heap-based buffer overflow in doProlog in xmlparse.c because scaffold backing array reallocation is mishandled when there is data-structure sharing across parsers.6.9 0.0014 None reported
Routine CVE-2026-56410 xmlwf in libexpat before 2.8.2 has an integer overflow in resolveSystemId.6.9 0.0013 None reported
Routine CVE-2026-56411 xmlwf in libexpat before 2.8.2 has an integer overflow in endDoctypeDecl via NOTATION declarations.6.9 0.0013 None reported
Routine CVE-2026-56408 expat: libexpat before 2.8.2 has an integer overflow in copyString.6.9 0.0013 None reported
Routine CVE-2026-56409 xmlwf in libexpat before 2.8.2 has an integer overflow for the output filename when -d outputDir is used.6.5 0.0012 None reported
Showing 1 to 17 of 17 1

Patch Radar data is free to use with attribution. Terms and how to credit it.

Product names, logos and trademarks shown on Patch Radar belong to their respective owners. They are used only to identify the software each security fix applies to and to help readers find their platform. Their use does not imply any affiliation with, or endorsement by, those owners, and Patchblox is not affiliated with any of them.