How severe is CVE-2024-7965?

CVE-2024-7965 has a CVSS score of 8.8/10, rated HIGH. Immediate patching is strongly recommended.

Which packages are affected by CVE-2024-7965?

Affected package information for CVE-2024-7965 is not yet fully mapped. Check the official advisory links for details.

How do I fix CVE-2024-7965?

No patched version of the affected component has shipped for CVE-2024-7965 yet. Where your build allows, override or pin the dependency away from the vulnerable range, and apply any maintainer-recommended mitigation.

How do I detect CVE-2024-7965 in my code and dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for the affected component. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

How do I mitigate CVE-2024-7965 if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

How does O3 Security protect against CVE-2024-7965?

O3 pinpoints whether CVE-2024-7965 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Is CVE-2024-7965 actively exploited in the wild?

Yes. There are 6 known exploit references for CVE-2024-7965, including 5 in-the-wild exploitations observed on GitHub and other sources. Treat this as actively exploitable and prioritize patching immediately. All exploit code should only be run in an isolated sandbox environment for research or authorized testing — never against production systems without explicit written authorization.

What is the EPSS score for CVE-2024-7965?

CVE-2024-7965 has an EPSS (Exploit Prediction Scoring System) score of 17.2%, placing it in the 97th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score warrants monitoring and prompt remediation.

Is CVE-2024-7965 in the CISA Known Exploited Vulnerabilities catalog?

Yes. CVE-2024-7965 (Google Chromium V8 Inappropriate Implementation Vulnerability) was added to CISA's Known Exploited Vulnerabilities (KEV) catalog on 2024-08-28. CISA required all US federal civilian agencies to remediate this vulnerability by 2024-09-18. The required action was: Apply mitigations per vendor instructions or discontinue use of the product if mitigations are unavailable. Being listed in the KEV catalog is the strongest possible confirmation of active exploitation — treat this as a critical priority.

When was CVE-2024-7965 published, and has it been updated?

CVE-2024-7965 was published on August 21, 2024 and was last updated on April 16, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

CISA KEV·Added 2024-08-28 — agencies required to remediate by 2024-09-18

CVE-2024-7965

HIGH

Published

Aug 21, 2024

Updated

Apr 16, 2026

Affected

0 pkgs

Patched

None yet

Exploits

6 known

EPSS Exploitation Probability

via FIRST.org ↗

17.2%probability of exploitation in next 30 days

Moderate Risk97th percentile0.00%

EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.

Description

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)

Exploits & PoCs

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.