CVE-2024-6779

CRITICALNVD 9.69.6
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to NVD's CVSS score.

This critical-severity CVE scores 9.6 under NVD CVSS v3. EPSS exploit probability: 6.3% (93rd percentile of EPSS-scored CVEs). GitHub Security Advisory CVSS 8.8 is lower than this score; a lower GitHub score revises it only when its advisory is newer than the CVE record's last change, and this advisory (published 2024-07-17) is not newer than that change (2025-03-20), so it does not.

Triggered by: Headline CVSS from NVD CVSS v3
Sources: EPSS, GitHub Security Advisory, NVD CVSS v3
Trending — 4 sources updated this week

Also known asEUVD-2024-47811 (ENISA EUVD) · GHSA-v4v9-v4wf-9c86 (GitHub Security Advisories)Source: ENISA EUVD

9.6EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 6.3%CVSS: 9.6Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

Out of bounds memory access in V8 in Google Chrome prior to 126.0.6478.182 allowed a remote attacker to potentially perform a sandbox escape via a crafted HTML page. (Chromium security severity: High)

CVSS v3
9.6
Vendor severity
HIGHper Google (Chromium)Vendor's own band, not a CVSS rating — advisory text: (Chromium security severity: High)
EG Score
9.6CRITICALmedium confidence
EG Risk
46
EG Risk 46/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity96% × 45%
Impact severity (EG Severity): CVSS 9.6 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation6.3% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track* at high (mission-essential systems).
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines.
EPSS PROB
6.3%
EPSS %ILE
93rd
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (9.6): severity, escalated by confirmed exploitation. This CVE's 9.6 is its impact severity (EG Severity), not escalated.

EG Severity
9.6 CRITICALCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.NVD CVSS v3 · CVSS v3.0 or v3.1
EG Likelihood
6.3% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-11-01). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at low or medium mission impact; Track* at high (mission-essential systems).CISA BOD 26-04: 14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Track* at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines.

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

July 16, 2024

Last Modified

March 20, 2025

Advisory Details (2)

Auto-updated Oct 2, 2026
Patch available.
Web page

Chromium

https://issues.chromium.org/issues/351327767
Web page

Chrome Releases: Stable Channel Update for Desktop

https://chromereleases.googleblog.com/2024/07/stable-channel-update-for-desktop.html

