The Adobe patch for CVE-2022-24086 wasn’t enough to mitigate the code. This led to a new CVE-2022-24087 being raised and a second patch going into production.