Chrome 143 fixes 13 security vulnerabilities, including four high-severity flaws, in a December desktop update rolling out to Windows, macOS, and Linux users.
The post Google Rolls Out Chrome 143 Update for Billions Worldwide appeared first on TechRepublic.
Chrome 143 fixes 13 security vulnerabilities, including four high-severity flaws, in a December desktop update rolling out to Windows, macOS, and Linux users.
The post Google Rolls Out Chrome 143 Update for Billions Worldwide appeared first on TechRepublic.
AI browsers introduce reasoning-based risks. Learn how cross-origin AI agents dismantle web security and what defenses are needed.
The post Convenience or Catastrophe? The Dangers of AI Browsers No One is Talking About appeared first on Security Boulevard.
The Tor Project is fundamentally changing its release schedule for the Alpha channel, switching it from the Firefox Extended Support Release base to the much faster Rapid Release cadence. This will come with real consequences for both testers and stable users.
It’s likely that Hackaday readers have among them a greater than average number of people who can name one special thing they did on September 23rd, 2002. On that day a new web browser was released, Phoenix version 0.1, and it was a lightweight browser-only derivative of the hugely bloated Mozilla suite. Renamed a few times to become Firefox, it rose to challenge the once-mighty Microsoft Internet Explorer, only to in turn be overtaken by Google’s Chrome.
Now in 2025 it’s a minority browser with an estimated market share just over 2%, and it’s safe to say that Mozilla’s take on AI and the use of advertising data has put them at odds with many of us who’ve kept the faith since that September day 23 years ago. Over the last few months I’ve been actively chasing alternatives, and it’s with sadness that in November 2025, I can finally say I’m Firefox-free.
It was perhaps inevitable that Firefox would lose market share when faced with a challenger from a player with the economic muscle of Google. Chrome is everywhere, it’s the default browser in Android and ChromeOS, and when stacked up against the Internet Explorer of fifteen years or so ago it’s not difficult to see why it made for an easy switch. Chrome is good, it’s fast and responsive, it’s friendly, and the majority of end users either don’t care or don’t know enough to care that it’s Google’s way in to your data. When it first appeared, they still had the “Don’t be evil” aura to them, even if perhaps behind the warm and fuzzy feeling it had already worn away in the company itself.
If Firefox were destined to become a minority player then it could still be a successful one; after all, 2% of the global browser market still represents a huge number of users whose referrals to search engines return a decent income. But the key to being a success in any business is to know your customers, and sitting in front of this particular screen it’s difficult to escape the conclusion that Mozilla have lost touch with theirs. To understand this it’s necessary for all of us to look in the mirror and think for a moment about who uses Firefox.
A quick straw poll in my hackerspace revealed a majority of Firefox users, while the same straw poll among another group of my non-hackerspace friends revealed none. The former used Firefox because of open-source vibes, while the latter used Edge or Safari because it came with their computer, or Chrome on their phone and on their desktop because of Google services. Hackaday is not a global polling organisation, but we think it’s likely that the same trend would reveal itself more widely. If you’re in the technology space you might use Firefox, but if you aren’t you may not even have heard of it in 2025. It’s difficult to see that changing any time soon, to imagine some killer feature that would make those Chrome, Safari, and Edge users care enough to switch to Firefox.
To service and retain this loyal userbase then, you might imagine that Mozilla would address their needs and concerns with what made Phoenix a great first version back in 2002. A lightweight and versatile standards-compliant and open-source web browser with acceptable privacy standards, and without any other non-browser features attached to it. Just a browser, only a browser, and above all, a fast browser.
Instead, Mozilla appear to be following a course calculated to alarm rather than retain these users. Making themselves an AI-focused organisation, neglecting their once-unbeatable developer network, and trying to sneak data gathering into their products. They appear now to think of themselves as a fad-driven Valley startup rather than the custodians of a valuable open-source package, and unsurprisingly this is concerning to those of us who know something about what a browser does behind the scenes.
It is likely that I am preaching to the choir here, but it’s important that there be a plurality of browsers in the world. And by that I mean not just a plurality of front-ends, but a plurality of browser engines. One of the reasons Phoenix appeared all those years ago was to challenge the dominance of Microsoft Internet Explorer, the tool by which the Redmond software company were trying to shape the online world to their tune. If you remember the browser wars of that era, you’ll have tales of incompatibilities seemingly baked in on purpose to break the chances of an open Web, and we were all poorer for it. Writing Javascript with a range of sections to deal with the quirks of different browser families is now largely a thing of the past, and for that you have the people who stuck with Firefox in the 2000s to thank.
The fear is that here in 2025 we are in an analogous situation to the early 2000s, with Google replacing Microsoft. Such is the dominance of Google Chrome and the WebKit-derived Blink engine which powers it, that in effect, Google have immense power to shape the Web just as Microsoft did back in the day. Do you trust them to live up to their now-retired mission statement and not be evil? We can’t say we do. Thus Firefox’s Gecko browser engine is of crucial importance, representing as it does the only any-way serious challenger to Blink and WebKit’s near-monopoly. That it is now tied to a Mozilla leadership treating it in so cavalier a manner does not bode well for the future of the Web.
So I’ve set out my stand here, that after twenty-three years, I’m ready to abandon Firefox. It’s not a decision that has been easy, because it’s important for all of us that there be a plurality of browsers, but such is the direction being taken by Mozilla that I am not anxious to sit idly by and constantly keep an eye out for new hidden privacy and AI features to turn off with obscure checkboxes. In the following piece I’ll take a look at my hunt for alternatives, and you may be surprised by the one I eventually picked.
If you’re using a recent version of Windows, Microsoft’s Edge browser will “helpfully” make itself your default PDF viewer. You might want to change that default depending on how you feel about the latest news. Microsoft and Adobe have announced that Acrobat will soon be integrated with Edge for enhanced PDF support. Microsoft seems aware of Adobe’s legacy of buggy software living inside browsers, so it’s going out of its way to talk about all the work it’s doing to make sure the new Acrobat feature is secure.
According to Microsoft, replacing its custom PDF stack with Acrobat will mean better colors, sharper graphics, improved performance, and (allegedly) more robust security. Acrobat in Edge will also enable new features like read-aloud narration and more reliable text selection in documents. All these basic capabilities will continue to be free, so you should not notice any loss of functionality as Acrobat support rolls out.
This is not a purely altruistic move by Adobe. Acrobat’s basic features are free, but it also sells premium subscriptions, and it’ll be trying to convert some of Microsoft’s 1.4 billion users to paying customers. A subscription adds features like text and image editing, file conversion, and combining files. The wording of Microsoft’s blog post is a bit vague, but it sounds like there will be an upsell built into Edge’s Acrobat interface. If you upgrade, a browser extension can be used to unlock those features. Those with a pre-existing subscription (starting at $13 per month) will also be able to use the extension to get premium features.
Until a few years ago, Adobe’s Flash platform was integrated with many browsers, but it was a security nightmare. PDF malware exists, but it’s not very common right now. Still, giving Adobe the chance to bungle browser security again is an interesting choice from Microsoft. In a separate blog post, Microsoft explains that it has implemented numerous technical countermeasures like PartitionAlloc (a secure heap implementation) and fuzzing (automated vulnerability testing). Acrobat in Edge will also be included in Microsoft’s bug bounty program, which the company hopes will encourage developers to report issues instead of turning them into exploits.
Edge is a core part of Windows 10 and 11 — you can’t even uninstall it. Microsoft is aware that Windows administrators in managed environments might not want the browser’s PDF handler to change overnight, so the rollout will happen in stages. Managed devices will have to opt-in for now, but the old Edge PDF engine will be discontinued in March 2024. For regular users, you can expect Acrobat to begin appearing in builds of Edge next month.
Now read:
Login