@justus61 @Pixav @opa334 So this is actually an error I didn't notice originally (though others initially didn't notice it either), but basically while Google says it was patched in 17.5, the CVE it associates with it was patched in 17.4... While I suppose it could be that the associated CVE is wrong, more than likely it's probably Google listing the wrong version for some reason (there's other errors there too, though nothing like that that is relevant).