According to this post (https://infosec.pub/post/53919558), Amazon saw this exploited in the wild on the 17th of Oct - ~4 days prior to the coordinated disclosure.

I remember there was an open PR to support the self-hosted backend on their application. I've followed it for years until I gave HabitTrove a change https://habittrove.app.enting.org/

1.Change broswer - Brave was recommended; she's using Zen (a Firefox fork). Personally, I recommend LibreWolf 2. Search engine - DuckDuckGo recommend; she's self-hosting SearchNGX 3. Email - Proton 4. OS - Linux

Not sure I missed something. I fast forwarded

Hello,

Can you detail how you're sending the emails? Where you have to configure the Proton credentials?

Source?

Oh.. OK. Thanks for checking

You might want to listen this https://darknetdiaries.com/episode/172/

This is copy/paste from official blog without even mentioning the source 👎 https://zeek.org/2026/07/the-cure-for-exceptional-zeek-package-testing-part-3/

This is copy/paste from official blog without even mentioning the source 👎 https://zeek.org/2026/07/the-cure-for-exceptional-zeek-package-testing-part-2/

This is copy/paste from official blog without even mentioning the source 👎 https://zeek.org/2026/07/the-cure-for-exceptional-zeek-package-testing-part-1/

Edit: It's the same author

You forgot "/s" on your post.

https://www.removepaywall.com/search?url=https%3A%2F%2Fwww.wired.com%2Fstory%2Fa-critical-deadline-is-approaching-for-windows-and-linux-security%2F