Linux · Ubuntu · Package update · January 16, 2026

libexpat1 2.4.3-1: libexpat1 2.4.3-1 for Ubuntu 25.04 (plucky)

libexpat1 2.4.3-1, released January 16, 2026, fixes 8 CVEs in libexpat1. None of them is reported as exploited. Patch Radar priority: High. The product is no longer supported.

HighUnsupported product
CVEs closed
8
None rated Critical
Exploited
0
None reported
Highest CVSS
9.8
Base score, 0 to 10
Highest EPSS
0.0548
92nd percentile

Priority of the 8 CVEs

Patch now 0 Urgent 0 High 8 Routine 0

Fixed package versions

ProductReleaseFixed in
libexpat1Ubuntu 25.04 (plucky)2.4.3-1

CVEs this fix closes

PriorityCVETitleCVSSEPSSExploitation
High CVE-2022-22822 xul-ext-lightning: addBinding in xmlparse.c in Expat (aka libexpat) before 2.4.3 has an integer overflow.9.8 0.0548 None reported
High CVE-2021-45960 expat: In Expat (aka libexpat) before 2.4.3, a left shift by 29 (or more) placesin the storeAtts function in xmlparse.c can...9.8 0.0467 None reported
High CVE-2021-46143 expat: In doProlog in xmlparse.c in Expat (aka libexpat) before 2.4.3, an integeroverflow exists for m_groupSize.9.8 0.0447 None reported
High CVE-2022-22823 thunderbird-mozsymbols: build_model in xmlparse.c in Expat (aka libexpat) before 2.4.3 has an integer overflow.9.8 0.0387 None reported
High CVE-2022-22824 expat: defineAttribute in xmlparse.c in Expat (aka libexpat) before 2.4.3 has an integer overflow.9.8 0.0387 None reported
High CVE-2022-22826 libxmltok1: nextScaffoldPart in xmlparse.c in Expat (aka libexpat) before 2.4.3 has an integer overflow.9.8 0.0318 None reported
High CVE-2022-22827 thunderbird-gnome-support: storeAtts in xmlparse.c in Expat (aka libexpat) before 2.4.3 has an integer overflow.9.8 0.0318 None reported
High CVE-2022-22825 libxmltok1: lookup in xmlparse.c in Expat (aka libexpat) before 2.4.3 has an integer overflow.9.8 0.0299 None reported
Showing 1 to 8 of 8 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.