Skip to content
TrustList
Security advisories

Firefox 160.0.1 fixes two high-impact security flaws in WebGL and media playback

Editorial

By TrustList Editorial

Mozilla released Firefox 160.0.1 on 17 November 2026, fixing CVE-2026-130020, a WebGL privilege escalation on Android, and CVE-2026-130021, a use-after-free in audio and video playback, both rated high.

About Firefox 160.0.1 fixes two high-impact security flaws in WebGL and media playback

Firefox 160.0.1 fixes two high-impact security flaws in WebGL and media playback

17 November 2026: Mozilla has released Firefox 160.0.1, a week after Firefox 160, with two security fixes that its advisory MFSA 2026-130 rates as high impact. Both were found by Mozilla itself.

Not yet independently verified. Mozilla rates both flaws high and does not say either has been exploited. The advisory lists Firefox only, so Firefox ESR is not stated to be affected. We will update this when it can be confirmed, and remove this note.

The two flaws

CVE-2026-130020 is a privilege escalation caused by incorrect boundary conditions in the Graphics: CanvasWebGL component. Mozilla's advisory says it affects Firefox on Android. WebGL is the browser interface that lets pages draw 3D graphics, and a flaw that lets a page escape its limits there can give an attacker more access than the browser is meant to allow.

CVE-2026-130021 is a use-after-free in the Audio/Video: Playback component. A use-after-free happens when the browser keeps using memory it has already released, and in a browser this class of bug can often be turned into code execution through a crafted page or media file.

The advisory does not say either flaw is being exploited, and it lists Firefox only, so Firefox ESR users are not named as affected by these two.

The other fixes in the release

The release notes list a set of non-security fixes alongside the two flaws: PDF printing problems, blank graphics on Macs with AMD graphics, wrong colours under Wayland on Linux, tab crashes on some sites, WebTransport datagrams and swipe scrolling. That makes 160.0.1 worth taking even where the security issues are judged low risk, because some of these fixes stop crashes users will notice.

What IT teams should do

For managed desktops, check that your update channel has picked up 160.0.1 and push it if your policy holds browser updates for testing; the change from 160 is small, so a short pilot is enough. Confirm the version on a sample of machines through about:support or your endpoint tool rather than assuming the auto-updater has run, since a browser left open for days may not have restarted into the new version.

For Android, where the WebGL flaw sits, managed devices should take the update from the Play Store or your mobile device management catalogue. Unmanaged phones used for work are harder: a short reminder to staff to update Firefox and restart it is the practical step.

If you run Firefox ESR, no action is needed for these two CVEs on Mozilla's advisory, but keep to the normal ESR update cycle, which received its own fixes with Firefox 160 on 10 November.

Sources

Categories & features

TrustList Weekly

The week in software and IT, in one email

The news that matters to buyers, new rankings and our own research. Every Thursday, free, and easy to leave.

We will email you to confirm. Unsubscribe with one click in any issue. Privacy policy

You may be interested in