Vendor Advisories for CVE-2024-6779(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Affected Packages

(4 across 4 ecosystems)
Debian:11(1)
PackageVulnerable rangeFix by version rangeDependents
chromium100.0.4896.127-1 ... 99.0.4844.84-1~deb11u1 (500 versions)
  • every version on: no fix on record
—
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
chromium113.0.5672.126-1 ... 126.0.6478.56-1~deb12u1 (136 versions)
  • every version up to 126.0.6478.182-1~deb12u1: fixed in 126.0.6478.182-1~deb12u1
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
chromium—
  • every version up to 126.0.6478.182-1: fixed in 126.0.6478.182-1
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
chromium—
  • every version up to 126.0.6478.182-1: fixed in 126.0.6478.182-1
—

Weakness Classification(2)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 27× in last 7d / 77× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

Showing the most recent 96 of 248 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. 4 repeat rows among the latest 100 are merged into the row they repeat. The 152 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-11-02 11:15 UTCEG score recompute
  2. 2026-11-02 11:15 UTCVendor advisory
  3. 2026-11-02 11:14 UTCGHSA enrichmentGHSA-v4v9-v4wf-9c86 · GitHub severity HIGH · GitHub CVSS 8.8
  4. 2026-11-01 16:32 UTCEPSS rescoreEPSS 6.3% · 93rd percentile
  5. 2026-11-01 13:31 UTCEG score recompute
  6. 2026-11-01 13:31 UTCVendor advisory
  7. 2026-11-01 13:31 UTCGHSA enrichmentGHSA-v4v9-v4wf-9c86 · GitHub severity HIGH · GitHub CVSS 8.8
  8. 2026-10-31 16:30 UTCEPSS rescoreEPSS 6.3% · 93rd percentile
  9. 2026-10-31 15:49 UTCVendor advisory
  10. 2026-10-31 15:49 UTCGHSA enrichmentGHSA-v4v9-v4wf-9c86 · GitHub severity HIGH · GitHub CVSS 8.8
  11. 2026-10-30 18:05 UTCEG score recompute
  12. 2026-10-30 18:05 UTCVendor advisory
  13. 2026-10-30 18:05 UTCGHSA enrichmentGHSA-v4v9-v4wf-9c86 · GitHub severity HIGH · GitHub CVSS 8.8
  14. 2026-10-30 16:32 UTCEPSS rescoreEPSS 6.3% · 93rd percentile
  15. 2026-10-29 20:22 UTCEG score recompute
  16. 2026-10-29 20:22 UTCVendor advisory
  17. 2026-10-29 20:22 UTCGHSA enrichmentGHSA-v4v9-v4wf-9c86 · GitHub severity HIGH · GitHub CVSS 8.8
  18. 2026-10-29 16:31 UTCEPSS rescoreEPSS 6.3% · 93rd percentile
  19. 2026-10-28 22:39 UTCEG score recompute
  20. 2026-10-28 22:39 UTCGHSA enrichmentGHSA-v4v9-v4wf-9c86 · GitHub severity HIGH · GitHub CVSS 8.8
  21. 2026-10-28 16:30 UTCEPSS rescoreEPSS 6.3% · 93rd percentile
  22. 2026-10-28 00:56 UTCEG score recompute
  23. 2026-10-28 00:56 UTCGHSA enrichmentGHSA-v4v9-v4wf-9c86 · GitHub severity HIGH · GitHub CVSS 8.8
  24. 2026-10-27 16:30 UTCEPSS rescoreEPSS 6.3% · 93rd percentile
  25. 2026-10-27 03:10 UTCEG score recompute
Show 71 more
  1. 2026-10-27 03:10 UTCVendor advisory
  2. 2026-10-27 03:10 UTCGHSA enrichmentGHSA-v4v9-v4wf-9c86 · GitHub severity HIGH · GitHub CVSS 8.8
  3. 2026-10-26 01:24 UTCVendor advisory
  4. 2026-10-26 01:24 UTCGHSA enrichmentGHSA-v4v9-v4wf-9c86 · GitHub severity HIGH · GitHub CVSS 8.8
  5. 2026-10-25 16:53 UTCEG score recompute
  6. 2026-10-25 16:30 UTCEPSS rescoreEPSS 6.3% · 93rd percentile
  7. 2026-10-25 03:41 UTCEG score recompute
  8. 2026-10-25 03:41 UTCVendor advisory
  9. 2026-10-25 03:41 UTCGHSA enrichmentGHSA-v4v9-v4wf-9c86 · GitHub severity HIGH · GitHub CVSS 8.8
  10. 2026-10-24 16:30 UTCEPSS rescoreEPSS 6.3% · 93rd percentile
  11. 2026-10-24 05:58 UTCEG score recompute
  12. 2026-10-24 05:58 UTCGHSA enrichmentGHSA-v4v9-v4wf-9c86 · GitHub severity HIGH · GitHub CVSS 8.8
  13. 2026-10-23 16:30 UTCEPSS rescoreEPSS 6.3% · 93rd percentile
  14. 2026-10-23 08:14 UTCEG score recompute
  15. 2026-10-23 08:14 UTCVendor advisory
  16. 2026-10-23 08:14 UTCGHSA enrichmentGHSA-v4v9-v4wf-9c86 · GitHub severity HIGH · GitHub CVSS 8.8
  17. 2026-10-22 16:31 UTCEPSS rescoreEPSS 6.3% · 93rd percentile
  18. 2026-10-22 10:28 UTCEG score recompute
  19. 2026-10-22 10:28 UTCVendor advisory
  20. 2026-10-22 10:27 UTCGHSA enrichmentGHSA-v4v9-v4wf-9c86 · GitHub severity HIGH · GitHub CVSS 8.8
  21. 2026-10-21 16:30 UTCEPSS rescoreEPSS 6.3% · 93rd percentile
  22. 2026-10-21 12:42 UTCEG score recompute
  23. 2026-10-21 12:42 UTCVendor advisory
  24. 2026-10-21 12:42 UTCGHSA enrichmentGHSA-v4v9-v4wf-9c86 · GitHub severity HIGH · GitHub CVSS 8.8
  25. 2026-10-20 16:30 UTCEPSS rescoreEPSS 6.3% · 93rd percentile
  26. 2026-10-20 15:00 UTCEG score recompute
  27. 2026-10-20 14:59 UTCGHSA enrichmentGHSA-v4v9-v4wf-9c86 · GitHub severity HIGH · GitHub CVSS 8.8
  28. 2026-10-19 16:30 UTCEPSS rescoreEPSS 6.3% · 93rd percentile
  29. 2026-10-19 14:53 UTCEG score recompute
  30. 2026-10-19 14:53 UTCVendor advisory
  31. 2026-10-19 14:53 UTCGHSA enrichmentGHSA-v4v9-v4wf-9c86 · GitHub severity HIGH · GitHub CVSS 8.8
  32. 2026-10-18 16:30 UTCEPSS rescoreEPSS 6.3% · 93rd percentile
  33. 2026-10-18 05:56 UTCEG score recompute
  34. 2026-10-17 16:31 UTCEPSS rescoreEPSS 6.3% · 93rd percentile
  35. 2026-10-16 16:37 UTCEPSS rescoreEPSS 6.3% · 93rd percentile
  36. 2026-10-15 16:30 UTCEPSS rescoreEPSS 6.3% · 93rd percentile
  37. 2026-10-14 16:30 UTCEPSS rescoreEPSS 6.3% · 93rd percentile
  38. 2026-10-13 16:31 UTCEPSS rescoreEPSS 6.3% · 93rd percentile
  39. 2026-10-12 17:35 UTCEG score recompute
  40. 2026-10-12 16:31 UTCEPSS rescoreEPSS 6.3% · 93rd percentile
  41. 2026-10-11 21:01 UTCEG score recompute
  42. 2026-10-11 15:53 UTCEG score recompute
  43. 2026-10-11 13:46 UTCEPSS rescoreEPSS 6.3% · 93rd percentile
  44. 2026-10-10 19:58 UTCEPSS rescoreEPSS 6.3% · 93rd percentile
  45. 2026-10-10 14:03 UTCOSV refresh
  46. 2026-10-09 20:05 UTCEPSS rescoreEPSS 6.3% · 93rd percentile
  47. 2026-10-08 17:08 UTCEPSS rescoreEPSS 6.3% · 93rd percentile
  48. 2026-10-07 23:46 UTCEPSS rescoreEPSS 6.3% · 93rd percentile
  49. 2026-10-06 15:16 UTCEPSS rescoreEPSS 6.3% · 93rd percentile
  50. 2026-10-05 17:41 UTCEPSS rescoreEPSS 6.3% · 93rd percentile
  51. 2026-10-04 23:20 UTCEPSS rescoreEPSS 6.3% · 93rd percentile
  52. 2026-10-03 14:24 UTCEPSS rescoreEPSS 6.3% · 93rd percentile
  53. 2026-10-02 16:28 UTCEG score recompute
  54. 2026-10-01 19:48 UTCEPSS rescoreEPSS 6.3% · 93rd percentile
  55. 2026-09-30 15:02 UTCEPSS rescoreEPSS 6.3% · 93rd percentile
  56. 2026-09-28 13:50 UTCEPSS rescoreEPSS 6.3% · 93rd percentile
  57. 2026-09-27 13:44 UTCEPSS rescoreEPSS 6.3% · 93rd percentile
  58. 2026-09-26 15:57 UTCEPSS rescoreEPSS 6.3% · 93rd percentile
  59. 2026-09-24 14:01 UTCEPSS rescoreEPSS 6.3% · 93rd percentile
  60. 2026-09-23 13:46 UTCEPSS rescoreEPSS 6.3% · 93rd percentile
  61. 2026-09-22 14:47 UTCEPSS rescoreEPSS 6.3% · 93rd percentile
  62. 2026-09-20 23:27 UTCOSV refresh
  63. 2026-09-20 20:14 UTCEPSS rescoreEPSS 6.3% · 93rd percentile
  64. 2026-09-18 19:26 UTCEPSS rescoreEPSS 6.3% · 93rd percentile
  65. 2026-09-16 14:06 UTCEPSS rescoreEPSS 6.3% · 93rd percentile
  66. 2026-09-16 05:12 UTCEPSS rescoreEPSS 6.3% · 93rd percentile
  67. 2026-09-15 03:08 UTCEPSS rescoreEPSS 6.3% · 93rd percentile
  68. 2026-09-13 16:45 UTCEPSS rescoreEPSS 6.2% · 93rd percentile
  69. 2026-09-12 14:59 UTCEPSS rescoreEPSS 6.2% · 93rd percentile
  70. 2026-09-11 14:51 UTCEPSS rescoreEPSS 6.2% · 93rd percentile
  71. 2026-09-11 09:35 UTCEPSS rescoreEPSS 6.2% · 93rd percentile

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2024-6779?
CVE-2024-6779 is a critical-severity vulnerability; its CVE record was published on July 16, 2024. Out of bounds memory access in V8 in Google Chrome prior to 126.0.6478.182 allowed a remote attacker to potentially perform a sandbox escape via a crafted HTML page. (Chromium security severity: High)
When was the CVE record for CVE-2024-6779 published?
The CVE record for CVE-2024-6779 was published on July 16, 2024. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of March 20, 2025; the record at its source may have been updated since.
Is CVE-2024-6779 actively exploited?
CVE-2024-6779 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 6.3% probability of exploitation in the next 30 days (93rd percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2024-6779?
CVE-2024-6779 has a CVSS v3 base score of 9.6 (NVD).
How do I remediate CVE-2024-6779?
A fix for CVE-2024-6779 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2024-6779 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2024-6779

Explore →

Is Your Infrastructure Affected by CVE-2024-6779?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Book a Demo →Browse All CVEs