There is a known issues with Firefox for Android, as it gets the CRL less reliably. Should also be fixed by force-refreshing the PlayStore to search for a full app updates. We are investigating.
I am on Firefox Mobile 158.0.1, with a build date of 2026-10-19T18:58:56, which I just updated through the Play Store and which still connects to the test sites.
I can confirm that upgrading to 158.0.2 fixed it for me (I tested right before the update and it was still trusting the corresponding CA, and after updating it doesn’t anymore).
I thought 158.0.1 is supposed to have the knowledge of these certificate revocations hard-coded? Maybe I misunderstood what the point of the browser update was.
I installed 158.0.1, restarted my phone, opened the website, waited long enough that the screen of my phone turns off, then reloaded the page. It still says “connected”.
FWIW my Firefox Nightly on Android, with build date 2026-10-20T09:59:29, also fails (i.e. it connects). Seemingly based on the build date it should be up-to-date? Let me know if you want an actual bug report.
We found the bug. Firefox for Android needs 1-15sec of being alive to fetch the block list. So it might not work when you open the test page directly from another app.
We have another browser fix coming in. But as a workaround, keep Firefox open for a bit.
Even after multiple minutes of the browser being alive, I’m still seeing insecure requests to emSign Root TLS CA - G3 go through. Fennec Nightly build date 2026-10-21T09:22:54. AAA Certificate Services is now blocked though.
Ah sorry, I forgot Fennec was also the name of a fork so my comment was ambiguous. I meant it as the original Firefox for Android codename, not the fork. I’m running an official Mozilla build of Firefox for Android Nightly.
Edit to add: 2026-10-22T08:45:08 reports everything secure though. Thanks for all y’all’s work on this!
There is a known issues with Firefox for Android, as it gets the CRL less reliably. Should also be fixed by force-refreshing the PlayStore to search for a full app updates. We are investigating.
score 2 · canonical
yup, after phone os update, play store update, ff app update, and reboot… still not seeing the fix.
score 1 · canonical
I am on Firefox Mobile 158.0.1, with a build date of 2026-10-19T18:58:56, which I just updated through the Play Store and which still connects to the test sites.
UPDATE: Restarting my phone resolved it.
score 1 · canonical
I’m also on
158.0.1(Samsung Galaxy S26 Ultra, Android 17) and restarting my phone didn’t fix it.score 1 · canonical
Thanks for the message. We found the bug. See response above.
score 1 · canonical
I can confirm that upgrading to
158.0.2fixed it for me (I tested right before the update and it was still trusting the corresponding CA, and after updating it doesn’t anymore).score 1 · canonical
I thought 158.0.1 is supposed to have the knowledge of these certificate revocations hard-coded? Maybe I misunderstood what the point of the browser update was.
I installed 158.0.1, restarted my phone, opened the website, waited long enough that the screen of my phone turns off, then reloaded the page. It still says “connected”.
score 1 · canonical
Yeah there was another independent bug. You should update to
.2score 1 · canonical
That finally fixed it, thanks :)
score 1 · canonical
FWIW my Firefox Nightly on Android, with build date
2026-10-20T09:59:29, also fails (i.e. it connects). Seemingly based on the build date it should be up-to-date? Let me know if you want an actual bug report.score 2 · canonical
We found the bug. Firefox for Android needs 1-15sec of being alive to fetch the block list. So it might not work when you open the test page directly from another app.
We have another browser fix coming in. But as a workaround, keep Firefox open for a bit.
score 1 · canonical
Even after multiple minutes of the browser being alive, I’m still seeing insecure requests to
emSign Root TLS CA - G3go through. Fennec Nightly build date2026-10-21T09:22:54.AAA Certificate Servicesis now blocked though.score 1 · canonical
Fennec is not Firefox for Android but a fork. Please report to them.
score 1 · canonical
Ah sorry, I forgot Fennec was also the name of a fork so my comment was ambiguous. I meant it as the original Firefox for Android codename, not the fork. I’m running an official Mozilla build of Firefox for Android Nightly.
Edit to add:
2026-10-22T08:45:08reports everything secure though. Thanks for all y’all’s work on this!score 1 · canonical
Great to hear it’s finally working for you
score 1 · canonical