The issue is related to the use of memory after it has been freed, specifically when removing an XSLT parameter during processing, which could lead to an exploitable use-after-free. There have been reports of attacks in the wild abusing this flaw, allowing a remote attacker to potentially execute arbitrary code.