CVE-2026-124915 · Runtime
NO FIX YET · SEE WHAT TO DO
Firefox's WebGPU graphics component has an incorrect boundary check, a memory-safety class of bug. The sources do not say what an attacker can do with it beyond that.
first public Nov 10, 2026 · 1 source
Could this affect your app?
Free first check from your website. Connect your repo for the full answer.
Anyone running Firefox before the fixed versions, since WebGPU is enabled by default in browsers that ship it. The sources do not say whether a web page alone can trigger the flaw or what conditions are required. Teams that pin Firefox ESR on managed desktops should check that channel.
Not affected if already-updated
Who cares browsers, firefox, webgpu
firefox --version (or check About Firefox) and compare against the fixed versions below.160153.7Incorrect boundary conditions in the Graphics: WebGPU component. This vulnerability was fixed in Firefox 160 and Firefox ESR 153.7.
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.
Check it with your coding agent
It reads this page and tells you if your code is affected.
Are you affected?
Ask from here. InfraStack checks the affected versions against your stack and answers in your inbox.
InfraStack checks the affected versions against your stack and answers in Slack, with the evidence and the fix.