Mozilla’s Foundation Security Advisory 2026-125, announced November 10, 2026, lists Firefox 160 as the fixed version and rates the advisory’s overall impact high. GBHackers reported 99 vulnerabilities; its breakdown assigns them to three impact categories.

Impact ratingReported vulnerabilities
High57
Moderate24
Low18

For context on other reported Firefox 160 changes, read NeoTeo’s earlier coverage of the browser’s features.

What high-impact flaws does the advisory describe?

Mozilla’s high-impact entries include sandbox escapes, privilege escalation and same-origin policy bypasses. A sandbox is a security boundary that restricts what code can access; a same-origin policy limits how web content from different origins can interact.

CVE-2026-124907 combines privilege escalation and a sandbox escape. Mozilla attributes the flaw to a use-after-free in Graphics: CanvasWebGL, a type of memory error in which software uses memory after it has been released. Other listed sandbox escapes include CVE-2026-124853 in Graphics: Text, CVE-2026-124859 in Storage: Cache API and CVE-2026-124864 in DOM: Service Workers.

The advisory also lists two high-impact same-origin policy bypasses: CVE-2026-124874 in Networking: HTTP and CVE-2026-124902 in Audio/Video, where Mozilla describes a race condition. These entries affect different components, even though both involve the same policy.

Why are the mitigation-bypass flaws different?

Mozilla identifies CVE-2026-124910 as a moderate-impact mitigation bypass in WebExtensions. CVE-2026-124938 is a separate low-impact mitigation bypass in Add-ons Manager. Their similar descriptions do not make them the same vulnerability: each has its own CVE identifier, component and impact rating.

When two security entries use similar wording, check the CVE and affected component alongside the impact rating.

A separate moderate-impact entry, CVE-2026-124911, concerns clickjacking in Autofill in Firefox for Android.