Astonishingly, the private keys were 4, 56, 66, 115, 155, 156, 230, 237.

exploiting compromised certificates requires an active adversary-in-the-middle attack, meaning the attacker must act as a proxy between two TLS parties and receive encrypted traffic, decrypt it, reencrypt it, and send it to the other party. Such capabilities, in some cases, are usually limited to only the most well-resourced attackers. People with control of a local network—at a coffee shop, university, or other organization—face much less of a challenge.

https://emudhra.we-have-a-problem.com/

Xkcd 221: int getRandomNumber() { return 4; // chosen by fair dice roll. guaranteed to be random. }

you are viewing a single comment's thread
view the rest of the comments
[–] 169 points 3 days ago (35 children)

Okay, that's fun and scary at the same time.

The article links to a webpage,

https://emudhra.we-have-a-problem.com/

That shows if your browser is still using those certs, and though it says Firefox has already updated, maybe it hasn't reached mobile yet as it shows I'm using them all still.

I guess I won't connect to anything important for a few days.

  • source
  • hideshow 35 child comments
  • [–] 74 points 3 days ago (8 children)

    My Firefox mobile got green ✅

    Maybe try manually updating through the app store

  • source
  • parent
  • hideshow 8 child comments
  • [–] 6 points 3 days ago* (5 children)

    What's odd is that I have auto updates disabled for Firefox on my spare phone, and I still show green on everything. I don't think it's updated in a couple months now.

  • source
  • parent
  • hideshow 5 child comments
  • [–] 4 points 3 days ago

    There are no entries in the certificate transparency logs for these intermediates in that period, indicating that CT-enforcing clients like Firefox, Chrome, Edge and Safari could not have been attacked.

  • source
  • parent
  • [–] 16 points 3 days ago (5 children)

    Useful link, thanks.

    Mobile Waterfox passes.

  • source
  • parent
  • hideshow 5 child comments
  • [–] 1 point 2 days ago (2 children)

    Interesting. I'm also using Waterfox and getting all red on my end.

  • source
  • parent
  • hideshow 2 child comments
  • [–] [S] 1 point 3 days ago* (1 child)

    is the post body having issues displaying? asking because this is way past the first time this season i've seen people not see it

  • source
  • parent
  • hideshow 1 child comment
  • [–] 5 points 3 days ago* (last edited 3 days ago) (3 children)

    For mobile

    • Vanadium 155.0.8059.84 (config 217) on GrapheneOS connects to 6/12 0/12. Last updated 2026-10-17
    • Fennec 158.0.0 (build #1580020) connects to 12/12. Last updated 2026-10-14
    • edited: after I hit 'run again' a couple times Vanadium went 0/12, so hurray. Didn't make a difference to my dear Fennec though.
  • source
  • parent
  • hideshow 3 child comments
  • [–] 4 points 3 days ago (1 child)

    Uhh... Weird. In my phone (Android 15) both Firefox 158.0.1 and Brave 1.97.59 (Chromium 155.0.8059.85) connect to 6 of the 12 hosts.

    But on my tablet (Android 10) I have the same versions of Firefox and Brave, and there they don't connect to any of the hosts.

    What can I do?

  • source
  • parent
  • hideshow 1 child comment
  • [–] 0 points 3 days ago (3 children)

    Do you mean not connecting to anything? Because that would be the action if you considered this a threat

  • source
  • parent
  • hideshow 3 child comments
  • [–] 3 points 2 days ago (2 children)

    That's... what I said?

    I do consider this a threat. A root certificate being compromised is a big deal. Your web traffic goes across multiple devices before reaching its intended destination, and if any one of them are compromised they could successfully perform an invisible man in the middle attack of your browser/app keeps trusting those certificates.

  • source
  • parent
  • hideshow 2 child comments
  • [–] 1 point 2 days ago (1 child)

    Ssl is pretty useful, yeah, but those that were mass unlocked with a gimmick key were already very insecure and at this moment they are revoked. Either way, aren't you supposed to be locked in now?

  • source
  • parent
  • hideshow 1 child comment
  • [–] 2 points 2 days ago*

    That only applies to applications and services that support remote certificate revocation.

    Those certificates were still in use until Firefox offered another update this morning, but that's just the browser. Every company and their little bastard love child wants you to use an app to connect to their services, how many of those apps support automatic certificate revocation?

    Any app on your phone that doesn't is now vulnerable to being compromised invisibly. A successful MITM attack looks like nothing at all. The attacker decrypts the traffic with the compromised certificate's secret to snoop in on the secrets (like username and password) and re-encrypts it to send it forward so the destination server doesn't know any different either.

    Now that it's public knowledge, I guarantee someone is trying to capitalize on it right now.

    How certain are you that not a single switch between you and your bank's website is fully secured?

  • source
  • parent