CVE-2026-124947 · Other
NO FIX YET · SEE WHAT TO DO
Firefox's Graphics component has incorrect boundary conditions, a memory-safety style flaw whose exact effect the sources do not describe. Mozilla says it was fixed in Firefox 160.
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 is exposed, as the sources only name Firefox as affected. The sources do not say whether the flaw needs a specific page, content, or setting to trigger. unknown for further details.
Not affected if firefox-160-or-later
Who cares desktop-browser, firefox
firefox --version on the machine.160.160Incorrect boundary conditions in the Graphics 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.