CVE-2024-9680
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.
do firstApply mitigations per vendor instructions or discontinue use of the product if mitigations are unavailable.
Can a WAF block it? No. This is a use-after-free memory bug. Generic WAF rules do not recognise the input that triggers it; only a rule written for this specific CVE can, and only if the triggering request has a recognisable shape.
Also consider: patch
Based on the weakness type only; no CVE-specific evidence yet. We check Cloudflare, AWS, Google Cloud Armor and Azure; for Akamai, Imperva, Fastly, F5, ask your vendor.
Is CVE-2024-9680 being exploited?
Yes. CVE-2024-9680 appears in CISA's Known Exploited Vulnerabilities catalog, which means exploitation in the wild has been confirmed and reported. Treat it as active rather than theoretical, and patch it ahead of higher-scoring vulnerabilities that carry no exploitation evidence.
How severe is CVE-2024-9680?
CVE-2024-9680 is rated Critical with a CVSS score of 9.8. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2024-9680?
Yes. A fix has been recorded for CVE-2024-9680. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2024-9680 affect?
CVE-2024-9680 affects mozilla:firefox, mozilla:thunderbird, debian:debian_linux. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
- affected< 131.0.2
- affected< 128.3.1
- affected< 115.16.1
- affected< 131.0.1
- affected< 128.3.1
- affected< 115.16.0
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.
public exploits
Unvetted proof-of-concept code on GitHub: 3 GitHub proofs of concept
Listed so you can judge urgency, not as a recommendation to run anything. GitHub “proofs of concept” are unvetted: some are fake or carry malware. Exploit-DB marks the entries its staff verified.
cisa ssvc
- exploitation
- active
- automatable
- yes
- technical impact
- total
Assessed by CISA 9 Oct 2024 (SSVC 2.0.3).
timeline
- 9 Oct 2024CISA SSVC assessment: exploitation active
- 9 Oct 2024Published · 1 day later
- 15 Oct 2024Added to CISA KEV (exploited in the wild) · 5 days later
- 17 Oct 2024First proof-of-concept repository on GitHub (unvetted) · 2 days later
- 5 Nov 2024CISA remediation due date (US federal agencies) · 19 days later
- 4 Aug 2026CVE record last updated · 637 days (about 2 years) later
- 2 Nov 2026Analysed by vulneraibility.com · 91 days (about 3 months) later
- Linkbugzilla.mozilla.org /show_bug.cgi?id=1923344
- Linkmsrc.microsoft.com /update-guide/en-US/vulnerability/CVE-2024-49039
- Linkmozilla.org /security/advisories/mfsa2024-51/
- Linkmozilla.org /security/advisories/mfsa2024-52/
- Linkcisa.gov /known-exploited-vulnerabilities-catalog?field_cve=CVE-2024-9680
- Linkbugs.freebsd.org /bugzilla/show_bug.cgi?id=281992
- Linklists.debian.org /debian-lts-announce/2024/10/msg00005.html
- Linklists.debian.org /debian-lts-announce/2024/10/msg00006.html
sources
- CVE List (CVE.org): description, affected versions, references; CVE Terms of Use
- NVD: CVSS and CPE data
- CISA KEV catalog: exploitation, date added, due date
- CISA Vulnrichment (ADP): SSVC decision points
- FIRST EPSS: exploit probability and percentile
- PoC-in-GitHub: GitHub repositories that claim a proof of concept
- Summary, impact and triage tags: written by our AI analysis pipeline from the sources above. Check them against the sources.