apk package
wolfi/expat
pkg:apk/wolfi/expat
Vulnerabilities (26)
| CVE | Sev | CVSS | KEV | Affected versions | Fixed in | Published | Description |
|---|---|---|---|---|---|---|---|
| CVE-2026-56412 | Med | 4.9 | < 2.8.2-r0 | 2.8.2-r0 | Jun 21, 2026 | 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 fo | |
| CVE-2026-56411 | Med | 6.9 | < 2.8.2-r0 | 2.8.2-r0 | Jun 21, 2026 | xmlwf in libexpat before 2.8.2 has an integer overflow in endDoctypeDecl via NOTATION declarations. | |
| CVE-2026-56410 | Med | 6.9 | < 2.8.2-r0 | 2.8.2-r0 | Jun 21, 2026 | xmlwf in libexpat before 2.8.2 has an integer overflow in resolveSystemId. | |
| CVE-2026-56409 | Med | 6.5 | < 2.8.2-r0 | 2.8.2-r0 | Jun 21, 2026 | xmlwf in libexpat before 2.8.2 has an integer overflow for the output filename when -d outputDir is used. | |
| CVE-2026-56408 | Med | 6.9 | < 2.8.2-r0 | 2.8.2-r0 | Jun 21, 2026 | libexpat before 2.8.2 has an integer overflow in copyString. | |
| CVE-2026-56405 | Med | 6.9 | < 2.8.2-r0 | 2.8.2-r0 | Jun 21, 2026 | libexpat before 2.8.2 has an integer overflow in getAttributeId. | |
| CVE-2026-56404 | Med | 6.9 | < 2.8.2-r0 | 2.8.2-r0 | Jun 21, 2026 | libexpat before 2.8.2 has an integer overflow in addBinding. | |
| CVE-2026-56403 | Med | 6.9 | < 2.8.2-r0 | 2.8.2-r0 | Jun 21, 2026 | libexpat before 2.8.2 has an integer overflow in storeAtts. | |
| CVE-2026-56132 | Med | 6.9 | < 2.8.2-r0 | 2.8.2-r0 | Jun 19, 2026 | 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. | |
| CVE-2026-50219 | Med | 4.9 | < 2.8.2-r0 | 2.8.2-r0 | Jun 4, 2026 | 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, | |
| CVE-2026-45186 | Low | 2.9 | < 2.8.1-r0 | 2.8.1-r0 | May 10, 2026 | 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. | |
| CVE-2026-41080 | Low | 2.9 | < 2.8.0-r0 | 2.8.0-r0 | Apr 16, 2026 | libexpat before 2.8.0 uses insufficient entropy, and thus hash flooding can occur via a crafted XML document. | |
| CVE-2026-32778 | Low | 2.9 | < 2.7.5-r0 | 2.7.5-r0 | Mar 16, 2026 | libexpat before 2.7.5 allows a NULL pointer dereference in the function setContext on retry after an earlier ouf-of-memory condition. | |
| CVE-2026-32777 | Med | 4.0 | < 2.7.5-r0 | 2.7.5-r0 | Mar 16, 2026 | libexpat before 2.7.5 allows an infinite loop while parsing DTD content. | |
| CVE-2026-32776 | Med | 4.0 | < 2.7.5-r0 | 2.7.5-r0 | Mar 16, 2026 | libexpat before 2.7.5 allows a NULL pointer dereference with empty external parameter entity content. | |
| CVE-2026-25210 | Med | 6.9 | < 2.7.4-r0 | 2.7.4-r0 | Jan 30, 2026 | In libexpat before 2.7.4, the doContent function does not properly determine the buffer size bufSize because there is no integer overflow check for tag buffer reallocation. | |
| CVE-2026-24515 | Low | 2.9 | < 2.7.4-r0 | 2.7.4-r0 | Jan 23, 2026 | In libexpat before 2.7.4, XML_ExternalEntityParserCreate does not copy unknown encoding handler user data. | |
| CVE-2025-59375 | Hig | 7.5 | < 2.7.2-r0 | 2.7.2-r0 | Sep 15, 2025 | libexpat in Expat before 2.7.2 allows attackers to trigger large dynamic memory allocations via a small document that is submitted for parsing. | |
| CVE-2024-8176 | Hig | 7.5 | < 2.7.0-r0 | 2.7.0-r0 | Mar 14, 2025 | A stack overflow vulnerability exists in the libexpat library due to the way it handles recursive entity expansion in XML documents. When parsing an XML document with deeply nested entity references, libexpat can be forced to recurse indefinitely, exhausting the stack space and c | |
| CVE-2024-50602 | Med | 5.9 | < 2.6.4-r0 | 2.6.4-r0 | Oct 27, 2024 | An issue was discovered in libexpat before 2.6.4. There is a crash within the XML_ResumeParser function because XML_StopParser can stop/suspend an unstarted parser. |
- affected < 2.8.2-r0fixed 2.8.2-r0
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 fo
- affected < 2.8.2-r0fixed 2.8.2-r0
xmlwf in libexpat before 2.8.2 has an integer overflow in endDoctypeDecl via NOTATION declarations.
- affected < 2.8.2-r0fixed 2.8.2-r0
xmlwf in libexpat before 2.8.2 has an integer overflow in resolveSystemId.
- affected < 2.8.2-r0fixed 2.8.2-r0
xmlwf in libexpat before 2.8.2 has an integer overflow for the output filename when -d outputDir is used.
- affected < 2.8.2-r0fixed 2.8.2-r0
libexpat before 2.8.2 has an integer overflow in copyString.
- affected < 2.8.2-r0fixed 2.8.2-r0
libexpat before 2.8.2 has an integer overflow in getAttributeId.
- affected < 2.8.2-r0fixed 2.8.2-r0
libexpat before 2.8.2 has an integer overflow in addBinding.
- affected < 2.8.2-r0fixed 2.8.2-r0
libexpat before 2.8.2 has an integer overflow in storeAtts.
- affected < 2.8.2-r0fixed 2.8.2-r0
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.
- affected < 2.8.2-r0fixed 2.8.2-r0
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,
- affected < 2.8.1-r0fixed 2.8.1-r0
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.
- affected < 2.8.0-r0fixed 2.8.0-r0
libexpat before 2.8.0 uses insufficient entropy, and thus hash flooding can occur via a crafted XML document.
- affected < 2.7.5-r0fixed 2.7.5-r0
libexpat before 2.7.5 allows a NULL pointer dereference in the function setContext on retry after an earlier ouf-of-memory condition.
- affected < 2.7.5-r0fixed 2.7.5-r0
libexpat before 2.7.5 allows an infinite loop while parsing DTD content.
- affected < 2.7.5-r0fixed 2.7.5-r0
libexpat before 2.7.5 allows a NULL pointer dereference with empty external parameter entity content.
- affected < 2.7.4-r0fixed 2.7.4-r0
In libexpat before 2.7.4, the doContent function does not properly determine the buffer size bufSize because there is no integer overflow check for tag buffer reallocation.
- affected < 2.7.4-r0fixed 2.7.4-r0
In libexpat before 2.7.4, XML_ExternalEntityParserCreate does not copy unknown encoding handler user data.
- affected < 2.7.2-r0fixed 2.7.2-r0
libexpat in Expat before 2.7.2 allows attackers to trigger large dynamic memory allocations via a small document that is submitted for parsing.
- affected < 2.7.0-r0fixed 2.7.0-r0
A stack overflow vulnerability exists in the libexpat library due to the way it handles recursive entity expansion in XML documents. When parsing an XML document with deeply nested entity references, libexpat can be forced to recurse indefinitely, exhausting the stack space and c
- affected < 2.6.4-r0fixed 2.6.4-r0
An issue was discovered in libexpat before 2.6.4. There is a crash within the XML_ResumeParser function because XML_StopParser can stop/suspend an unstarted parser.
Page 1 of 2