CVE-2022-26486
Mozilla Firefox Use-After-Free Vulnerability
Mozilla Firefox
An unexpected message in the WebGPU IPC framework could lead to a use-after-free and exploitable sandbox escape. We have had reports of attacks in the wild abusing this flaw. This vulnerability affects Firefox < 97.0.2, Firefox ESR < 91.6.1, Firefox for Android < 97.3.0, Thunderbird < 91.6.2, and Focus < 97.3.0.
Exploitation status
CISA Known Exploited Vulnerabilities
Listed by CISA on 7 March 2022. US federal agencies were required to remediate it by 21 March 2022.
EPSS — exploitation probability
FIRST puts the probability of exploitation activity in the next 30 days at 2.4%, which is higher than 84.1% of all scored vulnerabilities. EPSS is a forecast of activity, not a measure of severity, and it is rescored daily.
CVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:H
Frequently asked questions
Is CVE-2022-26486 being exploited by ransomware groups?
No ransomware group in this database is currently recorded as exploiting CVE-2022-26486.
What does CVE-2022-26486 affect?
CVE-2022-26486 affects Mozilla Firefox. An unexpected message in the WebGPU IPC framework could lead to a use-after-free and exploitable sandbox escape. We have had reports of attacks in the wild abusing this flaw. This vulnerability affects Firefox < 97.0.2, Firefox ESR < 91.6.1, Firefox for Android < 97.3.0, Thunderbird < 91.6.2, and Focus < 97.3.0.
How severe is CVE-2022-26486?
CVE-2022-26486 is rated CRITICAL with a CVSS base score of 9.6. EPSS puts the probability of exploitation in the next 30 days at 2.4%, higher than 84.1% of all scored vulnerabilities. It is listed in the CISA Known Exploited Vulnerabilities catalog, with a federal remediation deadline of 21 March 2022.
How should organisations respond to CVE-2022-26486?
Apply the vendor patch for Mozilla Firefox as the first priority, and treat any internet-facing instance as the most urgent. Because this vulnerability is associated with ransomware activity, also review whether the affected systems were reachable before patching, rather than assuming that patching alone closes the incident.