The issue is related to the incorrect object lifecycle in the PDFium component of Google Chrome, which can lead to heap corruption. This can be exploited by a remote attacker using a specially crafted PDF file, potentially allowing the execution of arbitrary code.