+44 1865 950 828 Secure Your Business
Actively exploited

CVE-2024-4761 Google Chromium V8 Out-of-Bounds Memory Write Vulnerability

Google Chromium V8 Engine contains an unspecified out-of-bounds memory write vulnerability via a crafted HTML page. This vulnerability could affect multiple web browsers that utilize Chromium, including, but not limited to, Google Chrome, Microsoft Edge, and Opera.

From the CISA KEV catalogue version 2026.11.06, with Cybergen analysis. Updated 6 Nov 2026.

Our Assessment

Should You Worry?

Patch urgentlyCybergen assessment
  • CISA confirmed exploitation in the wild and added it to the Known Exploited Vulnerabilities catalogue on 16 May 2024.
  • Rated High severity (CVSS 8.3, scored by CISA).
  • It has been in the catalogue for 904 days. Systems still unpatched now have almost certainly been scanned for it.
The Vulnerability

What It Is

Out of bounds write in V8 in Google Chrome prior to 124.0.6367.207 allowed a remote attacker to perform an out of bounds memory write via a crafted HTML page. (Chromium security severity: High)

Affected Versions

ProductVersions
Google Chrome124.0.6367.207 to before 124.0.6367.207

From the public CVE record, as supplied by the vendor. Always confirm against the vendor advisory.

From Watch to Action

What To Do Now

  1. 1

    Find it

    Search your asset inventory and external attack surface for Google Chromium V8. Include cloud images, appliances and anything a supplier runs for you.

    Attack Surface Management
  2. 2

    Fix it

    Apply mitigations per vendor instructions or discontinue use of the product if mitigations are unavailable.

    Vulnerability Management
  3. 3

    Hunt for compromise

    If an affected system was reachable before you patched, assume it may have been hit. Check logs, new accounts, web shells and outbound connections from the date of exposure.

    Incident Response
  4. 4

    Prove it is fixed

    Rescan or test the system after patching. Upgrades that fail silently and forgotten secondary instances are common.

    Penetration Testing

Vendor Advisories

Regulation

The Compliance Clock

Cyber EssentialsRated high, so if it affects devices in your Cyber Essentials scope, the update must be installed within 14 days of the vendor releasing it.NIS2If exploitation causes a significant incident, essential and important entities owe their CSIRT an early warning within 24 hours and a notification within 72 hours.DORAFinancial entities must classify ICT incidents and send an initial notification for a major incident within strict deadlines, with exploited flaws a common cause.US federal (BOD 22-01)Federal civilian agencies had until 6 Jun 2024 to remediate. A sensible benchmark for everyone else.

General guidance, not legal advice. Your obligations depend on your sector, scope and jurisdiction.

Stay Ahead

More Exploited Google Flaws

Get alerts for GoogleWe email you when a new Google vulnerability is confirmed as exploited. Add more vendors on Threat Watch.

By signing up you agree to receive Threat Watch alerts. Unsubscribe at any time. See our Privacy Policy.

CVE-2026-111497Google Brotli Unchecked Return Value VulnerabilityAdded 27 Oct 2026CVE-2026-58704Google Pixel Improper Authorization VulnerabilityAdded 16 Sep 2026CVE-2026-87491Google Chromium V8 Out of Bounds Write VulnerabilityAdded 9 Sep 2026CVE-2026-85046Google Chromium V8 Type Confusion VulnerabilityAdded 4 Sep 2026CVE-2026-11645Google Chromium V8 Out-of-Bounds Read and Write VulnerabilityAdded 9 Jun 2026CVE-2026-5281Google Dawn Use-After-Free VulnerabilityAdded 1 Apr 2026

All 76 exploited Google vulnerabilities

Not Sure If You Are Exposed?

Our attack surface and vulnerability teams can check your internet-facing estate for CVE-2024-4761 and every other exploited flaw on the list.

Check My Exposure
Evidence

Sources

  1. CISA Known Exploited Vulnerabilities catalogue
  2. NVD: CVE-2024-4761
  3. CVE record: CVE-2024-4761
  4. FIRST EPSS
  5. chromereleases.googleblog.com/2024/05/stable-channel-update-for-desktop_13.html
  6. issues.chromium.org/issues/339458194
  7. lists.fedoraproject.org/archives/list/[email protected]/message/NTSN22LNYXMWH
  8. lists.fedoraproject.org/archives/list/[email protected]/message/WSUWM73ZCXTN6
  9. lists.fedoraproject.org/archives/list/[email protected]/message/6G7EYH2JAK5OJ