CVE-2026-124920 · Other
NO FIX YET · SEE WHAT TO DO
Firefox's WebGPU graphics component reads memory that was never initialized, which can expose or corrupt data the browser holds. The sources do not say whether this leads to code execution.
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 older than version 160 with WebGPU in use, which is typically a browser that loads pages using GPU graphics. Systems that cannot run Firefox or do not use WebGPU are unlikely to be affected. The sources do not say whether WebGPU is enabled by default.
Not affected if firefox-160-or-later
Who cares desktop-browser, firefox, webgpu
firefox --version on the command line160160 or later, per the sourcesUninitialized memory in the Graphics: WebGPU component. This vulnerability was fixed in Firefox 160.
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.