Chrome 86 is being reported as out of date

I have a site running the following config:

    var $buoop = {
        required: { e:-4,f:-5,o:-5,s:-2,c:-6 },
        insecure: true,
        api: 2020.11,
    };

Which is throwing this:

I have tested setting insecure: false and removing Chrome from the browsers list all together. No change. Any ideas?

[josselex]

@FrankySnow Thanks! This seems to be the reason. I will correct this.

[FrankySnow]

On my two Chrome 86 (both Android and Windows), the debug info shows “Reasons to show: no vendor support” so I had to set unsupported: false. This feels wrong to me, as the vulnerability doesn’t mean that the browser has no vendor support…

Edit : further investigation shows that this vulnerability has been patched in 86.0.4240.111 more than one month ago and that it affected only Chrome desktop so tagging all Chrome 86 insecure or unsupported seems incorrect.