Firefox 160 Arrives With Mini Window and 99 Security Fixes
Mozilla's latest stable release adds an early Mini Window mode, Picture-in-Picture playback speed, broader MKV audio support, and patches 99 CVEs across the browser.

Firefox 160 is now rolling out on the Release channel, and alongside a handful of new features it closes 99 security vulnerabilities — 57 of them rated high severity. The headline additions are an early version of a new "Mini Window" mode, a Picture-in-Picture playback speed control, and support for Matroska (MKV) files carrying FLAC, MP3, or PCM audio.
- Firefox 160 began rolling out to Release channel users on November 10, 2026.
- Mini Window lets you pop a tab, or part of a page, into a small always-on-top window — an early, in-development feature.
- Picture-in-Picture now supports playback speeds from 0.25x to 2.0x.
- MKV files with FLAC, MP3, or PCM audio now play natively.
- Mozilla's advisory MFSA2026-125 fixes 99 CVEs: 57 high, 24 moderate, 18 low severity.
What's new in Firefox 160
Mozilla's official release notes for version 160.0 list a mix of small workflow features rather than one single marquee addition. The most visible new feature is Mini Window: an early, opt-in way to move a tab, or just a selected portion of a page, into a small floating window that stays on top of other apps. Mozilla frames it explicitly as an early version and says it's actively collecting feedback as the feature develops, so the current implementation is likely to change in upcoming releases.
Picture-in-Picture, the floating video player Firefox has offered for several years, gains a long-requested playback speed control running from 0.25x up to 2.0x. The option only appears once the PiP window is resized to medium or larger, so it's easy to miss if you keep the floating player small.
Who Mini Window is actually useful for
Mini Window solves a specific, narrow annoyance: keeping a reference document, a chat window, or a video visible while you work in another app, without dedicating a full browser window or juggling alt-tab. It's conceptually similar to features other browsers and operating systems have shipped under different names — always-on-top windows, "focus mode" panels, or widget-style overlays — but Firefox's version is built around moving an existing tab or a selected page fragment into the floating window rather than requiring a dedicated app or extension. Because Mozilla is treating this as an early build, some interactions (resizing behavior, which keyboard shortcuts summon it, whether it survives a browser restart) are still being worked out, and feedback from this release is expected to shape how the feature looks once it graduates out of its early state.
Media and platform changes
Firefox 160 adds native playback of Matroska (MKV) container files carrying FLAC, MP3, or PCM audio tracks, closing a long-standing gap for people who keep locally ripped media libraries in MKV format. On macOS specifically, WebGL content now renders through Apple's Metal graphics API instead of OpenGL, which Mozilla says can improve performance on some sites; Mac users may notice smoother scrolling or animation on WebGL-heavy pages as a result.
The release also ships sidebar history entries that can be dragged directly onto the tab strip to reopen in a new tab, an address bar context menu that now reads "Paste and Search" instead of the generic "Paste and Go" when the clipboard holds a search term, and PDF accessibility improvements so that math notation (MathML) saved into a PDF remains readable by screen readers.
What's new for developers and the web platform
Firefox 160 also brings two web-platform additions that matter more to developers than everyday browsing. The browser now supports the SpeechRecognition interface of the Web Speech API, enabling on-device, real-time speech-to-text in 40 languages without a page needing to round-trip audio to a server. And the legacy, WebKit-only ::-webkit-input-placeholder CSS pseudo-element is now supported as an alias for the standard ::placeholder, which should quietly fix placeholder-text styling on older sites that were only ever tested against Chrome and Safari. Mozilla credited 22 contributors with landing their first code change in this release, part of the project's ongoing push to keep its open-source contributor pipeline active alongside paid engineering work. That pipeline matters more for Firefox than for closed-source competitors, since community-submitted patches regularly account for a meaningful share of the bug fixes — including security fixes — that ship in any given monthly release.
A new way to silence repeat permission prompts
One smaller but practical addition: sites that keep asking to become the default handler for links like mailto: can now be permanently blocked with a one-click "Never allow" option, rather than dismissing the same prompt every time you visit. Blocked sites are listed and can be unblocked later from Firefox's settings, which is a cleaner fix than the workarounds people previously relied on to stop the repeated pop-ups.
Bug fixes worth knowing about
Alongside new features, Firefox 160 patches a handful of annoyances that had built up across recent releases. Typing quickly into the address bar right after clicking into it no longer occasionally drops the first character. Signing into intranet sites that use NTLM or Kerberos (Negotiate) authentication no longer freezes the browser for several seconds while credentials are negotiated. On macOS, background links opened from other apps — an RSS reader, for instance — no longer yank Firefox to the foreground, simultaneous downloads no longer silently stall when Firefox is set to ask where to save each file, and PDFs opened in Preview from the print dialog regain their proper filenames.
Inside MFSA2026-125: 99 fixes, 57 of them high severity
Every Firefox release ships with a matching Mozilla Foundation Security Advisory, and MFSA2026-125 is this month's. It's a large one: 99 individually tracked CVEs, more than most monthly browser updates.
| Severity | Count | Example |
|---|---|---|
| High | 57 | CVE-2026-124857 — use-after-free in the Canvas2D graphics component |
| Moderate | 24 | CVE-2026-124909 — information disclosure in Private Browsing |
| Low | 18 | CVE-2026-124934 — spoofing issue in the Security component |
None of the 99 entries are rated critical — Mozilla's own severity scale tops out at high for this release — but the sheer volume of high-severity memory-safety bugs is the real story. Several of the high-severity items involve use-after-free conditions in graphics code, including one described as a sandbox escape stemming from incorrect boundary handling in the Text rendering component. Use-after-free and boundary-check bugs are the categories browser security researchers watch most closely, because they're the building blocks of the exploit chains that eventually get weaponized for remote code execution, even when no individual bug in a given release is flagged as already under attack.
The moderate-severity entries skew toward information disclosure issues, such as the Private Browsing component bug listed above, where the risk is leaking data a user expected to stay isolated rather than letting an attacker run arbitrary code. Low-severity entries are mostly spoofing issues — cases where a malicious page could misrepresent itself in the address bar or a dialog box, annoying but not directly exploitable on their own. Mozilla's advisory lists every CVE individually with its own tracking bug number, which is useful if you need to confirm whether a specific, publicly disclosed Firefox bug was addressed in this release rather than relying on the summary counts alone.
Why this month's advisory is unusually large
Ninety-nine fixed CVEs is on the high end even by Firefox's own recent history, where monthly advisories more typically run from the dozens into the sixties. Mozilla's advisory doesn't single out a reason for the jump, and large counts like this are usually explained by a backlog of fuzzing-discovered memory bugs landing together rather than any one dramatic new discovery. The practical upshot for anyone running Firefox is the same regardless of the explanation: a large advisory like this one is exactly the kind of release where delaying the update for even a few days meaningfully widens your exposure window, since the vulnerability details become public the moment the advisory ships.
How to update to Firefox 160
Firefox normally updates itself in the background; opening the menu (the three horizontal lines) and going to Help > About Firefox forces an immediate check and shows the current version number once the update finishes downloading. People managing Firefox in a business environment should consult Mozilla's separate Firefox Enterprise release notes, since policy-controlled deployments often hold back point releases for compatibility testing before pushing them fleet-wide. Given the size of this month's security advisory, that testing window is worth keeping as short as practical rather than deferring the update to the next scheduled maintenance cycle.
If you're unsure which build you're running, the version number and build ID both appear on the same About Firefox screen, which is also where Firefox displays whether you're on the standard Release channel, Beta, Developer Edition, or Nightly — each of which receives security fixes on a different schedule, with Nightly and Beta typically getting a given fix weeks before it reaches Release.
Mozilla also flagged in this release that Firefox has dropped support for Windows 8.1 and earlier, and macOS 10.14 and earlier; anyone still on those older operating systems is directed toward Firefox ESR, the Extended Support Release track, instead.
Smart Window and other gradual rollouts
A few of Firefox 160's features aren't universal on day one. "Organize Tabs," part of Mozilla's Smart Window tab-grouping feature, is gaining French-language support in this release, but Mozilla describes it as a progressive rollout, meaning not every eligible user will see it immediately even after updating. Mini Window carries the same caveat: because Mozilla is explicitly soliciting feedback on an early version, expect its behavior to shift in upcoming point releases rather than treating the current implementation as final.
How Firefox 160 compares with the rest of the browser field
Firefox's release lands the same month as a heavy run of browser security news elsewhere: Chrome's own 157 branch shipped an emergency patch for a flaw already under active attack earlier in November. Seeing two of the web's major browser engines ship unusually large or urgent security updates in the same month is a reminder that browser security work runs on a constant cycle regardless of vendor — there's no single "quiet" browser to switch to for safety, just a question of which one you keep current.
What's next
Firefox 161 is already in the pipeline and is on track to ship November 24, 2026, roughly two weeks after 160. Early beta notes point to a more prominent Android warning when an extension update requests new permissions or data-collection consent, continuing Mozilla's recent focus on tightening how extensions request access on mobile. Expect a fresh security advisory to accompany that release as well, following the same monthly cadence Firefox has kept for years. It's a cadence worth getting used to across your whole toolchain, not just your browser — the same discipline applies to runtimes and languages you might use for development, such as keeping track of Node.js's own LTS release schedule or PHP's recent 8.6 upgrade decision.
Frequently asked questions
When did Firefox 160 release?
Firefox 160 began rolling out to Release channel users on November 10, 2026.
What is Mini Window in Firefox 160?
An early, in-development feature that lets you pop a tab or a selected part of a page into a small, always-on-top floating window.
How many security vulnerabilities does Firefox 160 fix?
99, per Mozilla's advisory MFSA2026-125: 57 high, 24 moderate, and 18 low severity.
Does Firefox 160 support MKV video files?
It adds support specifically for MKV files that carry FLAC, MP3, or PCM audio tracks.
How do I update to Firefox 160?
Go to the Firefox menu and select Help > About Firefox, which checks for and installs the latest version automatically.
Sources
- Firefox 160.0 Release Notes (Mozilla)firefox.com
- Mozilla Foundation Security Advisory MFSA2026-125mozilla.org
- MDN Web Docs — SpeechRecognition APIdeveloper.mozilla.org
- Mozilla Support — Firefox Enterprise Release Notessupport.mozilla.org
Felix Moreau writes Pandromeda's software coverage and how-to guides. He covers Windows, macOS and Linux updates, the apps people rely on, emulators and developer tools, and turns official documentation into clear, numbered steps that work on the current version.