Skip to main content
CVE-2024-6613VulnerabilityPublished Updated

CVE-2024-6613: Mozilla Firefox · CWE-209

Affects Mozilla FirefoxSource CVE Database V5

0

Not known to be exploited · CVSS 5.5 Medium : upgrade to 128 when convenient.

Data as of 26 Oct 2026, 08:30 UTC

CVSS 3.1 base score
5.5Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.1% chance of exploitation in 30 days – higher than 8% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 128
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:N/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 26 Oct 2026.

What to do

Upgrade Mozilla Firefox to 128.

Affected software

ProductAffectedFixed in
Mozilla FirefoxAffected
  • <128
Fixed in
  • 128

AI-suggested

Organizations should monitor Mozilla's official channels for the release of patches addressing CVE-2024-6613 and apply updates to Firefox and Thunderbird promptly once available, specifically upgrading to version 128 or later. If you cannot patch yet, organizations can mitigate risk by restricting local user access to untrusted WebAssembly content, for example, by controlling browser usage policies or disabling wasm execution where feasible. User education to avoid interacting with suspicious web content or email attachments containing wasm frames can reduce the likelihood of triggering the vulnerability. Additionally, implementing application crash monitoring and automated restart mechanisms can help maintain availability in case of unexpected crashes. Network-level controls such as web filtering to block known malicious wasm payloads may provide an additional layer of defense. Regular backups and incident response readiness will help minimize operational impact if exploitation occurs.

Description

The frame iterator could get stuck in a loop when encountering certain wasm frames leading to incorrect stack traces. This vulnerability affects Firefox < 128 and Thunderbird < 128.

References

Community reviews

Loading reviews…