@kevin it was filed *before* the actual 38545 CVE had been made public though