This page was not yet optimized for use on mobile devices.
Mozilla Firefox 134.0.2
Configuration details
| CPE title | Mozilla Firefox 134.0.2 |
|---|---|
| URI | cpe:2.3:a:mozilla:firefox:134.0.2:*:*:*:-:*:*:* |
Linked CVEs
186 CVEs| ID | Links | Severity | CVSS Score | Published on |
|---|---|---|---|---|
| Base score | ||||
| CVE-2025-1414 | MEDIUM | 6.5 | 18.02.2025 | |
| CVE-2025-2857 | CRITICAL | 10.0 | 27.03.2025 | |
| CVE-2025-3608 | MEDIUM | 6.5 | 15.04.2025 | |
| CVE-2025-4918 | CRITICAL | 9.8 | 17.05.2025 | |
| CVE-2025-4919 | HIGH | 8.8 | 17.05.2025 | |
| CVE-2025-49709 | CRITICAL | 9.8 | 11.06.2025 | |
| CVE-2025-49710 | CRITICAL | 9.8 | 11.06.2025 | |
| CVE-2026-100768 | HIGH | 8.8 | 29.09.2026 | |
| CVE-2026-100779 | HIGH | 8.8 | 29.09.2026 | |
| CVE-2026-100780 | HIGH | 8.8 | 29.09.2026 | |
| CVE-2026-100781 | CRITICAL | 9.6 | 29.09.2026 | |
| CVE-2026-100782 | HIGH | 8.8 | 29.09.2026 | |
| CVE-2026-100783 | MEDIUM | 4.3 | 29.09.2026 | |
| CVE-2026-100784 | HIGH | 8.8 | 29.09.2026 | |
| CVE-2026-100785 | HIGH | 8.8 | 29.09.2026 | |
| CVE-2026-100786 | CRITICAL | 9.6 | 29.09.2026 | |
| CVE-2026-100787 | CRITICAL | 9.6 | 29.09.2026 | |
| CVE-2026-100808 | HIGH | 8.8 | 29.09.2026 | |
| CVE-2026-100809 | HIGH | 8.1 | 29.09.2026 | |
| CVE-2026-100810 | CRITICAL | 9.8 | 29.09.2026 | |
| CVE-2026-100811 | CRITICAL | 9.6 | 29.09.2026 | |
| CVE-2026-100812 | MEDIUM | 6.5 | 29.09.2026 | |
| CVE-2026-100813 | HIGH | 8.8 | 29.09.2026 | |
| CVE-2026-100814 | HIGH | 8.8 | 29.09.2026 | |
| CVE-2026-100815 | HIGH | 8.8 | 29.09.2026 | |
| CVE-2026-100816 | HIGH | 8.1 | 29.09.2026 | |
| CVE-2026-100817 | MEDIUM | 5.4 | 29.09.2026 | |
| CVE-2026-100818 | CRITICAL | 9.6 | 29.09.2026 | |
| CVE-2026-100819 | CRITICAL | 9.6 | 29.09.2026 | |
| CVE-2026-100820 | HIGH | 8.8 | 29.09.2026 | |
| CVE-2026-100832 | HIGH | 8.8 | 29.09.2026 | |
| CVE-2026-74934 | HIGH | 7.5 | 18.08.2026 | |
| CVE-2026-74935 | HIGH | 8.8 | 18.08.2026 | |
| CVE-2026-74936 | CRITICAL | 9.8 | 18.08.2026 | |
| CVE-2026-74937 | HIGH | 8.8 | 18.08.2026 | |
| CVE-2026-74938 | CRITICAL | 9.1 | 18.08.2026 | |
| CVE-2026-74939 | HIGH | 8.8 | 18.08.2026 | |
| CVE-2026-74940 | CRITICAL | 9.8 | 18.08.2026 | |
| CVE-2026-74941 | HIGH | 8.8 | 18.08.2026 | |
| CVE-2026-74942 | HIGH | 8.8 | 18.08.2026 | |
| CVE-2026-74943 | CRITICAL | 9.8 | 18.08.2026 | |
| CVE-2026-74944 | CRITICAL | 9.8 | 18.08.2026 | |
| CVE-2026-74945 | MEDIUM | 6.5 | 18.08.2026 | |
| CVE-2026-74946 | HIGH | 8.8 | 18.08.2026 | |
| CVE-2026-74947 | HIGH | 8.8 | 18.08.2026 | |
| CVE-2026-74948 | MEDIUM | 6.5 | 18.08.2026 | |
| CVE-2026-74949 | HIGH | 8.8 | 18.08.2026 | |
| CVE-2026-74950 | HIGH | 8.8 | 18.08.2026 | |
| CVE-2026-74952 | HIGH | 8.8 | 18.08.2026 | |
| CVE-2026-74953 | HIGH | 8.8 | 18.08.2026 | |
| CVE-2026-74954 | HIGH | 7.5 | 18.08.2026 | |
| CVE-2026-74955 | HIGH | 8.8 | 18.08.2026 | |
| CVE-2026-74956 | CRITICAL | 9.1 | 18.08.2026 | |
| CVE-2026-74957 | HIGH | 8.1 | 18.08.2026 | |
| CVE-2026-74958 | HIGH | 7.5 | 18.08.2026 | |
| CVE-2026-74959 | CRITICAL | 9.1 | 18.08.2026 | |
| CVE-2026-74960 | HIGH | 8.1 | 18.08.2026 | |
| CVE-2026-74962 | HIGH | 8.1 | 18.08.2026 | |
| CVE-2026-74963 | MEDIUM | 5.4 | 18.08.2026 | |
| CVE-2026-74964 | CRITICAL | 9.8 | 18.08.2026 | |
| CVE-2026-74965 | HIGH | 8.8 | 18.08.2026 | |
| CVE-2026-74966 | HIGH | 7.5 | 18.08.2026 | |
| CVE-2026-74967 | MEDIUM | 5.4 | 18.08.2026 | |
| CVE-2026-74968 | MEDIUM | 5.4 | 18.08.2026 | |
| CVE-2026-74969 | HIGH | 8.8 | 18.08.2026 | |
| CVE-2026-74970 | MEDIUM | 5.4 | 18.08.2026 | |
| CVE-2026-74971 | MEDIUM | 4.3 | 18.08.2026 | |
| CVE-2026-74972 | MEDIUM | 4.3 | 18.08.2026 | |
| CVE-2026-74973 | MEDIUM | 4.2 | 18.08.2026 | |
| CVE-2026-74974 | MEDIUM | 5.4 | 18.08.2026 | |
| CVE-2026-74976 | MEDIUM | 6.5 | 18.08.2026 | |
| CVE-2026-74977 | HIGH | 7.5 | 18.08.2026 | |
| CVE-2026-74978 | HIGH | 8.1 | 18.08.2026 | |
| CVE-2026-74979 | CRITICAL | 9.8 | 18.08.2026 | |
| CVE-2026-74981 | HIGH | 8.1 | 18.08.2026 | |
| CVE-2026-74982 | HIGH | 7.5 | 18.08.2026 | |
| CVE-2026-74983 | HIGH | 8.1 | 18.08.2026 | |
| CVE-2026-74984 | MEDIUM | 6.8 | 18.08.2026 | |
| CVE-2026-74985 | CRITICAL | 9.8 | 18.08.2026 | |
| CVE-2026-74986 | CRITICAL | 9.1 | 18.08.2026 | |
| CVE-2026-74987 | CRITICAL | 9.8 | 18.08.2026 | |
| CVE-2026-74988 | CRITICAL | 9.8 | 18.08.2026 | |
| CVE-2026-74989 | CRITICAL | 9.8 | 18.08.2026 | |
| CVE-2026-74990 | CRITICAL | 9.8 | 18.08.2026 | |
| CVE-2026-75874 | CRITICAL | 10.0 | 18.08.2026 | |
| CVE-2026-84118 | MEDIUM | 5.4 | 01.09.2026 | |
| CVE-2026-84119 | CRITICAL | 9.6 | 01.09.2026 | |
| CVE-2026-84120 | MEDIUM | 5.4 | 01.09.2026 | |
| CVE-2026-84121 | CRITICAL | 9.6 | 01.09.2026 | |
| CVE-2026-84122 | MEDIUM | 5.4 | 01.09.2026 | |
| CVE-2026-84123 | HIGH | 8.8 | 01.09.2026 | |
| CVE-2026-84124 | MEDIUM | 5.4 | 01.09.2026 | |
| CVE-2026-84125 | MEDIUM | 5.4 | 01.09.2026 | |
| CVE-2026-84126 | MEDIUM | 4.3 | 01.09.2026 | |
| CVE-2026-84128 | HIGH | 8.8 | 01.09.2026 | |
| CVE-2026-84129 | CRITICAL | 9.8 | 01.09.2026 | |
| CVE-2026-84130 | HIGH | 7.5 | 01.09.2026 | |
| CVE-2026-84131 | HIGH | 8.8 | 01.09.2026 | |
| CVE-2026-84132 | HIGH | 7.5 | 01.09.2026 | |
| CVE-2026-84133 | CRITICAL | 9.8 | 01.09.2026 | |
| CVE-2026-84134 | CRITICAL | 9.8 | 01.09.2026 | |
| CVE-2026-84136 | MEDIUM | 6.1 | 01.09.2026 | |
| CVE-2026-84137 | MEDIUM | 4.3 | 01.09.2026 | |
| CVE-2026-84138 | MEDIUM | 6.5 | 01.09.2026 | |
| CVE-2026-84139 | MEDIUM | 6.1 | 01.09.2026 | |
| CVE-2026-84140 | CRITICAL | 9.8 | 01.09.2026 | |
| CVE-2026-84141 | CRITICAL | 9.8 | 01.09.2026 | |
| CVE-2026-84142 | CRITICAL | 9.8 | 01.09.2026 | |
| CVE-2026-84143 | CRITICAL | 9.8 | 01.09.2026 | |
| CVE-2026-84144 | HIGH | 7.5 | 01.09.2026 | |
| CVE-2026-84145 | HIGH | 7.5 | 01.09.2026 | |
| CVE-2026-92005 | MEDIUM | 5.3 | 15.09.2026 | |
| CVE-2026-92006 | HIGH | 8.8 | 15.09.2026 | |
| CVE-2026-92007 | HIGH | 8.8 | 15.09.2026 | |
| CVE-2026-92008 | HIGH | 8.8 | 15.09.2026 | |
| CVE-2026-92009 | HIGH | 8.8 | 15.09.2026 | |
| CVE-2026-92010 | HIGH | 8.8 | 15.09.2026 | |
| CVE-2026-92011 | HIGH | 8.8 | 15.09.2026 | |
| CVE-2026-92012 | HIGH | 8.8 | 15.09.2026 | |
| CVE-2026-92013 | HIGH | 8.8 | 15.09.2026 | |
| CVE-2026-92014 | HIGH | 8.8 | 15.09.2026 | |
| CVE-2026-92015 | HIGH | 8.8 | 15.09.2026 | |
| CVE-2026-92016 | HIGH | 8.8 | 15.09.2026 | |
| CVE-2026-92017 | HIGH | 8.8 | 15.09.2026 | |
| CVE-2026-92018 | CRITICAL | 9.6 | 15.09.2026 | |
| CVE-2026-92019 | HIGH | 8.1 | 15.09.2026 | |
| CVE-2026-92020 | HIGH | 8.8 | 15.09.2026 | |
| CVE-2026-92021 | HIGH | 8.8 | 15.09.2026 | |
| CVE-2026-92022 | HIGH | 8.8 | 15.09.2026 | |
| CVE-2026-92023 | HIGH | 8.8 | 15.09.2026 | |
| CVE-2026-92024 | HIGH | 8.8 | 15.09.2026 | |
| CVE-2026-92025 | HIGH | 8.8 | 15.09.2026 | |
| CVE-2026-92026 | HIGH | 8.8 | 15.09.2026 | |
| CVE-2026-92027 | HIGH | 8.8 | 15.09.2026 | |
| CVE-2026-92028 | HIGH | 8.8 | 15.09.2026 | |
| CVE-2026-92029 | HIGH | 8.8 | 15.09.2026 | |
| CVE-2026-92030 | MEDIUM | 5.4 | 15.09.2026 | |
| CVE-2026-92031 | MEDIUM | 6.5 | 15.09.2026 | |
| CVE-2026-92032 | CRITICAL | 9.6 | 15.09.2026 | |
| CVE-2026-92034 | CRITICAL | 9.1 | 15.09.2026 | |
| CVE-2026-92035 | CRITICAL | 9.6 | 15.09.2026 | |
| CVE-2026-92036 | CRITICAL | 9.8 | 15.09.2026 | |
| CVE-2026-92037 | CRITICAL | 9.8 | 15.09.2026 | |
| CVE-2026-92038 | CRITICAL | 9.1 | 15.09.2026 | |
| CVE-2026-92039 | MEDIUM | 6.3 | 15.09.2026 | |
| CVE-2026-92040 | HIGH | 8.8 | 15.09.2026 | |
| CVE-2026-92041 | CRITICAL | 9.1 | 15.09.2026 | |
| CVE-2026-92042 | HIGH | 7.5 | 15.09.2026 | |
| CVE-2026-92043 | HIGH | 8.8 | 15.09.2026 | |
| CVE-2026-92044 | HIGH | 7.5 | 15.09.2026 | |
| CVE-2026-92045 | CRITICAL | 9.6 | 15.09.2026 | |
| CVE-2026-92046 | HIGH | 8.8 | 15.09.2026 | |
| CVE-2026-92047 | HIGH | 8.8 | 15.09.2026 | |
| CVE-2026-92048 | CRITICAL | 9.0 | 15.09.2026 | |
| CVE-2026-92049 | HIGH | 8.8 | 15.09.2026 | |
| CVE-2026-92050 | CRITICAL | 9.1 | 15.09.2026 | |
| CVE-2026-92051 | CRITICAL | 9.1 | 15.09.2026 | |
| CVE-2026-92052 | HIGH | 8.8 | 15.09.2026 | |
| CVE-2026-92053 | HIGH | 8.8 | 15.09.2026 | |
| CVE-2026-92054 | HIGH | 8.8 | 15.09.2026 | |
| CVE-2026-92055 | HIGH | 8.8 | 15.09.2026 | |
| CVE-2026-92056 | HIGH | 8.8 | 15.09.2026 | |
| CVE-2026-92057 | CRITICAL | 9.1 | 15.09.2026 | |
| CVE-2026-92058 | HIGH | 8.8 | 15.09.2026 | |
| CVE-2026-92059 | CRITICAL | 9.3 | 15.09.2026 | |
| CVE-2026-92060 | HIGH | 8.8 | 15.09.2026 | |
| CVE-2026-92061 | CRITICAL | 9.8 | 15.09.2026 | |
| CVE-2026-92062 | HIGH | 8.8 | 15.09.2026 | |
| CVE-2026-92063 | MEDIUM | 6.5 | 15.09.2026 | |
| CVE-2026-92064 | HIGH | 8.8 | 15.09.2026 | |
| CVE-2026-92065 | HIGH | 8.8 | 15.09.2026 | |
| CVE-2026-92066 | CRITICAL | 9.8 | 15.09.2026 | |
| CVE-2026-92067 | HIGH | 8.8 | 15.09.2026 | |
| CVE-2026-92068 | MEDIUM | 5.4 | 15.09.2026 | |
| CVE-2026-92069 | MEDIUM | 5.4 | 15.09.2026 | |
| CVE-2026-92070 | MEDIUM | 4.3 | 15.09.2026 | |
| CVE-2026-92071 | CRITICAL | 9.6 | 15.09.2026 | |
| CVE-2026-92072 | HIGH | 8.0 | 15.09.2026 | |
| CVE-2026-92073 | HIGH | 8.8 | 15.09.2026 | |
| CVE-2026-92074 | HIGH | 8.8 | 15.09.2026 | |
| CVE-2026-92075 | CRITICAL | 9.1 | 15.09.2026 | |
| CVE-2026-92076 | HIGH | 8.8 | 15.09.2026 | |
| CVE-2026-92077 | MEDIUM | 6.5 | 15.09.2026 | |
| CVE-2026-92078 | MEDIUM | 6.5 | 15.09.2026 | |
| CVE-2026-92079 | CRITICAL | 9.1 | 15.09.2026 | |
| CVE-2026-96869 | MEDIUM | 4.3 | 29.09.2026 |
Showing 5 out of 186.
Matched certificates
This CPE has no matched certificates.