this post was submitted on 20 Oct 2026
964 points (99.7% liked)

Technology

88987 readers
2942 users here now

This is a most excellent place for technology news and articles.


Our Rules


  1. Follow the lemmy.world rules.
  2. Only tech related news or articles.
  3. Be excellent to each other!
  4. Mod approved content bots can post up to 10 articles per day.
  5. Threads asking for personal tech support may be deleted.
  6. Politics threads may be removed.
  7. No memes allowed as posts, OK to post as comments.
  8. Only approved bots from the list below, this includes using AI responses and summaries. To ask if your bot can be added please contact a mod.
  9. Check for duplicates before posting, duplicates may be removed
  10. Accounts 7 days and younger will have their posts automatically removed.

Approved Bots


founded 3 years ago
MODERATORS
 

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
[–] BluescreenOfDeath@lemmy.world 171 points 1 day ago (15 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.

[–] thisbenzingring@lemmy.today 76 points 1 day ago (3 children)

My Firefox mobile got green ✅

Maybe try manually updating through the app store

Mine showed red, but after updating it now shows all green

[–] damnthefilibuster@lemmy.world 14 points 1 day ago

In app safari on Mlem got all greens.

[–] zikzak025@lemmy.world 7 points 1 day ago* (last edited 1 day ago) (4 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.

[–] gex@lemmy.world 49 points 1 day ago

Firefox can push certificate revocation updates without having to push a new browser build

https://hacks.mozilla.org/2025/08/crlite-fast-private-and-comprehensive-certificate-revocation-checking-in-firefox/

[–] MangoPenguin@piefed.social 13 points 1 day ago

I think cert updates happen automatically on their own without the browser needing to be updated.

[–] Redjard@reddthat.com 5 points 1 day 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.

[–] thisbenzingring@lemmy.today 1 points 1 day ago (1 children)
[–] zikzak025@lemmy.world 3 points 1 day ago

That one is on version 154.0, dated August.

[–] tuckerm@feddit.online 16 points 1 day ago (2 children)

Useful link, thanks.

Mobile Waterfox passes.

[–] redwattlebird@thelemmy.club 1 points 1 day ago (1 children)

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

[–] tuckerm@feddit.online 1 points 18 hours ago (1 children)
[–] redwattlebird@thelemmy.club 2 points 16 hours ago

1.2.9 for me. Seems like I might have to revert to the older one.

[–] Aatube@lemmy.dbzer0.com 1 points 1 day ago* (last edited 1 day ago) (1 children)

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

[–] tuckerm@feddit.online 4 points 1 day ago

It's displaying fine for me, I think I was just scrolling quickly on my phone and didn't notice that the https://emudhra.we-have-a-problem.com/ link in the body was different from the linked article. I saw a blockquote in the post body, and figured that the URL beneath the quote was a link to the article.

[–] Dnb@lemmy.dbzer0.com 1 points 1 day ago

Update mobile Firefox it should be fixed now

[–] Davel23@fedia.io 14 points 1 day ago

I'm using Firefox and that site says I'm good.

Yep, my Firefox mobile hasn't updated yet either, gonna see if there's an update I can grab.

[–] kazerniel@quokk.au 1 points 1 day ago

I'm getting "⚠️ Inconclusive (timed out)" on Firefox 👀

[–] bazzett@lemmy.world 5 points 1 day ago (1 children)

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?

[–] Gerudo@lemmy.zip 1 points 1 day ago

Odd my mobile Brave rejects all.

[–] cheeseburger@lemmy.ca 5 points 1 day ago* (last edited 1 day ago) (2 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.
[–] floofloof@lemmy.ca 5 points 1 day ago* (last edited 1 day ago) (1 children)

My Vanadium just refused all 12 connections. But maybe some of the DNS blocking or Suricata on my LAN might have helped.

[–] cheeseburger@lemmy.ca 2 points 1 day ago

Thanks, I tried harder and got the same result as you. Edited my comment above to reflect.

[–] IronKrill@lemmy.ca 2 points 1 day ago

I just recently swapped to Fennec and it's correctly getting 0/12. These updates seem a bit inconsistent.

[–] lemmyng@lemmy.world 4 points 1 day ago

Ironfox is all green for me.

Cromite is half red, half green.

So yeah, fuck Chromium's monopoly.

[–] KeenFlame@feddit.nu 1 points 1 day ago (1 children)

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

[–] BluescreenOfDeath@lemmy.world 3 points 1 day ago (1 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.

[–] KeenFlame@feddit.nu 1 points 1 day ago (1 children)

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?

[–] BluescreenOfDeath@lemmy.world 2 points 1 day ago* (last edited 1 day 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?

[–] ArgentRaven@lemmy.world 4 points 1 day ago* (last edited 1 day ago)

I'm on a 10/7 build and I'm vulnerable on mobile FireFox, as well.

Edit: updated to a 10/19 version, 158.0.1, and it's still vulnerable.

[–] masterofn001@lemmy.ca 2 points 1 day ago

Are you using a vpn/tor?

[–] im_fine_sandy@nord.pub 1 points 1 day ago

WDYM you're still using them all?

You don't have e any green ticks?

[–] Nurse_Robot@lemmy.world -1 points 1 day ago

Brave Mobile is green ✅