CVE-2026-111132
Description
GNOME libgxps through 0.3.2 contains a heap out-of-bounds read in path_geometry_start_element() that allows attackers to read past allocations via crafted PolyBezierSegment or PolyQuadraticBezierSegment Points attributes. Attackers can supply a point count not divisible by three or two in a crafted XPS document to crash consumers like Evince and render adjacent heap memory into output.
Predictions
Heuristic predictions, AS-IS, for prioritization only.
Mitigations
No mitigations published for this CVE yet.
The vendor-content worker queues fetches as references arrive (check back in a few minutes). Or — if you've already worked around this in production — publish your fix to the community-verified tier.
Propose a mitigation on Community Mitigations published via the community go through AI scoring + 2 human reviewers + 7-day silent objection window before landing here withsource_tier=community-verified.
References
- https://gitlab.gnome.org/GNOME/libgxps
- https://gitlab.gnome.org/GNOME/libgxps/-/blob/f5027ed09c767e8a02e652fbc77dcea79e19e10d/libgxps/gxps-path.c#L776-L785
- https://gitlab.gnome.org/GNOME/libgxps/-/blob/f5027ed09c767e8a02e652fbc77dcea79e19e10d/libgxps/gxps-path.c#L832-L848
- https://hackmd.io/@haind-pwn/libgxps-poly-segment-points-arity-oob-read
- https://www.vulncheck.com/advisories/gnome-libgxps-through-0.3.2-heap-out-of-bounds-read-via-path-geometry-start-element
CWEs
CWE-125
Community-verified mitigations for this CVE will appear above when contributors publish them.
Verify integrity in audit chain (admin only). AS-IS.