# CVE-2024-9680: Mozilla Firefox Use-After-Free

> Attackers can execute arbitrary code in the content process via a use-after-free in Animation timelines, affecting Firefox and Thunderbird users.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Yes, since 15 Oct 2024 (CISA KEV), used in ransomware
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 9 Oct 2024
- **Updated:** 4 Aug 2026
- **Also known as:** ALSA-2024:7958, ALSA-2024:7977, ALSA-2024:8024, ALSA-2024:8025, DEBIAN-CVE-2024-9680, DLA-3914-1, DSA-5788-1, GHSA-hm3j-qgpw-pj98, MGASA-2024-0331, MGASA-2024-0336, RHSA-2024:7958, RHSA-2024:7977, RHSA-2024:8024, RHSA-2024:8025, RHSA-2024:8026, RHSA-2024:8027, RHSA-2024:8028, RHSA-2024:8029, RHSA-2024:8030, RHSA-2024:8031, RHSA-2024:8032, RHSA-2024:8033, RHSA-2024:8034, RHSA-2024:8131, RHSA-2024:8167, RHSA-2024:8176, RLSA-2024:7958, RLSA-2024:7977, RLSA-2024:8024, RLSA-2024:8025, SUSE-SU-2024:3731-1, UBUNTU-CVE-2024-9680, USN-7065-1, USN-7066-1, openSUSE-SU-2024:14393-1

## What is CVE-2024-9680?

CVE-2024-9680 is a critical use after free vulnerability in Debian Debian Linux, published on 9 Oct 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

An attacker was able to achieve code execution in the content process by exploiting a use-after-free in Animation timelines. We have had reports of this vulnerability being exploited in the wild. This vulnerability affects Firefox < 131.0.2, Firefox ESR < 128.3.1, Firefox ESR < 115.16.1, Thunderbird < 131.0.1, Thunderbird < 128.3.1, and Thunderbird < 115.16.0.

Weakness: CWE-416 (Use After Free)

## Which versions are affected by CVE-2024-9680?

It affects 3 products.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `firefox` | AlmaLinux:8 | All versions | 128.3.1-2.el8_10.alma.1 |
| `thunderbird` | AlmaLinux:8 | All versions | 128.3.1-1.el8_10.alma.1 |
| `firefox` | AlmaLinux:9 | All versions | 128.3.1-2.el9_4.alma.1 |
| `firefox-x11` | AlmaLinux:9 | All versions | 128.3.1-2.el9_4.alma.1 |
| `thunderbird` | AlmaLinux:9 | All versions | 128.3.1-1.el9_4.alma.1 |
| `firefox` | Red Hat:enterprise_linux:8::appstream | All versions | 0:128.3.1-2.el8_10 |
| `firefox-debuginfo` | Red Hat:enterprise_linux:8::appstream | All versions | 0:128.3.1-2.el8_10 |
| `firefox-debugsource` | Red Hat:enterprise_linux:8::appstream | All versions | 0:128.3.1-2.el8_10 |
| `thunderbird` | Red Hat:enterprise_linux:8::appstream | All versions | 0:128.3.1-1.el8_10 |
| `thunderbird-debuginfo` | Red Hat:enterprise_linux:8::appstream | All versions | 0:128.3.1-1.el8_10 |
| `thunderbird-debugsource` | Red Hat:enterprise_linux:8::appstream | All versions | 0:128.3.1-1.el8_10 |
| `firefox` | Red Hat:enterprise_linux:9::appstream | All versions | 0:128.3.1-2.el9_4 |
| `firefox-debuginfo` | Red Hat:enterprise_linux:9::appstream | All versions | 0:128.3.1-2.el9_4 |
| `firefox-debugsource` | Red Hat:enterprise_linux:9::appstream | All versions | 0:128.3.1-2.el9_4 |
| `firefox-x11` | Red Hat:enterprise_linux:9::appstream | All versions | 0:128.3.1-2.el9_4 |
| `thunderbird` | Red Hat:enterprise_linux:9::appstream | All versions | 0:128.3.1-1.el9_4 |
| `thunderbird-debuginfo` | Red Hat:enterprise_linux:9::appstream | All versions | 0:128.3.1-1.el9_4 |
| `thunderbird-debugsource` | Red Hat:enterprise_linux:9::appstream | All versions | 0:128.3.1-1.el9_4 |
| `firefox` | Red Hat:rhel_aus:8.2::appstream | All versions | 0:128.3.1-2.el8_2 |
| `firefox-debuginfo` | Red Hat:rhel_aus:8.2::appstream | All versions | 0:128.3.1-2.el8_2 |
| `firefox-debugsource` | Red Hat:rhel_aus:8.2::appstream | All versions | 0:128.3.1-2.el8_2 |
| `thunderbird` | Red Hat:rhel_aus:8.2::appstream | All versions | 0:128.3.1-1.el8_2 |
| `thunderbird-debuginfo` | Red Hat:rhel_aus:8.2::appstream | All versions | 0:128.3.1-1.el8_2 |
| `thunderbird-debugsource` | Red Hat:rhel_aus:8.2::appstream | All versions | 0:128.3.1-1.el8_2 |
| `firefox` | Red Hat:rhel_aus:8.4::appstream | All versions | 0:128.3.1-2.el8_4 |
| `firefox-debuginfo` | Red Hat:rhel_aus:8.4::appstream | All versions | 0:128.3.1-2.el8_4 |
| `firefox-debugsource` | Red Hat:rhel_aus:8.4::appstream | All versions | 0:128.3.1-2.el8_4 |
| `thunderbird` | Red Hat:rhel_aus:8.4::appstream | All versions | 0:128.3.1-1.el8_4 |
| `thunderbird-debuginfo` | Red Hat:rhel_aus:8.4::appstream | All versions | 0:128.3.1-1.el8_4 |
| `thunderbird-debugsource` | Red Hat:rhel_aus:8.4::appstream | All versions | 0:128.3.1-1.el8_4 |
| `firefox` | Red Hat:rhel_aus:8.6::appstream | All versions | 0:128.3.1-2.el8_6 |
| `firefox-debuginfo` | Red Hat:rhel_aus:8.6::appstream | All versions | 0:128.3.1-2.el8_6 |
| `firefox-debugsource` | Red Hat:rhel_aus:8.6::appstream | All versions | 0:128.3.1-2.el8_6 |
| `thunderbird` | Red Hat:rhel_aus:8.6::appstream | All versions | 0:128.3.1-1.el8_6 |
| `thunderbird-debuginfo` | Red Hat:rhel_aus:8.6::appstream | All versions | 0:128.3.1-1.el8_6 |
| `thunderbird-debugsource` | Red Hat:rhel_aus:8.6::appstream | All versions | 0:128.3.1-1.el8_6 |
| `firefox` | Red Hat:rhel_e4s:8.4::appstream | All versions | 0:128.3.1-2.el8_4 |
| `firefox-debuginfo` | Red Hat:rhel_e4s:8.4::appstream | All versions | 0:128.3.1-2.el8_4 |
| `firefox-debugsource` | Red Hat:rhel_e4s:8.4::appstream | All versions | 0:128.3.1-2.el8_4 |
| `thunderbird` | Red Hat:rhel_e4s:8.4::appstream | All versions | 0:128.3.1-1.el8_4 |

