Skip to main content
CVE-2024-6605VulnerabilityPublished Updated

CVE-2024-6605: Mozilla Firefox · Vulnerability

Affects Mozilla FirefoxSource CVE Database V5

0

Not known to be exploited · CVSS 8.8 High : upgrade to 128 soon.

Data as of 26 Oct 2026, 06:26 UTC

CVSS 3.1 base score
8.8High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.3% chance of exploitation in 30 days – higher than 28% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 128
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 9 Jul 2024

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-26.

What to do

Upgrade Mozilla Firefox to 128.

Affected software

ProductAffectedFixed in
Mozilla FirefoxAffected
  • <128
Fixed in
  • 128

AI-suggested

European organizations should immediately prepare to deploy Firefox updates once Mozilla releases patches for this vulnerability. If you cannot patch yet, organizations should implement the following measures: 1) Educate users about the risks of tapjacking and the importance of carefully reviewing permission prompts before granting access. 2) Employ mobile device management (MDM) solutions to restrict or monitor app permissions and control installation of untrusted applications. 3) Use security solutions capable of detecting suspicious UI overlays or tapjacking attempts on Android devices. 4) Encourage users to disable or limit permissions for apps that do not require them and to avoid interacting with unexpected permission prompts. 5) Monitor network and endpoint logs for unusual activity that may indicate exploitation attempts. 6) Consider restricting Firefox usage on Android devices in high-risk environments until patched. 7) Collaborate with security teams to simulate social engineering scenarios to raise awareness and test defenses against tapjacking attacks.

Description

Firefox Android allowed immediate interaction with permission prompts. This could be used for tapjacking. This vulnerability affects Firefox < 128.

References

Community reviews

Loading reviews…