CVE-2024-7965
Inappropriate implementation in V8 in Google Chrome prior to 128.0.6613.84 allowed a remote attacker to potentially exploit heap corruption via a crafted HTML page. (Chromium security severity: High)
do firstApply mitigations per vendor instructions or discontinue use of the product if mitigations are unavailable.
Can a WAF block it? No. The attack is delivered via a crafted HTML page loaded in the browser, which is an HTTP request. The malicious input looks like normal web content, so a web application firewall cannot reliably distinguish it from legitimate pages.
Also consider: patch
Based on an AI reading of the CVE description, and no vendor rule found yet. We check Cloudflare, AWS, Google Cloud Armor and Azure; for Akamai, Imperva, Fastly, F5, ask your vendor.
Is CVE-2024-7965 being exploited?
Yes. CVE-2024-7965 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-7965?
CVE-2024-7965 is rated High with a CVSS score of 8.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-7965?
Yes. A fix has been recorded for CVE-2024-7965. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2024-7965 affect?
CVE-2024-7965 affects google:chrome, microsoft:edge_chromium. 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< 128.0.6613.84
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: 2 GitHub proofs of concept
- bi-zone/CVE-2024-7965 · 51 ★
- XueDugu/cve-2024-7965-poc · 1 ★
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
- no
- technical impact
- total
Assessed by CISA 31 Aug 2024 (SSVC 2.0.3).
timeline
- 21 Aug 2024Published
- 28 Aug 2024Added to CISA KEV (exploited in the wild) · 6 days later
- 31 Aug 2024CISA SSVC assessment: exploitation active · 3 days later
- 16 Sept 2024First proof-of-concept repository on GitHub (unvetted) · 16 days later
- 18 Sept 2024CISA remediation due date (US federal agencies) · 2 days later
- 21 Oct 2025CVE record last updated · 399 days (about 1 year) later
- 2 Nov 2026Analysed by vulneraibility.com · 377 days (about 1 year) later
- Linkchromereleases.googleblog.com /2024/08/stable-channel-update-for-desktop_21.html
- Linkissues.chromium.org /issues/356196918
- Linkcisa.gov /known-exploited-vulnerabilities-catalog?field_cve=CVE-2024-7965
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.