Context of October stable versions
In the second half of October 2026, both Brave and Google released new stable versions of their browsers. Brave 1.97.57 launched on October 14, followed by version 1.97.59 on October 16, while Chrome 155 reached its desktop stable channel on October 13. These dates mark the reference point for evaluating which changes are relevant for end users versus routine maintenance updates.
The update cadence is high: Brave publishes several minor versions per month, while Chrome follows a four-week cycle for its major versions. For the user, the key is not frequency, but identifying whether an update introduces new AI capabilities or verifiable privacy improvements that justify reviewing the configuration.
Integrated AI news: Leo and end-to-end encryption
The most significant news from Brave in this cycle is the privacy reinforcement in Leo, its integrated AI assistant. From October 15, 2026, conversations with Leo are protected with end-to-end encryption and run inside Trusted Execution Environments (TEE) backed by Nvidia. This means that, according to official documentation, not even Brave can read the content of the queries.
Additionally, Brave has incorporated the use of the open-weight model GLM 5.3 Flash for certain Leo interactions. The combination of open models with verifiable trust infrastructure responds to a growing demand from users who want AI in the browser without ceding data to third parties. For the practical user, this implies that sensitive queries (such as financial or personal data) have an additional layer of protection compared to previous versions of the assistant.
Privacy improvements and tracker blocking
On the privacy front, Brave has introduced the Email Aliases feature for free. This tool allows generating alternative email addresses to register on websites without revealing the main email. Messages arrive in the inbox via forwarding, but the site only knows the alias. This feature, highlighted in August 2026, integrates into the navigation flow to reduce personal data exposure.
For its part, Chrome 155 maintains its focus on compatibility and the security of the Blink engine. Although no major changes in the end-user privacy interface are announced in this specific version, the update to Chromium 155 in Brave (and Chrome's common base) includes security fixes and improvements in cookie and tracker handling. The key difference is that Brave offers more granular and visible controls, while Chrome prioritizes stability and universal compatibility.
Technical comparison: Brave 1.97 vs. Chrome 155
Both browsers share the Chromium base, but diverge in additional features. The following table summarizes the verifiable changes in the stable versions of October 2026:
| Feature | Brave 1.97.59 (Oct 16, 2026) | Chrome 155.0.8059.84 (Oct 13, 2026) |
|---|---|---|
| Chromium Base | 155.0.8059.80 | 155.0.8059.84 |
| Integrated AI | Leo with E2E and TEE | Gemini (variable access) |
| Key Privacy | Email Aliases, Tor fix | Standard tracker blocking |
| Main Focus | Privacy and local AI | Compatibility and stability |
The Chromium version in Brave (155.0.8059.80) is slightly older than the stable Chrome version (155.0.8059.84), which is normal given that Brave integrates its own software layers. Brave users get advanced privacy features, while Chrome users access the latest security base of the Blink engine.
Update and compatibility recommendations
If you use Brave, updating to 1.97.59 is recommended to benefit from encryption in Leo and the fix for Tor connection issues. Verify that your third-party extensions are compatible with the new Chromium base, although most Chrome extensions work unchanged in Brave.
For Chrome users, updating to 155 is routine but important due to security fixes. No drastic changes in the user experience are expected, but it is prudent to review cookie settings and website permissions after the update. The practical decision depends on whether you prioritize advanced privacy (Brave) or maximum compatibility (Chrome).