Original announcement: · Reporting prepared on the publication date above.
What to know
- Use the update channel appropriate to each installation.
- Restart and confirm the installed version after updating.
- Test real business tasks and track devices awaiting completion.
Mozilla’s latest security announcement
On 27 October 2026, Mozilla published MFSA 2026-118, a high-impact advisory listing fixes in Firefox 159. It includes memory-safety issues and sandbox escapes. The advisory describes the scope of that release; administrators should check their installation channel for the current supported update rather than treating this article as a permanent version recommendation.
Update through the correct channel
Mozilla’s update instructions explain that downloaded browser updates take effect after a restart. Linux distribution packages and Microsoft Store installations have their own update channels. Identify how each team device receives Firefox before writing a single company-wide instruction.
Choose a practical test group
Our rollout suggestion is to begin with one representative device for each operating system your team uses. Ask the test users to complete their ordinary tasks: sign in to the customer portal, download a document, join a meeting and submit a form. Include the accessibility settings and extensions they actually need. Record the browser version after restarting, plus any workflow that behaves differently.
Make completion visible
Create a short maintenance ticket with device owner, update channel, restart status and check results. Separate devices that are waiting for the user from devices with a failed installer. Give staff a clear restart window and a contact for problems. A team member who has saved several days of work in open tabs needs useful instructions, not a vague request to update whenever convenient.
Review the wider workstation routine
Browser maintenance fits into the same operational calendar as operating-system updates, account recovery reviews and extension inventory. Schedule a follow-up for absent staff and devices kept offline. This article is a suggested rollout process, not evidence that any particular computer was compromised. For a managed review of your business devices, describe the environment through Kiava IT services. Our passkey and MFA guide covers the account protections that complement a maintained browser.
Sources & further reading
Primary sources supporting this article. The practical recommendations are Kiava’s general guidance and should be adapted to your project.