Expat 2.10.0 fixes four security issues in the widely used XML parsing library. Maintainer Sebastian Pipping urges packagers and maintainers of bundled or pinned copies to update. Applications that accept untrusted XML deserve particular attention.

Evidence status: maintainer-reported vulnerabilities and fixes. The release announcement does not report exploitation in the wild. Impact depends on the application and parser configuration.

What changed

The 2.10.0 changelog lists four fixes:

  • CVE-2026-113351: An application that reuses a parser with XML_ParserReset could reject subsequent documents because retained allocations were charged against the next document. An attacker who controls input could cause denial of service in that workflow.
  • CVE-2026-115506: Some nested-entity inputs consumed excessive processing time before the existing amplification checks rejected them. The fix calculates expansion earlier. The release notes warn that compression can reduce the size of an attack input.
  • CVE-2026-117610: Initial empty, non-final calls to a subparser could crash; Pipping says the impact could extend beyond denial of service.
  • CVE-2026-118370: The release protects counters in storeAtts from signed integer overflow.

Find the copy your application actually uses

Update to Expat 2.10.0 or a distributor’s package containing the relevant backported fixes. Check the distributor’s advisory rather than relying only on the upstream version number. Rebuild and redeploy applications or images that bundle or statically link their own copy; updating a system library alone may leave those copies unchanged.

Pipping says 13 known security issues remained unfixed when he published the announcement. The four fixes are worth applying, but this release does not close every known issue. His maintenance work is currently funded by the City of Munich’s open-source sabbatical.