Firefox 159 ו-ESR: לבחור את עדכון האבטחה של הענף שלכם

Read this news or bug-fix article as reference material:
https://nethanelfitoussi.com/article/firefox-159-esr-october-27-security-fixes?lang=en

Goal: apply the documented workflow to my development project.
Read the existing project instructions, inspect the relevant files and explain the smallest useful setup.

Use the article and its examples as references. Identify any missing project files before making changes.

If I have not supplied a project folder, ask which development project to use. Do not invent a repository URL.

Additional project setup instructions:
Review Mozilla’s 27 October 2026 advisories MFSA 2026-118, 2026-120 and 2026-119 at https://www.mozilla.org/en-US/security/advisories/ . Inventory desktop Firefox installations and the ESR branch on managed devices. Compare them to Firefox 159, ESR 153.6 or ESR 115.44 as appropriate; consult the separate advisory for each branch rather than assuming identical CVE coverage. Plan updates through the existing official or organisation-managed channel and verify the running version after restart. Separately inventory browser automation runtimes. Keep sandbox and site-isolation protections enabled. Do not infer exploitation from an outdated version or run proof-of-concept payloads.

Check the dated advisory and current official vendor guidance. Identify whether my installed version and configuration are affected before proposing a fix.

Give me a short plan, then make the agreed local changes and run the relevant checks. Report actual results and anything not verified. Stop before credentials, paid services, production changes, push, merge or deployment.