Products: Debian Debian Linux, Mozilla Firefox, Mozilla Thunderbird.

## How do I fix CVE-2024-9680?

Upgrade to a fixed version. US federal agencies must fix it by 5 Nov 2024.

## Is CVE-2024-9680 being exploited?

Yes. Attackers have exploited CVE-2024-9680 in the wild since at least 15 Oct 2024, including in ransomware campaigns.

Public exploit code:

- https://github.com/tdonaworth/Firefox-CVE-2024-9680 (github_poc): https://github.com/tdonaworth/Firefox-CVE-2024-9680
- Firefox/Tor Browser 0day exploit analysis (CVE-2024-9680) A UAF in animation timelines leading to RCE. Patched. (github_poc): https://github.com/moscovium-mc/Tor-0day-JavaScript-Exploit
- A vulnerability scanner for Firefox and Thunderbird that checks if your versions are out of date and susceptible to CVE-2024-9680. (github_poc): https://github.com/PraiseImafidon/Version_Vulnerability_Scanner

## Other vulnerabilities in Debian Debian Linux

- [CVE-2015-3306](https://insights.sbomify.com/CVE-2015-3306/): ProFTPD Improper Access Control (critical 10.0, exploited in the wild)
- [CVE-2025-49113](https://insights.sbomify.com/CVE-2025-49113/): RoundCube Webmail Deserialization of Untrusted Data (critical 9.9, exploited in the wild)
- [CVE-2026-24061](https://insights.sbomify.com/CVE-2026-24061/): GNU InetUtils Argument Injection (critical 9.8, exploited in the wild)
- [CVE-2025-39682](https://insights.sbomify.com/CVE-2025-39682/): Linux Kernel Improper Check for Unusual or Exceptional Conditions (critical 9.8, exploited in the wild)
- [CVE-2022-30333](https://insights.sbomify.com/CVE-2022-30333/): RARLAB UnRAR Directory Traversal (critical 9.8, exploited in the wild)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-9680 and fix it if it is affected.

What it is: CVE-2024-9680 is a critical use after free vulnerability in Debian Debian Linux, published on 9 Oct 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: Yes. Attackers have exploited CVE-2024-9680 in the wild since at least 15 Oct 2024, including in ransomware campaigns.

Affected product: Debian Debian Linux. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2024-9680/ (Markdown: https://insights.sbomify.com/CVE-2024-9680/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2024-9680
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2024-9680
- OSV: https://osv.dev/vulnerability/CVE-2024-9680

---
From sbomify Insights: https://insights.sbomify.com/CVE-2024-9680/
Summaries are generated and may contain mistakes; the official description above is the record.
