Firefox for Android at a glance
Show as table
| Month | Vulnerabilities | Critical |
|---|---|---|
| Nov 2026 | 0 | 0 |
| Oct 2026 | 0 | 0 |
| Sep 2026 | 0 | 0 |
| Aug 2026 | 0 | 0 |
| Jul 2026 | 0 | 0 |
| Jun 2026 | 0 | 0 |
| May 2026 | 0 | 0 |
| Apr 2026 | 0 | 0 |
| Mar 2026 | 0 | 0 |
| Feb 2026 | 0 | 0 |
| Jan 2026 | 0 | 0 |
| Dec 2025 | 0 | 0 |
| Nov 2025 | 0 | 0 |
| Oct 2025 | 0 | 0 |
| Sep 2025 | 0 | 0 |
| Aug 2025 | 0 | 0 |
| Jul 2025 | 0 | 0 |
| Jun 2025 | 0 | 0 |
| May 2025 | 0 | 0 |
| Apr 2025 | 0 | 0 |
| Mar 2025 | 0 | 0 |
| Feb 2025 | 0 | 0 |
| Jan 2025 | 0 | 0 |
| Dec 2024 | 0 | 0 |
33 results · Feed
-
Medium 6.1
Under certain conditions, an attacker with the ability to redirect users to a malicious site via an open redirect on a …
-
Medium 6.5
When recording the screen while in Private Browsing on Firefox for Android the address bar and keyboard were not hidden…
-
Critical 9.1
Different techniques existed to obscure the fullscreen notification in Firefox and Focus for Android. These could have …
-
High 7.5
A potential use-after-free in libaudio was fixed by disabling the AAudio backend when running on Android API below vers…
-
Unscored —
Using a redirect embedded into <code>sourceMappingUrls</code> could allow for navigation to external protocol links in …
-
Medium 6.5
Under certain circumstances, a call to the <code>bind</code> function may have resulted in the incorrect realm. This ma…
-
High 8.8
An attacker could have caused memory corruption and a potentially exploitable use-after-free of a pointer in a global o…
-
Unscored —
Following a Garbage Collector compaction, weak maps may have been accessed before they were correctly traced. This resu…
-
Medium 6.5
A wrong lowering instruction in the ARM64 Ion compiler resulted in a wrong optimization result. This vulnerability affe…
-
High 8.8
Firefox did not properly handle downloads of files ending in <code>.desktop</code>, which can be interpreted to run att…
-
Medium 6.5
When a secure cookie existed in the Firefox cookie jar an insecure cookie for the same domain could have been created, …
-
Unscored —
Multiple race conditions in the font initialization could have led to memory corruption and execution of attacker-contr…
-
Medium 6.5
If multiple instances of resource exhaustion occurred at the incorrect time, the garbage collector could have caused me…
-
High 8.8
Memory safety bugs present in Firefox 111 and Firefox ESR 102.9. Some of these bugs showed evidence of memory corruptio…
-
Unscored —
Under specific circumstances a WebExtension may have received a <code>jar:file:///</code> URI instead of a <code>moz-ex…
-
Unscored —
An attacker could cause the memory manager to incorrectly free a pointer that addresses attacker-controlled memory, res…
-
High 8.8
Memory safety bugs present in Firefox 111. Some of these bugs showed evidence of memory corruption and we presume that …
-
Unscored —
A website could have obscured the fullscreen notification by using a combination of <code>window.open</code>, fullscree…
-
Unscored —
When handling the filename directive in the Content-Disposition header, the filename would be truncated if the filename…
-
High 8.8
If an attacker was able to corrupt the methods of an Array object in JavaScript via prototype pollution, they could hav…
-
High 8.8CVE-2022-1529 EPSS 18%
An attacker could have sent a message to the parent process where the contents were used to double-index into a JavaScr…
-
High 8.8
Removing an XSLT parameter during processing could have lead to an exploitable use-after-free. We have had reports of a…
KEV Mar 7, 2022 -
Critical 9.6CVE-2022-26486 Exploited
An unexpected message in the WebGPU IPC framework could lead to a use-after-free and exploitable sandbox escape. We hav…
KEV Mar 7, 2022 -
Unscored —
When Web Render components were destructed, a race condition could have caused undefined behavior, and we presume that …
-
Unscored —
A malicious webpage could have forced a Firefox for Android user into executing attacker-controlled JavaScript in the c…
-
Unscored —
When performing EC scalar point multiplication, the wNAF point multiplication algorithm was used; which leaked partial …
-
Unscored —
When converting coordinates from projective to affine, the modular inversion was not performed in constant time, result…
-
Unscored —
During ECDSA signature generation, padding applied in the nonce designed to ensure constant-time scalar multiplication …
-
Unscored —
By holding a reference to the eval() function from an about:blank window, a malicious webpage could have gained access …
-
Unscored —
When trying to load a non-video in an audio/video context the exact status code (200, 302, 404, 500, 412, 403, etc.) wa…
-
Unscored —
A lock was missing when accessing a data structure and importing certificate information into the trust database. This …
-
Unscored —
Mozilla developers reported memory safety bugs present in Firefox for Android 79. Some of these bugs showed evidence of…
-
Unscored —
When typing in a password under certain conditions, a race may have occured where the InputContext was not being correc…