libexpat before commit 13c5f63 contains a heap buffer over-read vulnerability in xmlparse.c. XML_ParseBuffer advances the parse buffer end with parser->m_bufferEnd += len using a caller-supplied length that is not validated against the allocated buffer size, so repeated XML_ParseBuffer calls move m_bufferEnd past the end of the heap allocation and subsequent parsing reads out of bounds. Reaching this path requires a parse buffer to already be present; otherwise XML_ParseBuffer returns XML_ERROR_NO_BUFFER. A buffer is present after a prior call to XML_GetBuffer, either directly (the common case) or indirectly through a prior XML_Parse call that allocates the buffer internally. The over-read discloses adjacent heap memory to the calling application, recovering heap pointers, libc function pointers, and code pointers sufficient to defeat ASLR and build further exploitation primitives.
Fix
Microsoft's update · Important
- Release Notes — azl3 expat 2.8.3-2 on Azure Linux 3.0 · build 2.9.0-1
From the 2026-Oct release note of Microsoft's Security Update Guide, revised 2026-10-28.
Every line above is quoted from NVD, CISA, Microsoft, the vendor's own advisory or DISA; nothing is generated.
Change history 2
- StatusAwaiting Analysis → PublishedNVD modified 2026-10-27 10:14
- First seenCVSS 8.3NVD modified 2026-10-10 03:17
Affected (CPE criteria) 0
NVD has not attached CPE configurations yet.