It was indeed a false positive, I let you have a look there for the details.
For information, both tickets created are already fixed.
As a side note, reporting the issue here was a good move (thanks again for that!), however, I would not advise using a workaround when facing false positive, but to resolve it as false positive/won’t fix.