.onion privacy leak and moves Brave to Chromium 158.0.8127.42. It also starts a staged rollout of English speech recognition that runs on your own machine. Brave's official GitHub listing labels the build Release v1.100.58 (Chromium 158.0.8127.42). Its Linux packages appear in the asset list with November 18, 2026 timestamps.Windows users don't get a big redesign this time. The update fixes several narrower problems, and some of them matter a lot to the people who hit them.
What changed in Brave 1.100.58
Brave's public release notes, also posted on the Brave Community forum, list these changes:
- On-device WebSpeech for English: Brave added support for on-device WebSpeech API for English (being rolled out in phases using Griffin starting at 25%).
- Sync security tweak: [Security] Updated various sync "datatype" values to "EncryptableUserTypes".
- AI Chat: Updated AI Chat models. Brave doesn't name the new models.
- UI polish: Updated UI polish for various icons, colors, and spacing. The release also updated split view UI for stacked mode.
- Tor privacy fix: Brave fixed issue where ".onion" domains could be leaked as reported on HackerOne by newfunction.
- Linux admin crash: Brave fixed crash which occurred when the ability to set Brave as default browser was disabled via Admin policy on Linux.
- Containers and Split View: Brave fixed an issue where using "Add Tab to New Split View" on a tab in a container did not open the split view tab in the same container.
- Xbox web compatibility: Brave fixed an issue where and other sites that require viewport size request headers would fail to load.
- Engine update: Upgraded Chromium to 158.0.8127.42.
In short: the list contains one privacy fix, one engine update, a staged local-AI feature, and several targeted bug fixes.
The .onion leak fix
The .onion fix is the most important item for privacy-focused users. Brave's internal 1.100.x desktop release-notes tracker on GitHub lists it as "[hackerone] Tor leaks on fetchLater." fetchLater is a web API that lets a page queue a request to be sent later, for example when the user leaves the page.
The public notes describe the problem only as .onion domains possibly being leaked. Brave hasn't said which configurations were affected, how the leak could be triggered, or whether anyone exploited it. We won't guess.
The practical advice is still simple. If you use Brave's Private Window with Tor, install this update first and investigate later. A Tor window exists to keep onion destinations private. Any leak path undermines that purpose, even one that only appears in unusual timing conditions.
In short: Tor-window users should treat this as a priority update. Brave hasn't released enough detail to judge how severe the issue was.
Chromium 158.0.8127.42
The same GitHub tracker shows Brave moving from Chromium 158.0.8127.37 to 158.0.8127.42. That's a small point bump within Chromium 158, and it happened shortly before the 1.100.58 release was finalized.
Brave's own release-schedule wiki says the company aims to match Chrome's Chromium version. It also says Brave often ships a day after Google, because it waits to see which Chromium build Chrome actually ships.
There is also recent history worth noting. PiunikaWeb reports that 1.100.58 lands just a week after Brave rushed out v1.99.56 to patch an actively exploited Chromium flaw. Freedom.tech's release tracker lists the previous release: v1.99.57 on Thu, Nov 12, 2026 · 6 days apart.
So this is the third Brave stable build in about a week. Admins whose patch approval runs on a weekly cycle should check that they're approving the current build and haven't stopped at 1.99.x.
On-device speech recognition: what the rollout covers
The new speech feature is the most interesting change, and it's easy to misread. PiunikaWeb describes it as a privacy improvement, saying Brave's English speech processing keeps it on your device while maintaining web compatibility.
Brave's GitHub issue for the feature (#56487) explains how it works:
- Websites that call the standard Web Speech API for speech-to-text can be served by a local model. Brave routes those requests to its own controller and a sandboxed WebAssembly worker. It does not use Chromium's usual model-delivery pipeline.
- According to the issue, the worker uses an Nvidia Nemotron model through ONNX Runtime Web. It starts only when needed and shuts down after 60 seconds without use.
- Only English is supported at first.
- The model is a downloadable component, and the planned design asks for user consent before downloading it.
- The issue says the feature is not meant to be available in Private, Guest, or Tor profiles.
- The tracker lists one further hardening step, blocking all network traffic from the speech worker, as post-MVP. Don't assume this release already includes that restriction.
The rollout matters too. "Griffin starting at 25%" refers to Brave's server-side feature-flag system, Griffin, which turns the feature on for about a quarter of installs at first. Updating to 1.100.58 doesn't guarantee you'll see the feature. As PiunikaWeb puts it, you will just have to wait for Griffin to flip the switch on your install.
Brave's QA notes in the issue show the feature tested on Windows 64-bit, Linux, and macOS ARM64. One Windows check used a 1.100.52 beta on Windows 11 25H2. Those are pre-release test results, though, so they don't promise the same behaviour on every PC in the staged rollout.
In short: this is a real local-speech feature for English, but it reaches users gradually and Brave lists some hardening work as still to come.
Smaller fixes worth knowing about
Linux fleet admins: The DefaultBrowserSettingEnabled crash happened when that policy was set to false and someone clicked the default-browser prompt button. It's a small bug, but a managed browser that crashes when a user clicks a button generates support tickets. Windows deployments weren't named in this fix.
Container users: Brave Containers keep cookies and sessions separate. Before this fix, "Add Tab to New Split View" could open the new tab outside the original tab's container. That's a usability bug, and it also weakens the separation users expect from containers.
Xbox Cloud Gaming in Brave: The tracker says the play.xbox.com fix works by enabling Chromium's viewport-height client-hint request header. In practice, Brave now sends a screen-size header that some sites need in order to load. This fixes one specific loading failure. It doesn't mean every Xbox web feature now works in Brave.
How to update on Windows
- Open Brave's About Brave page. PiunikaWeb notes that you can update through the About Brave menu to grab the rest of the fixes right now.
- Let the update download, then restart the browser when asked.
- Confirm that the About page shows 1.100.58 with Chromium 158.0.8127.42.
If you install from scratch, note the "1.2 MB" download size Neowin lists. That file is the small web installer, not the browser itself. Brave's release notes say Brave*Setup.exe will fetch and install the latest available version for your CPU architecture from our update servers. By comparison, the Linux x86_64 RPM on the same release page is 155 MB. Brave says Windows 10 and above are supported. Admins who want a full package can use Brave's offline installers.
Should you update?
Yes, and especially in these cases:
- You use Tor windows. Update now because of the
.onionleak fix. - You manage Brave across a fleet. Make sure the Chromium point bump and the last week's run of releases have reached your machines.
- You use Containers or Xbox Cloud Gaming in Brave. Your specific bug is fixed.
- You want the local speech recognition. You may have to wait for your install to be included in the rollout.
The local speech feature is welcome, and processing dictation on the device is a sensible privacy choice. The release's most important work, though, is the less visible fixes for privacy leaks and engine updates.
References
- Brave Browser 1.100.58 - Neowin Neowin · 2026-11-19T05:14:01+00:00
- Desktop Release Notes for 1.100.x Release · Issue #61942 · brave/brave-browser · GitHub github.com
- Brave introduces local English WebSpeech API processing in v1.100.58 update piunikaweb.com