Everything checked, everything updated. What happened behind the scenes this week.

The best work is invisible. This week we didn't build anything on lottoprognose.ch that you can see. No new feature, no new design. Instead, something more important: We updated everything, verified it, and republished. Normally nobody writes about this. We do – because for us, trust isn't just about odds and statistics. What happened On October 21, 2026 , the Node.js project released security updates. Node.js is the runtime environment our platform runs on. A total of ten vulnerabilities were closed, spread across the version lines 22.x, 24.x, and 26.x . Two areas were particularly relevant: Compressed data Brotli . An error in the decoder could, when processing manipulated compressed data, lead to a memory access outside the intended range. Classified as the most severe of the ten vulnerabilities. HTTPS certificate validation. Several vulnerabilities allowed, under certain conditions, bypassing the validation of hostnames in certificates – for example when IP addresses were present in unusual notation. The matter with the certificates In parallel, it became known that signature keys of the certificate provider eMudhra had been compromised . Affected software could thereby have accepted forged HTTPS certificates as genuine. Said honestly, because context is part of the truth: to exploit this, an attacker would have additionally had to intercept or redirect an application's outbound traffic. That is a high hurdle – but one you don't leave standing. Our platform runs on a secure server. There, the base image was adjusted so that the affected certificate chains are rejected. Certain project types had to be republished for this. That is exactly what we did – completely and for all services. What this means for you Nothing to do. No new password, no new app version, no action required. After our review, there are no indications that user data was affected. According to public information, no attacks in the wild have been observed for the reported vulnerabilities to date. We didn't wait until something happened. We updated because an update was released. That's how it should be. Why we're writing about this Because it would have been easy not to. Nobody would have noticed if we had stayed silent. But we tell you the uncomfortable truth about winning chances – so we tell it to you about your data as well. Your data belongs to you. Our job is to treat it as if it were our own. And that includes installing updates before anyone asks for them. → To your account https://lottoprognose.ch/auth?tab=register The next draw will take place as usual. We wish you good luck. 🍀