How we discovered CVE-2025-55182 and what happened in the aftermath